From 4207b13cd108f7231ef2204fe9f9ae3bb644db5f Mon Sep 17 00:00:00 2001 From: owais-rehman Date: Mon, 10 Feb 2025 13:12:39 +0500 Subject: [PATCH] lint correction --- .../how-to-guides/certificate-management/http01-certs.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/content/for-administrators/how-to-guides/certificate-management/http01-certs.md b/content/for-administrators/how-to-guides/certificate-management/http01-certs.md index 75391276..b2f79029 100644 --- a/content/for-administrators/how-to-guides/certificate-management/http01-certs.md +++ b/content/for-administrators/how-to-guides/certificate-management/http01-certs.md @@ -36,6 +36,9 @@ spec: - **`.spec.dnsNames`**: List of DNS names that you want this certificate to support. - **`.spec.issuerRef.name`**: Name of the cluster issuer that you want to use when creating this certificate. You can confirm value for this field with cluster admin. +!!! note +Avoid modifying/deleting existing certificates as this might cause rate limiting at letsencrypt side. You can read more about this [here](https://letsencrypt.org/docs/rate-limits/) + ### Route ```yaml @@ -63,7 +66,7 @@ spec: ``` !!! note -The way you deploy these resources totally depend on how you want to ship it to cluster. If you want to deploy it with a particular application (which is a common case), then you need to ship it from your app-gitops repo as a part of your application's helm chart. +The way you deploy these resources totally depend on how you want to ship it to cluster. If you want to deploy it with a particular application (which is a common case), then you need to ship it from your `app-gitops` repo as a part of your application's helm chart. ## Step 3: Validation @@ -84,4 +87,4 @@ The way you deploy these resources totally depend on how you want to ship it to 1. Confirm that: - The Route resource is listed. - Its status is Accepted. - - The DNS name and TLS configuration are correct. \ No newline at end of file + - The DNS name and TLS configuration are correct.