Skip to content
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

The gatekeeper seems not to reload the new configuration after changing harness uri_role_mappings #418

Closed
zsinnema opened this issue Feb 2, 2022 · 2 comments · Fixed by #484
Assignees
Milestone

Comments

@zsinnema
Copy link
Contributor

zsinnema commented Feb 2, 2022

When an application is using uri_role_mapping option from cloudharness it seems that after the redeploy the gatekeeper still uses the old configuration. After a pod restart the new configuration is "activated"/"used"

@filippomc filippomc added this to the v2.0.0 milestone Feb 17, 2022
@filippomc filippomc self-assigned this May 9, 2022
@filippomc
Copy link
Collaborator

Relates to this: kubernetes/kubernetes#22368. Need to find a way to force pod restart when the configuration changes

@filippomc
Copy link
Collaborator

filippomc commented May 9, 2022

Adding an annotation to the pod may be a solution: https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments

filippomc added a commit that referenced this issue May 11, 2022
#418 Force restart of gatekeeper on conf change
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants