Conversation
Signed-off-by: TRIVENI206 <trivenireddy206@gmail.com>
Signed-off-by: TRIVENI206 <trivenireddy206@gmail.com>
5c11151 to
095bff1
Compare
| agentgateway: agentgateway | ||
| app.kubernetes.io/name: {{ include "agentgateway.name" . }} | ||
| app.kubernetes.io/instance: {{ .Release.Name }} | ||
| app.kubernetes.io/component: controller |
There was a problem hiding this comment.
Let's add the type to the controller here and in install/helm/kgateway/templates/_helpers.tpl:
| app.kubernetes.io/component: controller | |
| app.kubernetes.io/component: agentgateway-controller |
Signed-off-by: TRIVENI206 <trivenireddy206@gmail.com>
|
Awesome! Just a heads up, you'll need to regen the unit tests with |
Signed-off-by: trivenireddy <triveni@Asus.localdomain>
353fd51 to
5804c28
Compare
|
Thanks for the heads up! I’ve regenerated the deployer golden tests using REFRESH_GOLDEN=true go test ./test/deployer and updated the outputs to include the new component labels. The changes are pushed and CI should be rerunning now. |
|
Looks like there are still some diff failures in the unit tests, maybe try You can run the unit tests locally with |
|
I reran REFRESH_GOLDEN=true go test ./test/deployer after clearing the test cache. |
|
Look at the diff here: https://github.com/kgateway-dev/kgateway/actions/runs/21636858458/job/62368669512?pr=13439 Again, it should be reproducible by running |
Signed-off-by: trivenireddy <triveni@Asus.localdomain>
Description
#motivation
kgateway deployments currently lack a standard label to distinguish controller and gateway (proxy) components.
This makes it difficult to use selector-based features such as podAntiAffinity and topologySpreadConstraints without injecting custom labels.
#what changed
Change Type
/kind feature
#related to the
#13429