Open PRAJINPRAKASH opened 1 year ago
did you figure this out? i have the same exact issue
Have you tried creating a ClusterRole and a ClusterRoleBinding like someone else stated online here
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: dns-challenge-missing-role
rules:
- apiGroups: ["acme.amprajin.in"] # "" indicates the core API group
resources: ["godaddy"]
verbs: ["*"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: dns-challenge-missing-role-binding
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: dns-challenge-missing-role
subjects:
- kind: ServiceAccount
name: cert-manager
namespace: cert-manager
Can we close this ticket if you have been able to resolve it ? @PRAJINPRAKASH
This error happens when installing godaddy-webhook using the kubectl apply -f ...
method. The cert-manager.yaml have the string acme.mycompany.com
hard-coded for the groupName
. What you have to do is download that file and replace that value with the value you want.
OR
Install it using Helm with helm upgrade --install -n cert-manager godaddy-webhook godaddy-webhook/godaddy-webhook --set groupName=acme.YOURCOMPANY.com
Can you propose a PR to improve the readme file of this project to warn the user and propose solutions as you suggested ? @ckt114
Error presenting challenge: godaddy.acme.amprajin.in is forbidden: User "system:serviceaccount:cert-manager:cert-manager" cannot create resource "godaddy" in API group "acme.amprajin.in" at the cluster scope