Changes the k8s Container name from 'kgateway' to 'controller' #13232
Conversation
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
This name is not prominent in the docs or in users' minds because typically the controller Deployment's Pods have only one Container and you therefore do not need to name it in your 'kubectl' commands. Makes envoy & agentgateway data plane controllers consistent with one another. Signed-off-by: David L. Chandler <[email protected]>
gateway-bot
added
kind/cleanup
Signed-off-by: David L. Chandler <[email protected]>
Signed-off-by: David L. Chandler <[email protected]>
npolshakova
approved these changes
Jan 8, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Description
Makes envoy & agentgateway data plane controllers consistent with one another.
This name is not prominent in the docs or in users' minds. Typically the controller Deployment's Pods, even on Istio classic meshes, have only one Container and you therefore do not need to name it in your
kubectlcommands. If you were used to saying something likekubectl logs -n kgateway-system deploy/kgateway -c kgateway, then it will have to change tokubectl logs -n kgateway-system deploy/kgateway -c controller.Change Type
/kind cleanup
Changelog
Additional Notes