Horus-K opened a new issue, #12790:
URL: https://github.com/apache/apisix/issues/12790

   ### Description
   
   Why doesn't apisix-ingress-controller sync the new certificate to apisix 
after I regenerate the mywhoami.xxx.ai certificate?
   How can I force a certificate update? Business operations cannot be 
interrupted.
   I deployed using config_provider=yaml.
   ```
   helm install apisix \
     --namespace ingress-apisix \
     --create-namespace \
     --set apisix.deployment.role=traditional \
     --set apisix.deployment.role_traditional.config_provider=yaml \
     --set etcd.enabled=false \
     --set ingress-controller.enabled=true \
     --set ingress-controller.config.provider.type=apisix-standalone \
     --set ingress-controller.apisix.adminService.namespace=ingress-apisix \
     --set ingress-controller.gatewayProxy.createDefault=true \
     apisix/apisix
   ```
   
   ```
   apiVersion: cert-manager.io/v1
   kind: Certificate
   metadata:
     name: whoami
     namespace: devops
   spec:
     dnsNames:
       - mywhoami.xxx.ai
     issuerRef:
       group: cert-manager.io
       kind: ClusterIssuer
       name: letsencrypt-apisix
     secretName: mywhoami.xxx.ai
     usages:
       - digital signature
       - key encipherment
   ```
   
   ```
   apiVersion: apisix.apache.org/v2
   kind: ApisixTls
   metadata:
     name: whoami
     namespace: devops
   spec:
     hosts:
       - mywhoami.xxx.ai
     ingressClassName: apisix
     secret:
       name: mywhoami.xxx.ai
       namespace: devops
   ```
   
   
   ### Environment
   
   - APISIX version (run `apisix version`):  3.14.1-ubuntu
   - Operating system (run `uname -a`): 
   - OpenResty / Nginx version (run `openresty -V` or `nginx -V`):
   - etcd version, if relevant (run `curl 
http://127.0.0.1:9090/v1/server_info`):
   - APISIX Dashboard version, if relevant:
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run `luarocks --version`):
   


-- 
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