From a417ccdb9eeee993e3f18fc16eaafba2a5991dec Mon Sep 17 00:00:00 2001 From: owais-rehman Date: Mon, 30 Dec 2024 19:21:28 +0500 Subject: [PATCH] lint correction --- .../expose-applications-to-internet.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/for-developers/how-to-guides/expose-applications-to-internet/expose-applications-to-internet.md b/content/for-developers/how-to-guides/expose-applications-to-internet/expose-applications-to-internet.md index 0c7e76fb..184da311 100644 --- a/content/for-developers/how-to-guides/expose-applications-to-internet/expose-applications-to-internet.md +++ b/content/for-developers/how-to-guides/expose-applications-to-internet/expose-applications-to-internet.md @@ -33,11 +33,11 @@ application: #### Important Details - **Certificate**: - - Instruct Cert-Manager to generate TLS certificates for specific DNS entries. - - Requires: - - `.certificate.secretName`: This is the name of secret that `Certificate` will create. It will contain TLS credentials that will find its utilization in next steps. - - `.certificate.dnsNames`: DNS name for which this certificate will be valid. It can contain wildcard names like `*.example.com` or specific names like `api.example.com`. - - `.certificate.issuerRef.name`: Name of the issuer that this certificate will reference. We have created this issuer in previous steps. + - Instruct Cert-Manager to generate TLS certificates for specific DNS entries. + - Requires: + - `.certificate.secretName`: This is the name of secret that `Certificate` will create. It will contain TLS credentials that will find its utilization in next steps. + - `.certificate.dnsNames`: DNS name for which this certificate will be valid. It can contain wildcard names like `*.example.com` or specific names like `api.example.com`. + - `.certificate.issuerRef.name`: Name of the issuer that this certificate will reference. We have created this issuer in previous steps. ## Step 2: Deploy the Route