feat(helm): update chart metrics-server to 3.12.2

[chii-bot]

This PR contains the following updates:

Package	Update	Change
metrics-server	minor	3.8.2 -> 3.12.2

---

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Renovate Bot.

[chii-bot]

Path: cluster/apps/kube-system/metrics-server/helm-release.yaml
Version: 3.8.2 -> 3.12.2

@@ -4,6 +4,7 @@
 kind: ServiceAccount
 metadata:
 name: metrics-server
+ namespace: default
 labels:
 app.kubernetes.io/name: metrics-server
 app.kubernetes.io/instance: metrics-server
@@ -120,6 +121,7 @@
 kind: Service
 metadata:
 name: metrics-server
+ namespace: default
 labels:
 app.kubernetes.io/name: metrics-server
 app.kubernetes.io/instance: metrics-server
@@ -131,6 +133,7 @@
 port: 443
 protocol: TCP
 targetPort: https
+ appProtocol: https
 selector:
 app.kubernetes.io/name: metrics-server
 app.kubernetes.io/instance: metrics-server
@@ -140,6 +143,7 @@
 kind: Deployment
 metadata:
 name: metrics-server
+ namespace: default
 labels:
 app.kubernetes.io/name: metrics-server
 app.kubernetes.io/instance: metrics-server
@@ -162,13 +166,18 @@
 - name: metrics-server
 securityContext:
 allowPrivilegeEscalation: false
+ capabilities:
+ drop:
+ - ALL
 readOnlyRootFilesystem: true
 runAsNonRoot: true
 runAsUser: 1000
- image: k8s.gcr.io/metrics-server/metrics-server:v0.6.1
+ seccompProfile:
+ type: RuntimeDefault
+ image: registry.k8s.io/metrics-server/metrics-server:v0.7.2
 imagePullPolicy: IfNotPresent
 args:
- - --secure-port=4443
+ - --secure-port=10250
 - --cert-dir=/tmp
 - --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname
 - --kubelet-use-node-status-port
@@ -181,7 +190,7 @@
 ports:
 - name: https
 protocol: TCP
- containerPort: 4443
+ containerPort: 10250
 livenessProbe:
 failureThreshold: 3
 httpGet:
@@ -201,6 +210,10 @@
 volumeMounts:
 - name: tmp
 mountPath: /tmp
+ resources:
+ requests:
+ cpu: 100m
+ memory: 200Mi
 volumes:
 - name: tmp
 emptyDir: {}
@@ -221,6 +234,7 @@
 service:
 name: metrics-server
 namespace: default
+ port: 443
 version: v1beta1
 versionPriority: 100
 ---
@@ -229,12 +243,13 @@
 kind: ServiceMonitor
 metadata:
 name: metrics-server
+ namespace: default
 labels:
 app.kubernetes.io/name: metrics-server
 app.kubernetes.io/instance: metrics-server
 app.kubernetes.io/managed-by: Helm
 spec:
- jobLabel: metrics-server
+ jobLabel: app.kubernetes.io/instance
 namespaceSelector:
 matchNames:
 - default

[chii-bot]

MegaLinter status: ❌ ERROR

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
❌ COPYPASTE	jscpd	yes		2	0.9s
✅ REPOSITORY	git_diff	yes		no	0.02s
✅ REPOSITORY	secretlint	yes		no	1.18s
✅ YAML	prettier	1		0	0.51s
✅ YAML	yamllint	1		0	0.12s

See errors details in artifact MegaLinter reports on CI Job page
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.