Deployed 6ecfc62 to v2.6 with MkDocs 1.1.2 and mike 1.0.0

kubernetes-sigs · Oct 30, 2023 · 213b20a · 213b20a
1 parent 4a2957b
commit 213b20a
Show file tree

Hide file tree

Showing 36 changed files with 1,969 additions and 78 deletions.
diff --git a/latest/guide/use_cases/frontend_sg/index.html b/latest/guide/use_cases/frontend_sg/index.html
@@ -0,0 +1,16 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta charset="utf-8">
+  <title>Redirecting</title>
+  <noscript>
+    <meta http-equiv="refresh" content="1; url=../../../../v2.6/guide/use_cases/frontend_sg/" />
+  </noscript>
+  <script>
+    window.location.replace("../../../../v2.6/guide/use_cases/frontend_sg/");
+  </script>
+</head>
+<body>
+  Redirecting to <a href="../../../../v2.6/guide/use_cases/frontend_sg/">../../../../v2.6/guide/use_cases/frontend_sg/</a>...
+</body>
+</html>
diff --git a/v2.6/404.html b/v2.6/404.html
@@ -801,6 +801,18 @@
 
 
 
+
+
+
+
+    <li class="md-nav__item">
+      <a href="/guide/use_cases/frontend_sg/" class="md-nav__link">
+        Frontend Security Groups
+      </a>
+    </li>
+
+
+
         </ul>
       </nav>
     </li>

diff --git a/v2.6/CONTRIBUTING/index.html b/v2.6/CONTRIBUTING/index.html
@@ -806,6 +806,18 @@
 
 
 
+
+
+
+
+    <li class="md-nav__item">
+      <a href="../guide/use_cases/frontend_sg/" class="md-nav__link">
+        Frontend Security Groups
+      </a>
+    </li>
+
+
+
         </ul>
       </nav>
     </li>
@@ -991,7 +1003,7 @@ <h1 id="contributing-guidelines">Contributing Guidelines<a class="headerlink" hr
 <p><em>As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.</em></p>
 <h2 id="getting-started">Getting Started<a class="headerlink" href="#getting-started" title="Permanent link">&para;</a></h2>
 <h3 id="building-the-project">Building the project<a class="headerlink" href="#building-the-project" title="Permanent link">&para;</a></h3>
-<p><a href="/docs/controller-devel.md">Controller developement documentation</a> has instructions on how to build the project and project specific expectations.</p>
+<p><a href="/docs/controller-devel.md">Controller development documentation</a> has instructions on how to build the project and project specific expectations.</p>
 <h3 id="contributing-to-docs">Contributing to docs<a class="headerlink" href="#contributing-to-docs" title="Permanent link">&para;</a></h3>
 <p>The <a href="https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/">documentation</a> is generated using <a href="https://squidfunk.github.io/mkdocs-material/">Material for MkDocs</a>. In order to generate and preview docs locally, use the steps below -</p>
 <ul>

diff --git a/v2.6/code-of-conduct/index.html b/v2.6/code-of-conduct/index.html
@@ -806,6 +806,18 @@
 
 
 
+
+
+
+
+    <li class="md-nav__item">
+      <a href="../guide/use_cases/frontend_sg/" class="md-nav__link">
+        Frontend Security Groups
+      </a>
+    </li>
+
+
+
         </ul>
       </nav>
     </li>

diff --git a/v2.6/controller-devel/index.html b/v2.6/controller-devel/index.html
@@ -806,6 +806,18 @@
 
 
 
+
+
+
+
+    <li class="md-nav__item">
+      <a href="../guide/use_cases/frontend_sg/" class="md-nav__link">
+        Frontend Security Groups
+      </a>
+    </li>
+
+
+
         </ul>
       </nav>
     </li>

diff --git a/v2.6/deploy/configurations/index.html b/v2.6/deploy/configurations/index.html
@@ -939,6 +939,18 @@
 
 
 
+
+
+
+
+    <li class="md-nav__item">
+      <a href="../../guide/use_cases/frontend_sg/" class="md-nav__link">
+        Frontend Security Groups
+      </a>
+    </li>
+
+
+
         </ul>
       </nav>
     </li>
@@ -1435,6 +1447,18 @@ <h2 id="controller-command-line-flags">Controller command line flags<a class="he
 <td>Maximum duration of exponential backoff for targetGroupBinding reconcile failures</td>
 </tr>
 <tr>
+<td>tolerate-non-existent-backend-service</td>
+<td>boolean</td>
+<td>true</td>
+<td>Whether to allow rules which refer to backend services that do not exist</td>
+</tr>
+<tr>
+<td>tolerate-non-existent-backend-action</td>
+<td>boolean</td>
+<td>true</td>
+<td>Whether to allow rules which refer to backend actions that do not exist</td>
+</tr>
+<tr>
 <td>watch-namespace</td>
 <td>string</td>
 <td></td>

diff --git a/v2.6/deploy/installation/index.html b/v2.6/deploy/installation/index.html
@@ -465,6 +465,13 @@
     Additional requirements for non-EKS clusters:
   </a>
 
+</li>
+
+          <li class="md-nav__item">
+  <a href="#additional-requirements-for-isolated-cluster" class="md-nav__link">
+    Additional requirements for isolated cluster:
+  </a>
+
 </li>
 
           <li class="md-nav__item">
@@ -959,6 +966,18 @@
 
 
 
+
+
+
+
+    <li class="md-nav__item">
+      <a href="../../guide/use_cases/frontend_sg/" class="md-nav__link">
+        Frontend Security Groups
+      </a>
+    </li>
+
+
+
         </ul>
       </nav>
     </li>
@@ -1094,6 +1113,13 @@
     Additional requirements for non-EKS clusters:
   </a>
 
+</li>
+
+          <li class="md-nav__item">
+  <a href="#additional-requirements-for-isolated-cluster" class="md-nav__link">
+    Additional requirements for isolated cluster:
+  </a>
+
 </li>
 
           <li class="md-nav__item">
@@ -1234,6 +1260,9 @@ <h3 id="additional-requirements-for-non-eks-clusters">Additional requirements fo
 <li>Ensure subnets are tagged appropriately for auto-discovery to work</li>
 <li>For IP targets, pods must have IPs from the VPC subnets. You can configure the <a href="https://github.com/aws/amazon-vpc-cni-k8s#readme"><code>amazon-vpc-cni-k8s</code></a> plugin for this purpose.</li>
 </ul>
+<h3 id="additional-requirements-for-isolated-cluster">Additional requirements for isolated cluster:<a class="headerlink" href="#additional-requirements-for-isolated-cluster" title="Permanent link">&para;</a></h3>
+<p>Isolated clusters are clusters without internet access, and instead reply on VPC endpoints for all required connects.
+When installing the AWS LBC in isolated clusters, you need to disable shield, waf and wafv2 via controller flags <code>--enable-shield=false, --enable-waf=false, --enable-wafv2=false</code></p>
 <h3 id="using-the-amazon-ec2-instance-metadata-server-version-2-imdsv2">Using the Amazon EC2 instance metadata server version 2 (IMDSv2)<a class="headerlink" href="#using-the-amazon-ec2-instance-metadata-server-version-2-imdsv2" title="Permanent link">&para;</a></h3>
 <p>We recommend blocking the access to instance metadata by requiring the instance to use <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html">IMDSv2</a> only. For more information, please refer to the AWS guidance <a href="https://aws.github.io/aws-eks-best-practices/security/docs/iam/#restrict-access-to-the-instance-profile-assigned-to-the-worker-node">here</a>. If you are using the IMDSv2, set the hop limit to 2 or higher in order to allow the LBC to perform the metadata introspection. </p>
 <p>You can set the IMDSv2 as follows:
@@ -1281,13 +1310,13 @@ <h3 id="option-a-recommended-iam-roles-for-service-accounts-irsa">Option A: Reco
 <li>
 <p>Download an IAM policy for the LBC using one of the following commands:<p>
     If your cluster is in a US Gov Cloud region:
-    <div class="highlight"><pre><span></span><code>curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.0/docs/install/iam_policy_us-gov.json
+    <div class="highlight"><pre><span></span><code>curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.1/docs/install/iam_policy_us-gov.json
 </code></pre></div>
     If your cluster is in a China region:
-    <div class="highlight"><pre><span></span><code>curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.0/docs/install/iam_policy_cn.json
+    <div class="highlight"><pre><span></span><code>curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.1/docs/install/iam_policy_cn.json
 </code></pre></div>
     If your cluster is in any other region:
-    <div class="highlight"><pre><span></span><code>curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.0/docs/install/iam_policy.json
+    <div class="highlight"><pre><span></span><code>curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.1/docs/install/iam_policy.json
 </code></pre></div></p>
 </li>
 <li>
@@ -1313,7 +1342,7 @@ <h3 id="option-a-recommended-iam-roles-for-service-accounts-irsa">Option A: Reco
 </ol>
 <h3 id="option-b-attach-iam-policies-to-nodes">Option B: Attach IAM policies to nodes<a class="headerlink" href="#option-b-attach-iam-policies-to-nodes" title="Permanent link">&para;</a></h3>
 <p>If you're not setting up IAM roles for service accounts, apply the IAM policies from the following URL at a minimum. Please be aware of the possibility that the controller permissions may be assumed by other users in a pod after retrieving the node role credentials, so the best practice would be using IRSA instead of attaching IAM policy directly.
-<div class="highlight"><pre><span></span><code>curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.0/docs/install/iam_policy.json
+<div class="highlight"><pre><span></span><code>curl -o iam-policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.6.1/docs/install/iam_policy.json
 </code></pre></div></p>
 <p>The following IAM permissions subset is for those using <code>TargetGroupBinding</code> only and don't plan to use the LBC to manage security group rules:</p>
 <div class="highlight"><pre><span></span><code>{
@@ -1340,6 +1369,7 @@ <h3 id="option-b-attach-iam-policies-to-nodes">Option B: Attach IAM policies to
 <h2 id="network-configuration">Network configuration<a class="headerlink" href="#network-configuration" title="Permanent link">&para;</a></h2>
 <p>Review the <a href="https://docs.aws.amazon.com/eks/latest/userguide/sec-group-reqs.html">worker nodes security group</a> docs. Your node security group must permit incoming traffic on TCP port 9443 from the Kubernetes control plane. This is needed for webhook access.</p>
 <p>If you use <a href="https://eksctl.io/usage/vpc-networking/">eksctl</a>, this is the default configuration.</p>
+<p>If you use custom networking, please refer to the <a href="https://aws.github.io/aws-eks-best-practices/networking/custom-networking/#use-custom-networking-when">EKS Best Practices Guides</a> for network configuration.</p>
 <h2 id="add-controller-to-cluster">Add controller to cluster<a class="headerlink" href="#add-controller-to-cluster" title="Permanent link">&para;</a></h2>
 <p>We recommend using the Helm chart to install the controller. The chart supports Fargate and facilitates updating the controller.</p>
 <div class="tabbed-set" data-tabs="1:2"><input checked="checked" id="__tabbed_1_1" name="__tabbed_1" type="radio" /><label for="__tabbed_1_1">Helm</label><div class="tabbed-content">
@@ -1353,7 +1383,8 @@ <h3 id="summary">Summary<a class="headerlink" href="#summary" title="Permanent l
 </code></pre></div></li>
 <li>
 <p>If upgrading the chart via <code>helm upgrade</code>, install the <code>TargetGroupBinding</code> CRDs.
-<div class="highlight"><pre><span></span><code>kubectl apply -k &quot;github.com/aws/eks-charts/stable/aws-load-balancer-controller//crds?ref=master&quot;
+<div class="highlight"><pre><span></span><code>wget https://raw.githubusercontent.com/aws/eks-charts/master/stable/aws-load-balancer-controller/crds/crds.yaml
+kubectl apply -f crds.yaml
 </code></pre></div></p>
 <div class="admonition tip">
 <p class="admonition-title">Tip</p>
@@ -1375,7 +1406,7 @@ <h3 id="install-cert-manager">Install <code>cert-manager</code><a class="headerl
 <h3 id="apply-yaml">Apply YAML<a class="headerlink" href="#apply-yaml" title="Permanent link">&para;</a></h3>
 <ol>
 <li>Download the spec for the LBC.
-<div class="highlight"><pre><span></span><code>wget https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.6.0/v2_6_0_full.yaml
+<div class="highlight"><pre><span></span><code>wget https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.6.1/v2_6_1_full.yaml
 </code></pre></div></li>
 <li>Edit the saved yaml file, go to the Deployment spec, and set the controller <code>--cluster-name</code> arg value to your EKS cluster name
 <div class="highlight"><pre><span></span><code>apiVersion: apps/v1
@@ -1389,20 +1420,20 @@ <h3 id="apply-yaml">Apply YAML<a class="headerlink" href="#apply-yaml" title="Pe
         spec:
             containers:
                 - args:
-                    - --cluster-name=&lt;INSERT_CLUSTER_NAME&gt;
+                    - --cluster-name=&lt;your-cluster-name&gt;
 </code></pre></div></li>
 <li>If you use IAM roles for service accounts, we recommend that you delete the <code>ServiceAccount</code> from the yaml spec. If you delete the installation section from the yaml spec, deleting the <code>ServiceAccount</code> preserves the <code>eksctl</code> created <code>iamserviceaccount</code>.
 <div class="highlight"><pre><span></span><code>apiVersion: v1
 kind: ServiceAccount
 </code></pre></div></li>
 <li>Apply the yaml file
-<div class="highlight"><pre><span></span><code>kubectl apply -f v2_6_0_full.yaml
+<div class="highlight"><pre><span></span><code>kubectl apply -f v2_6_1_full.yaml
 </code></pre></div></li>
 <li>Optionally download the default ingressclass and ingressclass params
-<div class="highlight"><pre><span></span><code>wget https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.6.0/v2_6_0_ingclass.yaml
+<div class="highlight"><pre><span></span><code>wget https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/download/v2.6.1/v2_6_1_ingclass.yaml
 </code></pre></div></li>
 <li>Apply the ingressclass and params
-<div class="highlight"><pre><span></span><code>kubectl apply -f v2_6_0_ingclass.yaml
+<div class="highlight"><pre><span></span><code>kubectl apply -f v2_6_1_ingclass.yaml
 </code></pre></div></li>
 </ol>
 </div>

diff --git a/v2.6/deploy/pod_readiness_gate/index.html b/v2.6/deploy/pod_readiness_gate/index.html
@@ -878,6 +878,18 @@
 
 
 
+
+
+
+
+    <li class="md-nav__item">
+      <a href="../../guide/use_cases/frontend_sg/" class="md-nav__link">
+        Frontend Security Groups
+      </a>
+    </li>
+
+
+
         </ul>
       </nav>
     </li>
-Original file line number
+Diff line change
@@ Expand Up / @@ -801,6 +801,18 @@ @@
+        <li class="md-nav__item">
+          <a href="/guide/use_cases/frontend_sg/" class="md-nav__link">
+            Frontend Security Groups
+          </a>
+        </li>
             </ul>
           </nav>
         </li>
@@ Expand Down @@