Fix cert-manager Issuer rendering annotations: null and wire documented Certificate annotations/labels

[yugstar]

Summary

Two related fixes in charts/metrics-server/templates/certificate.yaml (only triggered when tls.type=cert-manager):

1. Issuer renders annotations: null (bug)

The Issuer metadata referenced .Values.additionalAnnotations, which does not exist anywhere in values.yaml. So helm template --set tls.type=cert-manager rendered:

kind: Issuer
metadata:
  annotations:
    null

This is the same annotations: null → GitOps OutOfSync footgun that was already fixed for the APIService template in #1752. I removed the broken block (the value never existed, so there is no behavior to preserve).

2. tls.certManager.annotations / tls.certManager.labels were dead values

values.yaml declares tls.certManager.annotations and tls.certManager.labels, and the README documents them as "Add extra annotations/labels to the Certificate resource" — but they were never wired to the Certificate. This applies them (guarded with with), so the documented values actually take effect.

Verification

• helm template --set tls.type=cert-manager → Issuer no longer renders annotations: null (no stray null anywhere).
• --set tls.certManager.annotations.foo=bar --set tls.certManager.labels.team=infra → both now appear on the Certificate.
• Default render otherwise unchanged; helm lint passes.
• Per CONTRIBUTING.md, Chart.yaml is intentionally left unmodified; the change is recorded under CHANGELOG.md [UNRELEASED].

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: yugstar / name: Aman Raj (4930d44, c4ea651)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: yugstar
Once this PR has been reviewed and has the lgtm label, please assign stevehipwell for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• charts/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

This issue is currently awaiting triage.

If metrics-server contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: yugstar
Once this PR has been reviewed and has the lgtm label, please assign stevehipwell for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• charts/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @yugstar!

It looks like this is your first PR to kubernetes-sigs/metrics-server 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/metrics-server has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @yugstar. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.