New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZARF removes namespace labels pertaining to pod security when using --adopt-existing-resources #2489
Labels
bug 🐞
Something isn't working
Comments
Confirmed this is a bug, thanks! |
AustinAbro321
added a commit
that referenced
this issue
May 20, 2024
## Description Changes behavior to keep existing metadata on namespaces rather than steamrolling them ## Related Issue Fixes #2489 ## Checklist before merging - [ ] Test, docs, adr added or updated as needed - [ ] [Contributor Guide Steps](https://github.com/defenseunicorns/zarf/blob/main/.github/CONTRIBUTING.md#developer-workflow) followed --------- Co-authored-by: Lucas Rodriguez <[email protected]> Co-authored-by: Philip Laine <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Device and OS:
App version: 0.33.1
Kubernetes distro being used: rke2 1.28.9
Other:
Steps to reproduce
Expected result
The existing labels that do not interfere with ZARF remain
Actual Result
Existing labels pertaining to pod security are removed
Visual Proof (screenshots, videos, text, etc)
Severity/Priority
Additional Context
Add any other context or screenshots about the technical debt here.
The text was updated successfully, but these errors were encountered: