Automated Metrics Server version update 0.9.0 - #6060
Conversation
|
Reviews (1): Last reviewed commit: "Create new Metrics Server version" | Re-trigger Greptile |
| - --secure-port=10250 | ||
| - --kubelet-insecure-tls | ||
| - --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname | ||
| - --kubelet-use-node-status-port |
There was a problem hiding this comment.
The kustomize patch replaces the Deployment container args list, so the rendered 0.9.0 deployment loses the base manifest's --metric-resolution=15s flag. Any kURL install using this version with the insecure kubelet TLS patch will run metrics-server with its binary default resolution instead of the upstream manifest value.
| - --kubelet-use-node-status-port | |
| - --kubelet-use-node-status-port | |
| - --metric-resolution=15s |
| apiVersion: kustomize.config.k8s.io/v1beta1 | ||
| kind: Kustomization | ||
| patches: | ||
| - path: kubelet-insecure-tls.yaml |
There was a problem hiding this comment.
The addon system expects a per-version testgrid spec under the new version directory, but this version only adds the install assets. With no per-version test spec, the changed metrics-server package can be skipped by the addon change matrix, so broken packaging or install behavior can merge without the normal addon test run.
Knowledge Base Used: Addons System
be41e8f to
70fe866
Compare
|
Reviews (2): Last reviewed commit: "Create new Metrics Server version" | Re-trigger Greptile |
70fe866 to
bf6712f
Compare
|
Reviews (3): Last reviewed commit: "Create new Metrics Server version" | Re-trigger Greptile |
bf6712f to
d8c65f5
Compare
|
Reviews (4): Last reviewed commit: "Create new Metrics Server version" | Re-trigger Greptile |
|
Reviews (5): Last reviewed commit: "empty commit to trigger CI" | Re-trigger Greptile |
|
Testgrid Run(s) Executing @ https://testgrid.kurl.sh/run/pr-6060-71309ef-metrics-server-0.9.0-k8s-docker-2026-08-17T23:07:54Z |
Automated changes by the cron-metrics-server-update GitHub action