Bug 1960651
Summary: | Authentication Operator should not copy app.kubernetes.io/instance label | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Asmita <agawand> |
Component: | kube-apiserver | Assignee: | Abu Kashem <akashem> |
Status: | CLOSED WONTFIX | QA Contact: | Ke Wang <kewang> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 4.6 | CC: | akashem, aos-bugs, eparis, jokerman, kostrows, mfojtik, mharri, slaznick, surbania, tim.speetjens, william.caban, xxia |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-08-18 14:26:03 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Asmita
2021-05-14 13:54:11 UTC
Make ArgoCD ignore the namespaces that already contain managed payloads, we can't and won't be special-casing every project out there. If it's not possible to make ArgoCD ignore namespaces, make them add that ability. From your comment, I understand that copying the labels and annotations from the source secret to the destination is a design decision. What is the use case for copying that? Does the authentication operator accept any special labels or annotations in the secrets to fine tune its behaviour? For reference, related argocd issue. https://github.com/argoproj/argo-cd/issues/4487 Moving closer to the team dealing with APIs. Dear reporter, As part of the migration of all OpenShift bugs to Red Hat Jira, we are evaluating all bugs which will result in some stale issues or those without high or urgent priority to be closed. If you believe this bug still requires engineering resolution, we kindly ask you to follow this link[1] and continue working with us in Jira by recreating the issue and providing the necessary information. Also, please provide the link to the original Bugzilla in the description. To create an issue, follow this link: [1] https://issues.redhat.com/secure/CreateIssueDetails!init.jspa?pid=12332330&issuetype=1&priority=10300&components=12367637 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days |