Actions
Story #5132
closed[Epic] As a user, I can consume Pulp 3 from OperatorHub.io
Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
Category:
Operator - Moved to Github Issues
Sprint/Milestone:
-
Start date:
Due date:
% Done:
100%
Estimated time:
(Total: 0:00 h)
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Quarter:
Description
h1. !! Ticket moved to GitHub: "pulp/pulp-operator/256":https://github.com/pulp/pulp-operator/issues/256
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.
Related issues
Updated by fao89 over 4 years ago
- Category set to Operator - Moved to Github Issues
Updated by mdepaulo@redhat.com almost 4 years ago
- Precedes Story #5587: [Epic] Medium Term To-Do for pulp-operator added
Updated by mdepaulo@redhat.com almost 4 years ago
- Precedes Story #5598: [Epic] Long-Term To-Do for pulp-operator added
Updated by fao89 about 3 years ago
- Description updated (diff)
- Status changed from NEW to CLOSED - DUPLICATE
Actions