-
Notifications
You must be signed in to change notification settings - Fork 366
Open
Description
Current Behavior
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
Expected Behavior
No response
Error Logs
No response
Steps to Reproduce
After creating ApisixTls, the Secret certificate is updated but not synchronized.
Environment
apisix-ingress-controller:2.0.0-rc5
- APISIX version (run
apisix version): 3.14.1-ubuntu
Metadata
Metadata
Assignees
Labels
No labels