-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failed reading secret "cert-manager": resource name may not be empty #8
Labels
good first issue
Good for newcomers
Comments
晚上好,我检查了你的 apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
name: ali-letsencrypt-staging
spec:
acme:
server: https://acme-staging-v02.api.letsencrypt.org/directory
email: xxxxxx
privateKeySecretRef:
name: ali-letsencrypt-staging
solvers:
- dns01:
webhook:
groupName: xxxxxx
solverName: alidns
config:
region: "cn-beijing"
accessKeySecretRef: # ** 这里应该是 accessKeyIdRef **
name: alidns
key: access-key-id
secretKeySecretRef:
name: alidns
key: access-key-secret |
遇到了同样的问题把 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
pod/alidns-webhook-68f86c46c4-jw72j 每 2 分钟报这个 E1230
目标是在 kube-prometheus-stack namespace 中创建 ingress-nginx。
k8s 版本 v1.27.8
执行代码如下:
在 kube-prometheus-stack、cert-manager 两个namespace 均有创建 secret
ClusterIssuer 如下:
在 kube-prometheus-stack namespace 创建 ingress
在创建 ingress 的同时,会自动创建名字为 grafana-ali-letsencrypt-staging 的 Certificate。
Certificate 的 SECRET 是 grafana-ali-letsencrypt-staging。
但 READY 状态是 False。
kube-prometheus-stack namespace 下也自动创建了名字为 grafana-ali-letsencrypt-staging-2ddsj 的 secret。
不知道为何 pod 要读 cert-manager 这个 secret,这个 secret 名字是如何传进去的。
我曾把 Secret 的名字由 alidns 改为了 cert-manager,但还是会报相同的错误。
The text was updated successfully, but these errors were encountered: