From c0b0c4fde742dde6bb135ec254095db84c4f540b Mon Sep 17 00:00:00 2001
From: Steven Zamborsky <97125550+stevenzamborsky@users.noreply.github.com>
Date: Thu, 21 Jul 2022 16:34:03 -0400
Subject: [PATCH] Add an "Important Note" regarding EKS CSR approval. (#16406)

---
 .../content/docs/platform/k8s/helm/examples/standalone-tls.mdx  | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/content/docs/platform/k8s/helm/examples/standalone-tls.mdx b/website/content/docs/platform/k8s/helm/examples/standalone-tls.mdx
index b493d80e8..b145f9d23 100644
--- a/website/content/docs/platform/k8s/helm/examples/standalone-tls.mdx
+++ b/website/content/docs/platform/k8s/helm/examples/standalone-tls.mdx
@@ -83,6 +83,8 @@ e is 65537 (0x10001)
 
 3. Create the certificate
 
+   ~> **Important Note:** If you are using EKS, certificate signing requirements have changed.  As per the AWS [certificate signing](https://docs.aws.amazon.com/eks/latest/userguide/cert-signing.html) documentation, EKS version `1.22` and later now requires the `signerName` to be `beta.eks.amazonaws.com/app-serving`, otherwise, the CSR will be approved but the certificate will not be issued.
+
    1. Create a file `${TMPDIR}/csr.yaml` with the following contents:
 
       ```bash