add crossplane bootstrap

kind/crossplane-complete/templates/7-eks-cluster-xr.yaml

@@ -32,6 +32,9 @@ spec:
     workload-type: "non-gpu"
     workers-size: 2
 
+    cluster-role: "arn:aws:iam::597766473323:role/EKS-Cluster-Role"
+    workernode-role: "arn:aws:iam::597766473323:role/EKS-Cluster-Role"
+
   compositionRef:
     name: amazon-eks-cluster
 

kind/crossplane.sh

+##!/bin/bash
+
+#
+# The Crossplane CLI extends kubectl with functionality to build, push, and install Crossplane packages
+#
+curl -sL https://raw.githubusercontent.com/crossplane/crossplane/release-1.0/install.sh | sh
+sudo mv kubectl-crossplane /usr/local/bin
+
+# In order to authenticate with the external provider API such as AWS, the provider controllers need to have access to credentials. 
+# It could be an IAM User for AWS
+# An AWS user with Administrative privileges is needed to enable Crossplane to create the required resources
+# We wil have to first create a configuration file, secrets.conf, with credeantials of an AWS account in the following format.
+#
+# [default]
+# aws_access_key_id =ABCDEFGHIJ0123456789
+# aws_secret_access_key = Ow3HUaP8BbqkV4dUrZr0H7yT5nGP5OPFcZJ+
+#
+# Then using that file, a Kubernetes Secret is created as follows
+#
+kubectl -n crossplane-system create secret generic aws-credentials --from-file=credentials=./secrets.conf
+
+# Push this package to a repository in an image registry
+#
+cd eks-ressource/eks-configuration
+kubectl crossplane build configuration
+kubectl crossplane push configuration IMAGE_REPO:IMAGE_TAG
+
+# Here are a set of CLI commands to look at various resources 
+#
+kubectl get crossplane  # get all resources related to Crossplane.
+kubectl get managed     # get all resources that represent a unit of external infrastructure such as RDSInstance.
+kubectl get composite   # get all resources that represent an XR
+
+