Merged
Conversation
That we can deploy oauth2-proxy again.
carlobeltrame
approved these changes
Dec 22, 2025
Member
carlobeltrame
left a comment
carlobeltrame
left a comment
There was a problem hiding this comment.
In the future, add renovate for helmfile and for helm, and install the same modern helm version in all deployment workflows.
For now, fixing our ability to deploy the ops dashboard at all is the priority 👍
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The oauth2-proxy chart had a bug and deployed redis even when disabled.
This is fixed with helm v4.
We also need to update helmfile, the old version of helmfile had a problem with the new helm.
Result can be seen here:
https://github.com/ecamp/ecamp3/actions/runs/19785182325
And with update of oauth2-proxy:
https://github.com/ecamp/ecamp3/actions/runs/19785222001