1. Deploy the apicurio-registry-streams helm chart on AWS EKS


    To deploy the Apicurio Registry Helm chart on an AWS EKS cluster, we'll proceed with the following steps:

    1. Create an EKS cluster using the eks.Cluster component from the pulumi/eks package. This will allow us to create a managed Kubernetes cluster on AWS. The EKS cluster will handle the orchestration of the Kubernetes nodes where your applications will be deployed.

    2. Use the kubernetes.helm.v3.Chart resource from the @pulumi/kubernetes package to deploy the Apicurio Registry streams Helm chart onto the EKS cluster. Helm charts are collections of pre-configured Kubernetes resources that can be deployed as a unit.

    Here's a program written in TypeScript that carries out these steps:

    import * as eks from "@pulumi/eks"; import * as k8s from "@pulumi/kubernetes"; import * as pulumi from "@pulumi/pulumi"; // Create an EKS cluster. const cluster = new eks.Cluster("myCluster", { // Specify the desired number and types of instances for the node group. desiredCapacity: 2, minSize: 1, maxSize: 3, instanceType: "t3.medium", // Choose an appropriate instance type. }); // Once the cluster is created, obtain the 'kubeconfig' we will use to communicate with the cluster. const kubeConfig = cluster.kubeconfig.apply(JSON.stringify); // Create a Kubernetes provider instance that uses our EKS cluster's kubeconfig. const clusterProvider = new k8s.Provider("myClusterProvider", { kubeconfig: kubeConfig, }); // Deploy the Apicurio Registry streams Helm chart to the EKS cluster. const apicurioRegistry = new k8s.helm.v3.Chart("apicurioRegistry", { chart: "apicurio-registry-streams", version: "1.0.0", // Specify the Helm chart version you want to deploy. fetchOpts:{ repo: "https://helm.apicur.io" // This URL is where the chart repository is located. }, }, { provider: clusterProvider }); // Export the cluster's kubeconfig and the Apicurio Registry's endpoint to access the application. export const kubeconfigOutput = cluster.kubeconfig; export const apicurioRegistryEndpoint = cluster.getKubernetesEndpoint();

    In this program:

    • We instantiate an EKS cluster with a node group configuration that specifies the desired number of EC2 instances and the instance types suitable for our workload.

    • We deploy the Apicurio Registry using a Helm chart with its repository URL, and we bind this deployment to the clusterProvider, which is associated with our EKS cluster.

    • We export the kubeconfig, which would be used to connect and manage the Kubernetes cluster with tools like kubectl.

    • We also export the endpoint for Apicurio Registry services deployed on the cluster, which can be used to access the Apicurio Registry UI or API.

    Please replace the chart version with the specific version you wish to deploy if 1.0.0 is not correct, and make sure to set the access permissions and networking options for your EKS cluster as per your requirements.

    You need to have Pulumi installed and configured with your AWS account to run this code. The deployment can be initiated using the Pulumi CLI with the usual commands pulumi up to create or update resources and pulumi destroy to remove them.