Project

Profile

Help

Story #5598

[Epic] Long-Term To-Do for pulp-operator

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

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

0%

Estimated time:
(Total: 0:00 h)
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Quarter:

Subtasks

Task #5404: Container CI testing shouldn't install packages onto the pulp-api containerNEWmdepaulo@redhat.com

Actions
Task #5599: Operator: Upgrades orchestrationNEW

Actions
Task #5600: Implement multiple pulp-resource-manager instancesNEW

Actions
Task #5601: Implement multiple pulp-api instancesNEW

Actions
Task #5602: Implement pulp-resource-manager autoscalingNEW

Actions
Task #5603: Implement pulp-api autoscalingNEW

Actions

Related issues

Follows Pulp - Story #5587: [Epic] Medium Term To-Do for pulp-operatorNEW

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>
Follows Pulp - Story #5132: [Epic] As a user, I can consume Pulp 3 from OperatorHub.ioNEW

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by fao89 almost 2 years ago

  • Tags CI/CD added

#2 Updated by fao89 over 1 year ago

  • Category set to Operator

#3 Updated by mdepaulo@redhat.com 8 months ago

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

#4 Updated by mdepaulo@redhat.com 8 months ago

  • Follows Story #5132: [Epic] As a user, I can consume Pulp 3 from OperatorHub.io added

Please register to edit this issue

Also available in: Atom PDF