MirtoBusico commented on issue #235:
URL: 
https://github.com/apache/apisix-helm-chart/issues/235#issuecomment-1038345433


   @tokers 
   Well maybe I don't understand the documentation
   
   I created a generic secret using these commands:
   ```
   sysop@m01serv:~/m01certs$ cd ~/m01certs
   sysop@m01serv:~/m01certs$ ls -lh m01ca.*
   -rw-r--r-- 1 root root 1,7K gen 17 18:43 m01ca.key
   -rw-r--r-- 1 root root 1,5K gen 17 18:46 m01ca.pem
   -rw-r--r-- 1 root root   41 feb 11 14:01 m01ca.srl
   sysop@m01serv:~/m01certs$ kubectl -n kube-system create secret generic 
m01cacert --from-file=cert=./m01ca.pem
   secret/m01cacert created
   sysop@m01serv:~/m01certs$ kubectl describe secret m01cacert -n kube-system
   Name:         m01cacert
   Namespace:    kube-system
   Labels:       <none>
   Annotations:  <none>
   
   Type:  Opaque
   
   Data
   ====
   cert:  1464 bytes
   sysop@m01serv:~/m01certs$ 
   ```
   Then I modified the values.yaml file in the apisix helm chart:
   ```
     tls:
       enabled: true
       servicePort: 443
       containerPort: 9443
       existingCASecret: "m01cacert"
       certCAFilename: "cert"
       http2:
         enabled: true
   ```
   Then I installed apisix with:
   ```
   kubectl create ns apisix
   kubectl label namespace apisix istio-injection=enabled
   helm install apisix apisix/apisix -f apisix-values.yaml \
   --set ingress-controller.config.apisix.serviceNamespace=apisix \
   --set ingress-controller.config.apisix.serviceName=apisix-admin \
   --namespace apisix
   ```
   Now the apisix pod never starts saying
   ```
   MountVolume.SetUp failed for volume "ssl" : secret "m01cacert" not found
   ```
   
   <img width="1849" alt="apisix-m01cacert" 
src="https://user-images.githubusercontent.com/11090934/153770172-06ba5461-b66e-4b87-9d60-b5e7f67e10ff.png";>
   
   What I'm doing wrong?
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to