Add documentation

Author: cPu1

userdocs/src/usage/addon-upgrade.md

@@ -1,5 +1,12 @@
 # Default add-on updates
 
+!!! warning "New for 2024"
+    eksctl now installs default addons as EKS addons instead of self-managed addons. Read more about its implications in [Cluster creation flexibility for default networking addons](#cluster-creation-flexibility-for-default-networking-addons).
+
+!!! warning "New for 2024"
+    For updating addons, `eksctl utils update-*` cannot be used for clusters created with eksctl v0.184.0 and above.
+    This guide is only valid for clusters created before this change.
+
 There are 3 default add-ons that get included in each EKS cluster:
 - `kube-proxy`
 - `aws-node`

userdocs/src/usage/addons.md

@@ -6,6 +6,12 @@ CNI plugin through the EKS API
 
 ## Creating addons (and providing IAM permissions via IRSA)
 
+!!! tip "New for 2024"
+    eksctl now supports creating clusters without any default networking addons: [Cluster creation flexibility for default networking addons](#cluster-creation-flexibility-for-default-networking-addons).
+
+!!! warning "New for 2024"
+    eksctl now installs default addons as EKS addons instead of self-managed addons. Read more about its implications in [Cluster creation flexibility for default networking addons](#cluster-creation-flexibility-for-default-networking-addons).
+
 !!! tip "New for 2024"
     EKS Add-ons now support receiving IAM permissions, required to connect with AWS services outside of cluster, via [EKS Pod Identity Associations](/usage/pod-identity-associations/#eks-add-ons-support-for-pod-identity-associations)
 
@@ -87,8 +93,8 @@ addons:
 
 For addon create, the `resolveConflicts` field supports three distinct values:
 
-- `none` - EKS doesn't change the value. The create might fail. 
-- `overwrite` - EKS overwrites any config changes back to EKS default values. 
+- `none` - EKS doesn't change the value. The create might fail.
+- `overwrite` - EKS overwrites any config changes back to EKS default values.
 - `preserve` - EKS doesn't change the value. The create might fail. (Similarly to `none`, but different from [`preserve` in updating addons](#updating-addons))
 
 ## Listing enabled addons
@@ -141,7 +147,7 @@ eksctl utils describe-addon-configuration --name vpc-cni --version v1.12.0-eksbu
 This returns a JSON schema of the various options available for this addon.
 
 ## Working with configuration values
-`ConfigurationValues` can be provided in the configuration file during the creation or update of addons. Only JSON and YAML formats are supported. 
+`ConfigurationValues` can be provided in the configuration file during the creation or update of addons. Only JSON and YAML formats are supported.
 
 For eg.,
 
@@ -202,10 +208,10 @@ addons:
   resolveConflicts: preserve
 ```
 
-For addon update, the `resolveConflicts` field accepts three distinct values: 
+For addon update, the `resolveConflicts` field accepts three distinct values:
 
 - `none` - EKS doesn't change the value. The update might fail.
-- `overwrite` - EKS overwrites any config changes back to EKS default values. 
+- `overwrite` - EKS overwrites any config changes back to EKS default values.
 - `preserve` - EKS preserves the value. If you choose this option, we recommend that you test any field and value changes on a non-production cluster before updating the add-on on your production cluster.
 
 ## Deleting addons
@@ -216,3 +222,48 @@ eksctl delete addon --cluster <cluster-name> --name <addon-name>
 This will delete the addon and any IAM roles associated to it.
 
 When you delete your cluster all IAM roles associated to addons are also deleted.
+
+## Cluster creation flexibility for default networking addons
+
+When a cluster is created, EKS automatically installs VPC CNI, CoreDNS and kube-proxy as self-managed addons.
+To disable this behavior in order to use other CNI plugins like Cilium and Calico, eksctl now supports creating a cluster
+without any default networking addons. To create such a cluster, set `addonsConfig.disableDefaultAddons`, as in:
+
+```yaml
+addonsConfig:
+  disableDefaultAddons: true
+```
+
+```shell
+$ eksctl create cluster -f cluster.yaml
+```
+
+To create a cluster with only CoreDNS and kube-proxy and not VPC CNI, specify the addons explicitly in `addons`
+and set `addonsConfig.disableDefaultAddons`, as in:
+
+```yaml
+addonsConfig:
+  disableDefaultAddons: true
+addons:
+  - name: kube-proxy
+  - name: coredns
+```
+
+```shell
+$ eksctl create cluster -f cluster.yaml
+```
+
+As part of this change, eksctl now installs default addons as EKS addons instead of self-managed addons during cluster creation
+if `addonsConfig.disableDefaultAddons` is not explicitly set to true. As such, `eksctl utils update-*` commands can no
+longer be used for updating addons for clusters created with eksctl v0.184.0 and above:
+
+- `eksctl utils update-aws-node`
+- `eksctl utils update-coredns`
+- `eksctl utils update-kube-proxy`
+
+Instead, `eksctl update addon` should be used now.
+
+To learn more, see [EKS documentation][eksdocs].
+
+
+[eksdocs]: https://aws.amazon.com/about-aws/whats-new/2024/06/amazon-eks-cluster-creation-flexibility-networking-add-ons/

userdocs/theme/main.html

@@ -6,11 +6,18 @@
     <code>eksctl</code> is now fully maintained by AWS. For more details check out
     <a class="announce" href="https://github.com/aws/containers-roadmap/issues/2280">eksctl Support Status Update</a>.
   </p>
+  <p style="text-align: center;">
+    <code>eksctl</code> now supports <a href="/usage/addons/#cluster-creation-flexibility-for-default-networking-addons">Cluster creation flexibility for networking add-ons</a>.
+  </p>
+  <p style="text-align: center;">
+    <code>eksctl</code> now installs default addons as EKS addons instead of self-managed addons. To understand its implications, check out
+    <a href="/usage/addons/#cluster-creation-flexibility-for-default-networking-addons">Cluster creation flexibility for networking add-ons</a>.
+  </p>
 {% endblock %}
 
 
 {% block scripts %}
   <!-- Add scripts that need to run before here -->
   {{ super() }}
 
-{% endblock %}
+{% endblock %}