Conversation
…load Identity Replace invalid config.useWorkloadIdentityExtension with the correct managedIdentity.clientID field in azureDNS solver spec. Also remove clientID and tenantID as direct azureDNS fields in the private issuer as they are not valid cert-manager spec fields for any auth method.
… Principal for Azure Add azure.useWorkloadIdentity (default: true) to allow switching between Workload Identity (managedIdentity.clientID) and Service Principal (clientID + tenantID + clientSecretSecretRef) auth methods.
violenti
approved these changes
Mar 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
config.useWorkloadIdentityExtension: truewith correctmanagedIdentity.clientIDinazureDNSsolver spec (both public and private ClusterIssuer)clientIDandtenantIDdirect fields fromazureDNSin the private issuer — those fields don't exist in cert-manager's spec for any auth methodazure.useWorkloadIdentity(default:true) to support both Workload Identity and Service Principal auth methodsWhy
config.useWorkloadIdentityExtensionis not a valid field in cert-manager'sazureDNSspec. Any cluster using this had a ClusterIssuer that failed silently to issue certificates. The correct approach per cert-manager docs ismanagedIdentity.clientID.Compatibility
{{- if eq .Values.cloudProvider "azure" }}useWorkloadIdentity: true, default): usesmanagedIdentity.clientID— requires cert-manager >= 1.8useWorkloadIdentity: false): usesclientID+tenantID+clientSecretSecretRef— requiresazure.clientSecret.secretNameto be setazure.clientIDis now required whencloudProvider=azure— previously the field existed invalues.yamlbut was unused in the public issuer, causing silent failuresTest plan
Ready: True, ACME account registeredReady: True, ACME account registered