Adding EKS Adon Example for Upbound

examples/aws-provider/README.md

@@ -41,37 +41,6 @@ kubectl apply -f managed-resources/vpc.yaml
 kubectl get VPC aws-provider-vpc
 ```
 
-## Authenticate with an existing EKS Cluster using AWS Provider
-
-The following shows an example of how to authenticate and retrieve `kubeconfig` from an existing remote EKS Cluster using AWS Provider
-
-```shell
-# Please make sure to replace `<your-cluster-name>` with your EKS cluster name in the below file before applying.
-kubectl apply -f managed-resources/eks-clusterauth.yaml
-
-# Verify the resource. When authentication is complete, you should see READY: True in the output.
-kubectl get clusterauths.eks.aws.upbound.io
-
-NAME                               READY   SYNCED   EXTERNAL-NAME                      AGE
-eks-x86-us-east-2-1-28-blueprint   True    True     eks-x86-us-east-2-1-28-blueprint   11d
-
-# Verify if the secret has pulled the `kubeconfig` of a remote cluster to management cluster.
-kubectl describe secret eks-x86-us-east-2-1-28-eks-connection -n upbound-system
-
-Name:         eks-x86-us-east-2-1-28-eks-connection
-Namespace:    upbound-system
-Labels:       <none>
-Annotations:  <none>
-
-Type:  connection.crossplane.io/v1alpha1
-
-Data
-====
-clusterCA:   1107 bytes
-endpoint:    72 bytes
-kubeconfig:  4314 bytes
-```
-
 ## Crossplane Kubernetes Provider
 
 The following example shows the creation of Namespace with Crossplane Kuberentes provider

examples/upbound-aws-provider/README.md

@@ -35,6 +35,52 @@ kubectl create -f managed-resources/s3/bucket.yaml
 kubectl get buckets
 ```
 
+## Authenticate with an existing EKS Cluster using upbound AWS Provider
+
+The following shows an example of how to authenticate and retrieve `kubeconfig` from an existing remote EKS Cluster using AWS Provider
+
+```shell
+# Please make sure to replace `<your-cluster-name>` with your EKS cluster name in the below file before applying.
+kubectl apply -f managed-resources/eks/eks-clusterauth.yaml
+
+# Verify the resource. When authentication is complete, you should see READY: True in the output.
+kubectl get clusterauths.eks.aws.upbound.io
+
+NAME                               READY   SYNCED   EXTERNAL-NAME                      AGE
+eks-x86-us-east-2-1-28-blueprint   True    True     eks-x86-us-east-2-1-28-blueprint   11d
+
+# Verify if the secret has pulled the `kubeconfig` of a remote cluster to management cluster.
+kubectl describe secret eks-x86-us-east-2-1-28-eks-connection -n upbound-system
+
+Name:         eks-x86-us-east-2-1-28-eks-connection
+Namespace:    upbound-system
+Labels:       <none>
+Annotations:  <none>
+
+Type:  connection.crossplane.io/v1alpha1
+
+Data
+====
+clusterCA:   1107 bytes
+endpoint:    72 bytes
+kubeconfig:  4314 bytes
+```
+
+### Deploys an EKS Addon for Upbound AWS Provider
+
+The following shows an example of how to deploy an EKS Addon on an EKS Cluster from a management EKS Cluster using Upbound AWS Provider
+
+```shell
+# Please make sure to replace `<your-cluster-name>` with your EKS cluster name in the below file before applying.
+kubectl create -f managed-resources/eks/eks-addon.yaml
+
+# Verify the resource. When provisioning is complete, you should see READY: True in the output
+kubectl get addon.eks.aws.upbound.io -A
+
+NAME             READY   SYNCED   EXTERNAL-NAME                              AGE
+vpc-cni          True    True     eks-x86-us-east-2-1-28-blueprint:vpc-cni   12d
+```
+
 ## Deploy the examples
 
 - [sqs-lambda-s3](composite-resources/serverless-examples/sqs-lambda-s3/README.md)

examples/upbound-aws-provider/managed-resources/eks/eks-addon.yaml

@@ -0,0 +1,13 @@
+apiVersion: eks.aws.upbound.io/v1beta1
+kind: Addon
+metadata:
+  annotations:
+    meta.upbound.io/example-id: eks/v1beta1/addon
+  name: vpc-cni
+spec:
+  forProvider:
+    addonName: vpc-cni
+    clusterName: <your-cluster-name>
+    region: eu-west-1
+  providerConfigRef:
+    name: default