Project

Profile

Help

Story #5132

closed

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

Added by mdepaulo@redhat.com over 4 years ago. Updated about 2 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
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.

Sub-issues 41 (0 open41 closed)

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

Actions
Story #5134: Fix pulp-operator CI w/ Ansible MoleculeCLOSED - CURRENTRELEASEfao89

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

Actions
Story #5136: pulp-operator needs a stable & configurable accessible portCLOSED - DUPLICATE

Actions
Story #5137: As a pulp-operator user, I can configure & expand the storage volume sizeCLOSED - DUPLICATE

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 varsCLOSED - DUPLICATE

Actions
Story #5140: Make /var/lib/pulp/assets part of the container imagesCLOSED - DUPLICATEmdepaulo@redhat.com

Actions
Story #5141: The postgres container (when part of pulp-operator at least) should use an fsGroupMODIFIEDchambridge

Actions
Story #5142: The pulp-operator Persistent Volume Claim for /var/lib/pulp should by default be writable only by rootMODIFIED

Actions
Story #5143: Publish pulp-operator on OperatorHub.ioCLOSED - CURRENTRELEASE

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.ioCLOSED - COMPLETEmdepaulo@redhat.com

Actions
Issue #5414: HTTP requests to containers hang over IPv6CLOSED - CURRENTRELEASEmdepaulo@redhat.comActions
Story #5657: pulp-operator should deploy nginx as the Pulp WebserverMODIFIED

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

Actions
Task #6522: Upgrade pulp container for pulp-operator to Fedora 32CLOSED - COMPLETEmdepaulo@redhat.com

Actions
Story #8272: pulp-operator needs to support the creation of route and ingressMODIFIEDchambridge

Actions
Task #8273: pulp-operator ci/cd clean up MODIFIEDchambridge

Actions
Story #8289: pulp-operator should use a secret for database configurationMODIFIEDchambridge

Actions
Task #8293: pulp-operator bump API version to v1beta1 to allow for productizationMODIFIEDchambridge

Actions
Task #8294: pulp-operator custom resource definition needs schema definitionMODIFIEDchambridge

Actions
Task #8345: pulp-operator should use standard redis imageMODIFIEDchambridge

Actions
Task #8353: pulp-operator should accept or generate a secret for the admin passwordMODIFIEDchambridge

Actions
Story #8361: pulp-operator to support object storage for contentMODIFIEDchambridge

Actions
Story #8402: pulp-operator will provide deployment status information itemsMODIFIEDchambridge

Actions
Story #8409: pulp-operator should be installable by catalog source on OpenShiftMODIFIEDchambridge

Actions
Task #8418: pulp-operator to vendor required collectionsMODIFIEDchambridge

Actions
Task #8424: bugfix for pulp-operator using Azure blob storageMODIFIEDchambridge

Actions
Story #8429: As a pulp-operator user, I can use a version of Pulp with my desired set of pluginsCLOSED - DUPLICATEmdepaulo@redhat.com

Actions
Story #8456: pulp-operator should allow resource requirements to be setMODIFIEDchambridge

Actions
Story #8472: pulp-operator should allow for the migration of database dataCLOSED - CURRENTRELEASE

Actions
Story #8473: pulp-operator should enable backup of secrets and database to a PVCCLOSED - CURRENTRELEASE

Actions
Story #8474: pulp-operator should enable the backup of filesystem data when using RWM PVCCLOSED - CURRENTRELEASEchambridge

Actions
Story #8513: pulp-operator should be able to restore a pulp deploymentCLOSED - CURRENTRELEASEchambridge

Actions
Story #8530: pulp-operator ci/cd should provide nightly builds for simplified testingCLOSED - CURRENTRELEASEchambridge

Actions
Story #8563: Simplify the downstream productization changes needed in pulp-operatorCLOSED - CURRENTRELEASEchambridge

Actions
Story #8598: pulp-operator should disable container navigation in galaxy by defaultCLOSED - CURRENTRELEASEchambridge

Actions
Story #8630: pulp-operator restore flexibility improvementsCLOSED - CURRENTRELEASEchambridge

Actions
Story #8877: pulp-operator should allow user to specify the storage class for redis PVCCLOSED - CURRENTRELEASEchambridge

Actions
Issue #8880: pulp-operator fails to check status endpoint when deployed in a different namespaceCLOSED - CURRENTRELEASEchambridgeActions

Related issues

Precedes Pulp - Story #5587: [Epic] Medium Term To-Do for pulp-operatorCLOSED - DUPLICATEmdepaulo@redhat.com

Actions
Precedes Pulp - Story #5598: [Epic] Long-Term To-Do for pulp-operatorCLOSED - DUPLICATEmdepaulo@redhat.com

Actions
Actions #1

Updated by fao89 over 4 years ago

  • Tags CI/CD added
Actions #2

Updated by fao89 over 3 years ago

  • Category set to Operator - Moved to Github Issues
Actions #3

Updated by mdepaulo@redhat.com about 3 years ago

  • Precedes Story #5587: [Epic] Medium Term To-Do for pulp-operator added
Actions #4

Updated by mdepaulo@redhat.com about 3 years ago

  • Precedes Story #5598: [Epic] Long-Term To-Do for pulp-operator added
Actions #5

Updated by fao89 over 2 years ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE

Also available in: Atom PDF