Loading...

XML

Word

Printable

Type: Feature Request
Resolution: Won't Do
Priority: Major
Fix Version/s: None
Affects Version/s: None
Component/s: quay-operator
Labels:
- rfe-rejected-to-wontdo
- triaged

Target Version:
None
Activity Type:
Product / Portfolio Work
Status Summary:
None
Blocked:
False
Blocked Reason:
None
Products:
None
Hierarchy Progress Bar:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Review Complete:
PX Impact Score:
PX Impact Range:
None
PX Priority Data:
PX Technical Impact:
None
PX Technical Impact Notes:
None
PX Scheduling Request:
None

What problem/issue/behavior are you having trouble with? What do you expect to see?
Currently the quay operator only accepts TLS certificates for Quay in the quay-config-bundle-secret. This mechanism is not ideal for deployments where customer's are using 'kubernetes.io/tls' and have to manually manage the TLS key in the quay-config-bundle-secret.

Would be great to see the operator support an option in the CRD to take the name of a k8s secret as input for the TLS keys and automatically update the quay app deployment when the TLS key is updated.

is related to

PROJQUAY-8801 Cert-manager support

Assignee:: Daniel Messer

Reporter:: Ivan C (Inactive)

Need Info From:: None

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2021/11/23 5:30 PM

Updated:: 2025/10/09 1:55 PM

Resolved:: 2024/05/14 10:41 AM

Target start:: None

Target end:: None

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates