apisix-ingress-controller
apisix-ingress-controller copied to clipboard
request help: webhook-registration.yaml
Issue description
apiVersion: admissionregistration.k8s.io/v1 kind: ValidatingWebhookConfiguration metadata: name: apisix-validations labels: app: apisixroute-plugin-validator-webhook kind: validating webhooks:
- name: apisixroute.plugin.validator.webhook
clientConfig:
service:
name: apisix-admission-server
namespace: ingress-apisix
port: 8443
path: "/validation/apisixroutes/plugin"
caBundle: ${CA_BUNDLE}
rules:
- operations: [ "CREATE", "UPDATE" ] apiGroups: ["apisix.apache.org"] apiVersions: ["*"] resources: ["apisixroutes"] timeoutSeconds: 30 failurePolicy: Ignore sideEffects: None admissionReviewVersions: ["v1", "v1beta1"]
kubectl apply -f webhook-registration.yaml
Error from server (BadRequest): error when creating "webhook-registration.yaml": ValidatingWebhookConfiguration in version "v1" cannot be handled as a ValidatingWebhookConfiguration: v1.ValidatingWebhookConfiguration.Webhooks: []v1.ValidatingWebhook: v1.ValidatingWebhook.ClientConfig: v1.WebhookClientConfig.Service: CABundle: decode base64: illegal base64 data at input byte 0, error found in #10 byte of ...|A_BUNDLE}","service"|..., bigger context ...|1beta1"],"clientConfig":{"caBundle":"${CA_BUNDLE}","service":{"name":"apisix-admission-server","name|...
Environment
- your apisix-ingress-controller version (output of apisix-ingress-controller version --long):
- your Kubernetes cluster version (output of kubectl version):
- if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):
You can refer to this file https://github.com/apache/apisix-ingress-controller/blob/master/test/e2e/testdata/webhook-create-signed-cert.sh
If you want to use admissionregistration.k8s.io/v1
, please ensure your kubernetes cluster is at least as new as v1.16
In addition, please add a description when submitting an issue next time, so that it can be more clear
thanks
This issue has been marked as stale due to 90 days of inactivity. It will be closed in 30 days if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the [email protected] list. Thank you for your contributions.
This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.