Project

Profile

Help

Story #8598

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

pulp-operator should disable container navigation in galaxy by default

Added by chambridge 16 days ago. Updated 9 days ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
Category:
Operator
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.

Associated revisions

Revision f3bd8308 View on GitHub
Added by chambridge 9 days ago

Container registry capabilities will be disable by default in Galaxy

  • Update CRD with container token secret
  • Update CRD with settings
  • Add playbook defaults
  • Setup token server value
  • Mount container auth keys when secret is provided
  • Provide galaxy container CR for testing
  • Add secret to status of Pulp and PulpBackup
  • Write secret during backup
  • Read/Create secret during restore

fixes #8598 https://pulp.plan.io/issues/8598

History

#1 Updated by chambridge 10 days ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to chambridge

#2 Updated by pulpbot 9 days ago

  • Status changed from ASSIGNED to POST

#3 Updated by chambridge 9 days ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

Please register to edit this issue

Also available in: Atom PDF