Skip to content

Latest commit

 

History

History
91 lines (62 loc) · 2.87 KB

README.md

File metadata and controls

91 lines (62 loc) · 2.87 KB
Raw

Crossplane Blueprint examples

This folder contains examples for deploying AWS resources using the following providers

Pre-requisites:

  • EKS Cluster bootstrap deployment
  • Crossplane deployment in bootstrap cluster
  • ProviderConfig deployment with injected identity

Follow these links to bootstrap the cluster

AWS Provider

The following steps demonstrates VPC example composition deployment with AWS Provider

Deploy Composition and XRD

Deploys VPC Composition file and XRD definition file

kubectl apply -f ../../compositions/aws-provider/vpc

Deploy Application example

Deploys VPC claim resource which uses the above composition.

kubectl apply -f composite-resources/vpc/vpc.yaml

Deploy Managed resource for AWS Provider

The following shows the deployment of VPC using AWS Provider

kubectl apply -f managed-resources/vpc.yaml

# Verify the resource. When provisioning is complete, you should see READY: True in the output
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

# 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

Note: Kubernetes Provider should be deployed as a pre-requisite for this example. Terraform and eksctl bootstrap scripts deploys kubernetes provider in EKS Cluster.

kubectl apply -f ../kubernetes-provider/test-namespace.yaml

# Verify the resource
kubectl get namespaces  

NAME                        STATUS   AGE
crossplane-test-namespace   Active   81s