How to create a TLS/SSL certificate with a Cert-Manager and Let's Encrypt in Azure AKS? | AKS

[@mathijsmillenaar8839]

Thanks!

[@GauravSharma-os6ds]

Hey Nirav, Glad to see you creating such an informative tutorials. Cloud you please make a video on Applicateway as AKS ingress controller, Its in high in demand.

[@Niravgandhi]

I'll keep that in mind for a future video.

[@ThePalominojuan]

Hi Gandhi, I am following your kubernetes tutorial and I have a problem after finishing all the steps and reviewing the description of the cert-manager I get the following error "Issuing certificate as Secret does not exist aks" I have reviewed documentation but the solutions I have found do not solve the problem,Thank you Gandhi.

[@Niravgandhi]

How can I help

[@Charles-it7fg]

Hi Nirav! Thanks for this video. I have a slightly different use case that requires using Azure Key Vault as cert manager. How would you approach this?

[@chetanrokade5156]

Hi Nirav, In Ingress object, under tls, we defined secretName: tls-secret -- Is this default name or we have added this secret?

[@Niravgandhi]

We need to add

[@MohanKumar-k2f6q]

Hi Nirav, I have followed what you have shown in the video but still, it is not working for me.

[@Niravgandhi]

did you add your email account?

[@MohanKumar-k2f6q]

@@Niravgandhi Yes i have added

[@saisivakiran8467]

What will be the content of tls-secret?

[@Niravgandhi]

I think, base 64, needs to check

[@bryantlan7092]

Hi Nirav, nice content, do you know if there's a way to configure the tls version (e.g. use tls 1.2 over tls 1.0) for the ingress controller?

[@Niravgandhi]

Yes, you can configure the TLS version for an ingress controller to ensure it uses a specific version like TLS 1.2 over TLS 1.0. The configuration process depends on the specific ingress controller you are using. kubectl edit configmap -n ingress-nginx nginx-configuration data: ssl-protocols: "TLSv1.2 TLSv1.3"

[@Shubhm1517]

Nirav, Could you please suggest me any Sandbox where I can do all this(Pod/Node/Ingress/etc creation).

[@Niravgandhi]

K3s

[@Shubhm1517]

@@Niravgandhi Thanks Nirav.

[@poshakj]

what if the certificates are expired, how can we renew the certificates with cert manager?

[@Niravgandhi]

Automatically renew

[@karanjoshi8220]

How to use this in a private AKS cluster?

[@Niravgandhi]

Use key valult

[@karanjoshi8220]

@@Niravgandhi Thanks, I was looking for this.

[@rojabujji5021]

Hi @KaranJoshi8220 I am also using private AKS cluster any reference repo you have

[@chetanrokade5156]

Thanks Sir..Really helpful playlist.

[@Niravgandhi]

Most welcome

[@srinivas1623]

Pls do some monitoring tools grafana and prometheus Thank you Gandihi

[@Niravgandhi]

Next week

[@rojabujji5021]

Would you please provide github reference

[@deva_2022]

if you add the commands and yml file github page and links of the pages you used . it would be better

[@Niravgandhi]

I will do it

[@deva_2022]

@@Niravgandhi thank u

[@TheFesk98]

could you please be more consistent? you are mixing up certificate and secret many times. also why your certificate is an Ingress? Why not Certificate? Why did you not explain this?

[@Niravgandhi]

Not getting you. Please convert into question and send. My certificate is not ingress. Ingress in name space

[@TheFesk98]

@@Niravgandhi your file called certi.yaml is of kind Ingress, not of kind Certificate, why is that?

[@Niravgandhi]

Yes .got it .will rename file

[@Niravgandhi]

@@TheFesk98 it's just file .. i will rename, it should be ingress.yaml

[@TheFesk98]

I meant that: I usually know it s a good practice to not use the TLS in the Ingress resource, but apply a Certificate resource after you apply the ClusterIssuer and configure your TLS secret and cert-provider through a separate resource, but I figured out that what you did is the equivalent method