Change kubeRBACProxyImage to use bitnami legacy container#79
Merged
git-hulk merged 1 commit intoRocksLabs:unstablefrom Oct 28, 2025
Merged
Change kubeRBACProxyImage to use bitnami legacy container#79git-hulk merged 1 commit intoRocksLabs:unstablefrom
git-hulk merged 1 commit intoRocksLabs:unstablefrom
Conversation
git-hulk
approved these changes
Oct 28, 2025
Member
|
@s2x Thanks for your fix. |
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
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.
fix: switch from bitnami/kube-rbac-proxy:0.14.0 to bitnamilegacy/kube-rbac-proxy:0.14.0
The bitnami/kube-rbac-proxy image was deprecated and removed from Docker Hub, causing image pull errors.
According to bitnami/charts#35164 , the legacy images are now hosted under the bitnamilegacy namespace. This change updates the image reference to use the legacy registry to restore compatibility and ensure successful deployments.