We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I followed the steps in https://imroc.cc/k8s/trick/cert-manager-webhook-dnspod/ , but got an error below.
error decoding solver config: json: cannot unmarshal number into Go struct field customDNSProviderConfig.secretId of type string
And found the value of secretId in clusterissuers.cert-manager.io/dnspod is not a string type.
The text was updated successfully, but these errors were encountered:
一直是 string,正常情况不会报错。具体 ClusterIssuer 的 yaml 以及 webhook 的 deployment yaml 是什么?
Sorry, something went wrong.
I followed the steps in https://imroc.cc/k8s/trick/cert-manager-webhook-dnspod/ , but got an error below. error decoding solver config: json: cannot unmarshal number into Go struct field customDNSProviderConfig.secretId of type string And found the value of secretId in clusterissuers.cert-manager.io/dnspod is not a string type.
我也遇到了这个问题,不过最后发现问题了。这里的secretid 和secretkey 是腾讯云(qcloud.com)的 。不能用dnspod的 appid和 token。
I followed the steps in https://imroc.cc/k8s/trick/cert-manager-webhook-dnspod/ , but got an error below. error decoding solver config: json: cannot unmarshal number into Go struct field customDNSProviderConfig.secretId of type string And found the value of secretId in clusterissuers.cert-manager.io/dnspod is not a string type. 我也遇到了这个问题,不过最后发现问题了。这里的secretid 和secretkey 是腾讯云(qcloud.com)的 。不能用dnspod的 appid和 token。
我当时的确使用了腾讯云的密钥,只是生成 yaml 的时候类型错误了
No branches or pull requests
I followed the steps in https://imroc.cc/k8s/trick/cert-manager-webhook-dnspod/ , but got an error below.
And found the value of secretId in clusterissuers.cert-manager.io/dnspod is not a string type.
The text was updated successfully, but these errors were encountered: