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

[jaeger] make Deployment depend on oauth2 config, if enabled #541

Merged
merged 1 commit into from
Feb 22, 2024

Conversation

cdanis
Copy link
Contributor

@cdanis cdanis commented Feb 22, 2024

What this PR does

Without this, changes to the oauth2-proxy configuration don't affect any metadata in the Deployment, meaning pods must be deleted manually after a configuration change.

Checklist

  • DCO signed
  • Commits are GPG signed
  • Chart Version bumped
  • Title of the PR starts with chart name ([jaeger] or [jaeger-operator])
  • README.md has been updated to match version/contain new values

Signed-off-by: Chris Danis <cdanis@wikimedia.org>
@cdanis cdanis force-pushed the oauth2-config-deploy branch from 4884f0e to d63e5c1 Compare February 22, 2024 22:10
@pavelnikolov pavelnikolov merged commit 3af618d into jaegertracing:main Feb 22, 2024
2 checks passed
antonioberben pushed a commit to antonioberben/jaeger-helm-charts that referenced this pull request Feb 26, 2024
…racing#541)

Signed-off-by: Chris Danis <cdanis@wikimedia.org>
Signed-off-by: Antonio Berben <antonio.berben@solo.io>
antonioberben pushed a commit to antonioberben/jaeger-helm-charts that referenced this pull request Feb 26, 2024
…racing#541)

Signed-off-by: Chris Danis <cdanis@wikimedia.org>
Signed-off-by: Antonio Berben <antonio.berben@solo.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants