Fix cloudbeaver ingress tls hosts secretName#38
Merged
Brawdunoir merged 1 commit intoApr 2, 2026
Merged
Conversation
Contributor
Author
Collaborator
|
Hello and thanks for the PR. I introduced it after adding HTTP Route, my bad. |
Collaborator
|
Can you please bump the patch version on the chart so I can merge ? |
ftqualifio
force-pushed
the
fix/cloudbeaver-ingress-secretname
branch
from
April 2, 2026 14:45
59e5db4 to
908d781
Compare
ftqualifio
force-pushed
the
fix/cloudbeaver-ingress-secretname
branch
from
April 2, 2026 14:49
44d8987 to
f2e9578
Compare
Contributor
Author
|
Done! |
Brawdunoir
self-requested a review
April 2, 2026 16:08
Brawdunoir
approved these changes
Apr 2, 2026
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.
"cloudbeaver/templates/ingress.yaml" at <include>: wrong number of args for include: want 2 got 0