Project

Profile

Help

Story #5132

[Epic] As a user, I can consume Pulp 3 from OperatorHub.io

Added by mdepaulo@redhat.com 5 months ago. Updated about 1 hour ago.

Status:
NEW
Priority:
Normal
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

29%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

Synopsis

Kubernetes Operators are the the new preferred way to deploy and manage applications on top of Kubernetes / OpenShift.

Once ready for the community to consume, they are published on https://OperatorHub.io

TODO

Before our operator can be published, it needs to be stable enough in certain ways:
  • Ansible Molecule and Pulp-Smash need to run against it
  • Users need to be able to specify a consistent/stable port to access content (& API) against, rather than just the random port that K8s assigns.
  • Storage needs to be expandable
  • In general, a user's interaction with the containers should be stable. It shouldn't randomly stop working without interaction because we re-worked something in the containers / operator.
  • Some security improvements should be implemented

Not required

The following is strongly desirable, but is an acceptable limitation for this Epic:
  • Support for K8s clusters that do not support ReadWriteMany Persistent Volume Claims. This can be documented as a limitation if not implemented in time.

Subtasks

Story #5133: Rebase pulp-operator on latest operator frameworkNEWmdepaulo@redhat.com

Actions
Story #5134: Fix pulp-operator CI w/ Ansible MoleculeNEWmdepaulo@redhat.com

Actions
Story #5135: Pulp Smash should be run against pulp-operator as part of CINEWmdepaulo@redhat.com

Actions
Story #5136: pulp-operator needs a stable & configurable accessible portNEWmdepaulo@redhat.com

Actions
Story #5137: pulp-operator needs configurable and expandable storage sizeNEWmdepaulo@redhat.com

Actions
Story #5138: In pulp-operator, the content_origin should be set to the actual accessible service URLCLOSED - CURRENTRELEASEmdepaulo@redhat.com

Actions
Story #5139: pulp-operator should have better use of the ENTRYPOINT & env varsNEWmdepaulo@redhat.com

Actions
Story #5140: Figure out how to make /var/lib/pulp/static part of the container imagesNEWmdepaulo@redhat.com

Actions
Story #5141: The postgres container (when part of pulp-operator at least) should use an fsGroupNEWmdepaulo@redhat.com

Actions
Story #5142: The pulp-operator Persistent Volume Claim for /var/lib/pulp should by default be writable only by rootNEWmdepaulo@redhat.com

Actions
Story #5143: Publish pulp-operator on OperatorHub.ioNEWmdepaulo@redhat.com

Actions
Task #5174: pulp-operator CI should automatically build its image for k3s testingCLOSED - COMPLETEmdepaulo@redhat.com

Actions
Task #5175: pulp-operator should auto-publish to quay.ioNEWmdepaulo@redhat.com

Actions
Issue #5414: HTTP requests to containers hang over IPv6CLOSED - CURRENTRELEASEmdepaulo@redhat.comActions
Story #5657: pulp-operator should use nginx and possibly other K8s ingressesNEWmdepaulo@redhat.com

Actions
Story #5683: pulp-operator should set content_origin to load balancer addresses, when availableNEW

Actions

History

#1 Updated by fabricio.aguiar about 1 hour ago

  • Tags CI/CD added

Please register to edit this issue

Also available in: Atom PDF