Skip to content

Commit a0e332a

Browse files
committed
Update documentation for cronjob removal and Istio CA certificate plugin.
1 parent 74d2a66 commit a0e332a

File tree

1 file changed

+1
-30
lines changed

1 file changed

+1
-30
lines changed

support/azure/azure-kubernetes/extensions/istio-add-on-plug-in-ca-certificate.md

Lines changed: 1 addition & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ This article discusses common troubleshooting issues with the Istio add-on plug-
4242

4343
- For the cluster to auto-detect changes in the Azure Key Vault secrets, you have to enable [auto-rotation](/azure/aks/csi-secrets-store-configuration-options#enable-and-disable-auto-rotation) for the Azure Key Vault secrets provider add-on.
4444

45-
- Although changes to the intermediate certificate are applied automatically, changes to the root certificate are only picked up by the control plane after the `istiod` deployment is restarted by a cronjob that the add-on deploys, as explained in the [Deployed resources](#deployed-resources) section. This cronjob runs at a 10-minute interval.
45+
- Changes to the root and intermediate certificates are applied automatically.
4646

4747
## Enable the Istio add-on to use a plug-in CA certificate
4848

@@ -118,35 +118,6 @@ As part of the add-on deployment for the plug-in certificates feature, the follo
118118
-----END CERTIFICATE-----
119119
```
120120

121-
- The `istio-cert-validator-cronjob-asm-1-21` [cronjob object](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/) is created in the `aks-istio-system` namespace. This cronjob is scheduled to run every 10 minutes to check for updates on the root certificate. If the root certificate that's in the `cacerts` Kubernetes secret doesn't match the `istio-ca-root-cert` configmap in the `aks-istio-system` namespace, it restarts the `istiod-asm-1-21` deployment:
122-
123-
```bash
124-
kubectl get cronjob --namespace aks-istio-system
125-
```
126-
127-
```output
128-
NAME SCHEDULE SUSPEND ACTIVE
129-
istio-cert-validator-cronjob-asm-1-21 */10 * * * * False 0
130-
```
131-
132-
You can run the following command to check the cronjob logs for the last run:
133-
134-
```bash
135-
kubectl logs --namespace aks-istio-system $(kubectl get pods --namespace aks-istio-system | grep 'istio-cert-validator-cronjob-' | sort -k8 | tail -n 1 | awk '{print $1}')
136-
```
137-
138-
This command generates one of the following output messages, depending on whether a root certificate update was detected:
139-
140-
```output
141-
Root certificate update not detected.
142-
```
143-
144-
```output
145-
Root certificate update detected. Restarting deployment...
146-
deployment.apps/istiod-asm-1-21 restarted
147-
Deployment istiod-asm-1-21 restarted.
148-
```
149-
150121
## Determine certificate type in deployment logs
151122

152123
You can view the `istiod` deployment logs to determine whether you have a self-signed CA certificate or a plug-in CA certificate. To view the logs, run the following command:

0 commit comments

Comments
 (0)