Project

Profile

Help

Actions
Send by e-mail Copy link

Story #8598

closed

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 over 3 years ago. Updated over 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
chambridge
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
Copy link
 #1

Updated by chambridge over 3 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to chambridge
Actions
Copy link
 #2

Updated by pulpbot over 3 years ago

  • Status changed from ASSIGNED to POST

Added by chambridge over 3 years ago

Revision f3bd8308 | View on GitHub

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

Actions
Copy link
 #3

Updated by chambridge over 3 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by fao89 over 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Send by e-mail Copy link

Also available in: Atom PDF