Actions
Story #8598
closedStory #5132: [Epic] As a user, I can consume Pulp 3 from OperatorHub.io
pulp-operator should disable container navigation in galaxy by default
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
Operator - Moved to Github Issues
Sprint/Milestone:
-
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
The current experience is that galaxy when running on Kubernetes will assume users will use built-in registry or quay.
A custom resource field will enable/disable of container navigation for demo purposes. This field will be hidden from the form view in the cluster service version.
Actions
Container registry capabilities will be disable by default in Galaxy
fixes #8598 https://pulp.plan.io/issues/8598