Azure-docs: Unknown field "acme" in io.cert-manager.v1alpha2.Certificate.spec

[flashtheman]

There seems to be an error in the the documentation for https://docs.microsoft.com/en-us/azure/aks/ingress-static-ip.

When I run the line

kubectl apply -f certificates.yaml

I get the following error:
error: error validating "certificate.yaml": error validating data: ValidationError(Certificate.spec): unknown field "acme" in io.cert-manager.v1alpha2.Certificate.spec; if you choose to ignore these errors, turn validation off with --validate=false

It seems that the .yaml specification for Certificate has changed and doesn't accept the "acme" part anymore.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 12009c1f-282d-2632-fac0-64b09c432833
• Version Independent ID: 6052d3d4-d295-9340-b16d-4c200e34cd73
• Content: Use ingress controller with static IP - Azure Kubernetes Service
• Content Source: articles/aks/ingress-static-ip.md
• Service: container-service
• GitHub Login: @mlearned
• Microsoft Alias: mlearned

[VikasPullagura-MSFT]

@flashtheman
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

[VikasPullagura-MSFT]

@mlearned
Can you please check and add your comments on this doc update request as applicable.

[khalfan123]

I am getting following error, can someone guide me how to resolve this issue.
error: error validating "certificates.yaml": error validating data: ValidationError(Certificate.spec): unknown field "acme" in io.cert-manager.v1alpha2.Certificate.spec; if you choose to ignore these errors, turn validation off with --validate=false

[CalOmnie]

Turning off validation with the flag provided did the trick for me.

[jperl]

It seems that the field was deprecated https://github.com/jetstack/cert-manager/issues/2761#issuecomment-605879129

[Farzad-Jalali]

Turning off validation with the flag provided did the trick for me.

you are right, thanks you save one day of my life!
I used the --validate=false and the after a few minutes you could see the valid certificate throw your browser! :)

[zr-msft]

Thank you @flashtheman for the feedback!

I've recently updated and tested the article and was not able to reproduce your issue. Please follow up if you are still seeing this issue.

please-close

[bastoune]

I still have the issue. It appears that the main issue is that it uses a deprecated acme field.

Refering to : https://github.com/jetstack/cert-manager/issues/2761#issuecomment-605879129