Azure DNS ACME Solver Issue

[kstedman9]

Describe the bug:

I am trying to use the ACME DNS01 Solver as part of my ClusterIssuer. My AKS cluster is setup with managedIdentities and the managed identity has the proper role permissions (verified by SysAdmin). When I create the certificate object, the challenge gives me a status of

cert-manager Error presenting challenge: error instantiating azuredns challenge solver: ClientID is not set but neither --cluster-issuer-ambient-credentials nor --issuer-ambient-credentials are set. These are necessary to enable Azure Managed Identities

So even though the default in the code for cluster-issuer-ambient-crednetials is true I set it the flag in the cert-manager deployment just to verify. But obviously when cert-manager gets to that part of the code it is false still so either it is not getting passed in correctly or more likely I am missing something in my setup. This is my only issuer in the cluster so it cannot be using a different issuer.

Steps to reproduce the bug:

Anything else we need to know?:

I did try to upgrade to the v1.6-alpha and use the managedIdentity field to see if that was the problem but I get the same exact error.

Environment details::

• Kubernetes version: 1.20.9
• Cloud-provider/provisioner: Azure
• cert-manager version: 1.5
• Install method: static manifests

/kind bug

[jetstack-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle stale

[rajan2]

@kstedman9 ,

Kindly try with principal ID instead of clientID

[jetstack-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle rotten
/remove-lifecycle stale

[jetstack-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

[jetstack-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

[jetstack-bot]

@jetstack-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.