[GH-ISSUE #883] [Feature] Support additional annotations when k8s deploy #601

New issue

Closed

opened 2026-03-03 01:04:36 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 01:04:36 +03:00

Owner

Originally created by @whg517 on GitHub (Jul 21, 2025).
Original GitHub issue: https://github.com/certimate-go/certimate/issues/883

功能描述 / Description

When deploying certificates to k8s, it is supported to configure additional annotations or labels.

For example, I would like to deploy the certificate in the "default" namespace and add the "kubernetes-replicator" annotation to the certificate, so that the replicator can automatically synchronize the secret to other namespaces.

请求动机 / Motivation

In the k8s environment, if a wildcard domain certificate is applied for, it can be used for the ingresses of multiple namespaces. However, the current deployment pipeline can only be configured to deploy to a single namespace of Kubernetes.

The Kubernetes-replicator tool in the community can dynamically synchronize the specified secret to the target namespace based on the annotations of the secret. This triggering rule is accomplished by configuring annotations in this secret.

Now, the certificate is deployed into the k8s secret. It supports configuration of the namespace and the secret name, but annotations or labels cannot be configured.

It is hoped that this function can be added.

其他 / Miscellaneous

No response

贡献 / Contribution

我乐意为此贡献 PR！ / I am interested in contributing a PR for this!

Originally created by @whg517 on GitHub (Jul 21, 2025). Original GitHub issue: https://github.com/certimate-go/certimate/issues/883 ### 功能描述 / Description When deploying certificates to k8s, it is supported to configure additional annotations or labels. For example, I would like to deploy the certificate in the "default" namespace and add the "kubernetes-replicator" annotation to the certificate, so that the replicator can automatically synchronize the secret to other namespaces. ### 请求动机 / Motivation In the k8s environment, if a wildcard domain certificate is applied for, it can be used for the ingresses of multiple namespaces. However, the current deployment pipeline can only be configured to deploy to a single namespace of Kubernetes. The Kubernetes-replicator tool in the community can dynamically synchronize the specified secret to the target namespace based on the annotations of the secret. This triggering rule is accomplished by configuring annotations in this secret. Now, the certificate is deployed into the k8s secret. It supports configuration of the namespace and the secret name, but annotations or labels cannot be configured. It is hoped that this function can be added. ### 其他 / Miscellaneous _No response_ ### 贡献 / Contribution - [x] 我乐意为此贡献 PR！ / I am interested in contributing a PR for this!