Unable to build kubernetes objects from release manifest: error validating "" error validating data: [ValidationError(Certificate.spec): unknown field "keyAlgorithm" in io.cert-manager.v1.Certificate.spec
See original GitHub issueI want to deploy a Pulsar Cluster on Kubernetes with TLS enabled. I have followed Pulsar documentation to do this: https://pulsar.apache.org/docs/en/helm-deploy/
I have in advance install cert-manager. It is running well:
kubectl get pods --namespace cert-manager
NAME READY STATUS RESTARTS AGE
cert-manager-76d44b459c-vd8kl 1/1 Running 0 25m
cert-manager-cainjector-9b679cc6-jxm4b 1/1 Running 0 25m
cert-manager-webhook-57c994b6b9-trbtw 1/1 Running 0 25m
I have also prepared the helm release
git clone https://github.com/apache/pulsar-helm-chart
cd pulsar-helm-chart
./scripts/pulsar/prepare_helm_release.sh -n pulsar -k pulsar-mini -c
But when I want to deploy Pulsar cluster using Helm with tls enabled:
helm repo add apache https://pulsar.apache.org/charts
helm repo update
helm install --set initialize=true --set namespace=pulsar --set certs.internal_issuer.enabled=true \
--set tls.enabled=true --set tls.proxy.enabled=true --set tls.broker.enabled=true --set tls.bookie.enabled=true \
--set tls.zookeeper.enabled=true --set tls.autorecovery.enabled=true --set tls.toolset.enabled=true pulsar-mini charts/pulsar
I have that error:
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: error validating "": error validating data: [ValidationError(Certificate.spec): unknown field "keyAlgorithm" in io.cert-manager.v1.Certificate.spec, ValidationError(Certificate.spec): unknown field "keyEncoding" in io.cert-manager.v1.Certificate.spec, ValidationError(Certificate.spec): unknown field "keySize" in io.cert-manager.v1.Certificate.spec, ValidationError(Certificate.spec): unknown field "organization" in io.cert-manager.v1.Certificate.spec]
Does anyone have a solution for this?
In the case I enabled TLS on all the cluster and not additionally on all components, the Pulsar Cluster is deployed but the proxy pod is not present anymore.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:7
Top Results From Across the Web
[GitHub] [pulsar] thalesmg commented on ... - The Mail Archive
... Unable to build kubernetes objects from release manifest: error validating "" error validating data: [ValidationError(Certificate.spec): ...
Read more >unknown field "acme" in io.cert-manager.v1.Certificate.spec
Please, consider read this tutorial about a certificate obtained from ACME with DNS validation in the cert-manager.io documentation.
Read more >API Reference - cert-manager Documentation
ACMEAuthorization contains data returned from the ACME server on an authorization that must be completed in order validate a DNS name on an...
Read more >Upgrading Cert-Manager
Rancher uses cert-manager to automatically generate and renew TLS certificates for HA deployments of Rancher. As of Fall 2019, ...
Read more >Kubernetes Troubleshooting - Fixing Validation Error | Datree.io
yml": error validating data: [ValidationError(Deployment.spec.template.spec.containers[0]): unknown field "names" in io.k8s.api.core.v1.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
After spending a lot of time trying to get this to work, I managed to find an API version that makes
cert-manager
work. Pulsar chart version 2.9.3.I got the same problem as well. Pulsar chart version
2.9.3
, cert-manager chart versionv1.5.4
.