-
Notifications
You must be signed in to change notification settings - Fork 3
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
file permission errors in the certificates init container #136
Comments
fwiw -- adjusting the init container's runtime user to match the registry1 image user with the following override did not resolve the behavior:
(Note that the GL chart doesn't appear to expose the security context for each individual init container.. Applying the above broke the |
Dropping some links to various pieces of the helm chart here as well because they were a bit of pain to track down:
|
We could check to see if we see this in the staging env @defenseunicorns/swf |
Observed this in staging - it currently only affects the |
Of note adding certs to GitLab works for webservice but not registry and the GitLab chart does not expose extra volume mounts in the registry... |
Blocking this on defenseunicorns/uds-core#464 for now - we could implement our own path / workarounds but it would be best to integrate with uds-core |
Environment
Device and OS: RHEL VMs on Nutanix provisioned infra
App/package versions: v17.0.1
Kubernetes distro being used: RKE2
Steps to reproduce
Expected result
No errors.
Actual Result
Severity/Priority
low -> mid
I'm not sure the extent of the impact here given that most environments seem to be functional, but I could see this causing some odd behavior down the line if not addressed.
Additional Context
The text was updated successfully, but these errors were encountered: