Repository navigation
Conversation
Carry operator proxy settings, credentials, and CA trust in each sandbox generation. Stage the material privately on the assigned supervisor and grant reads of the configured proxy Secret. Refs: ai-openshell#5879 Signed-off-by: Shiju <shiju@nvidia.com>
This branch has not been deployed
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.
Summary
Kubernetes deployments that require an upstream CONNECT proxy currently need a dedicated supervisor Pod per sandbox. This change lets operators use the same upstreamProxy settings with a shared supervisor pool, while applications keep their destination URLs and each sandbox keeps its policy and provider credential bindings.
Related Issue
Closes #5879
Changes
Release Notes
Shared Kubernetes supervisors support upstreamProxy for policy-approved CONNECT egress. Upgrade the gateway and every pool member before enabling the settings. Start a new sandbox generation to pick up changes to proxy settings, credentials, or CA trust.
Testing
Checklist