Automated Metrics Server version update 0.9.0 - #6060
Conversation
replicated-ci-kurl
added
automated-pr
kurl::type::feature
|
Reviews (1): Last reviewed commit: "Create new Metrics Server version" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| - --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 |
2 participants
Automated changes by the cron-metrics-server-update GitHub action