-
Notifications
You must be signed in to change notification settings - Fork 361
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
Better helm support for airgapped clusters with no access to public image registry #3049
Comments
aren't they share same registry? |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
Let's track adding top level images configuration support for statsd exporter using this GH issue |
Should we close this? Leave undo to be tracked via #3369 |
this is the parent issue / |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
What about envoy proxy image? That should be configurable too. |
you should be able do that with https://gateway.envoyproxy.io/docs/api/extension_types/#envoyproxykubernetesprovider right now. |
Description:
Envoy Gateway uses 3 images
Would be great if theres a simpler way to change the registry as a helm value without doing a helm template and edit
[optional Relevant Links:]
The text was updated successfully, but these errors were encountered: