You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then deploy ClusterIssuer using a second ClusterProfile
apiVersion: config.projectsveltos.io/v1alpha1kind: ClusterProfilemetadata:
name: clusterissuerspec:
dependsOn:
- cert-managerclusterSelector: env=fvsyncMode: ContinuousWithDriftDetectionpolicyRefs:
- name: clusterissuernamespace: defaultkind: ConfigMap
---
apiVersion: v1kind: ConfigMapmetadata:
name: clusterissuernamespace: defaultdata:
clusterissuer.yaml: | apiVersion: cert-manager.io/v1 kind: ClusterIssuer metadata: name: cloudflare namespace: cert-manager spec: acme: email: raspberry-pi@home.pi server: https://acme-staging-v02.api.letsencrypt.org/directory privateKeySecretRef: # Secret resource that will be used to store the account's private key. name: example-issuer-account-key # Add a single challenge solver, HTTP01 using nginx solvers: - http01: ingress: class: nginx
Cert-manager is deployed and so is ClusterIssuer.
Now change ClusterProfile cert-manager so it does not match anymore. Cert-manager and ClusterIssuer CRD will be removed (and so all ClusetrIssuers instance).
Drift-detect-manager detects the drift, but fails to report to the management cluster.
I0612 10:39:59.221556 1 drift_evaluation.go:38] "Evaluating Configuration drift"I0612 10:39:59.225888 1 drift_evaluation.go:52] "Evaluating resource for configuration drift" resource="/cloudflare" gvk="cert-manager.io/v1, Kind=ClusterIssuer"E0612 10:39:59.240108 1 drift_evaluation.go:55] "failed to evaluate resource" err="no matches for kind \"ClusterIssuer\" in version \"cert-manager.io/v1\"" resource="/cloudflare" gvk="cert-manager.io/v1, Kind=ClusterIssuer"I0612 10:39:59.240141 1 drift_evaluation.go:65] "requeuing resource for evaluation" resource="/cloudflare" gvk="cert-manager.io/v1, Kind=ClusterIssuer"
The text was updated successfully, but these errors were encountered:
Deploy cert-manager
Then deploy ClusterIssuer using a second ClusterProfile
Cert-manager is deployed and so is ClusterIssuer.
Now change ClusterProfile cert-manager so it does not match anymore. Cert-manager and ClusterIssuer CRD will be removed (and so all ClusetrIssuers instance).
Drift-detect-manager detects the drift, but fails to report to the management cluster.
The text was updated successfully, but these errors were encountered: