1. Deploy the tyk-dev-portal helm chart on Oracle Kubernetes Engine (OKE)


    To deploy the tyk-dev-portal Helm chart on Oracle Kubernetes Engine (OKE), we'll carry out the following steps:

    1. Set Up OKE Cluster: We'll initialize an OKE cluster. Pulumi's oci.ContainerEngine.Cluster is an abstraction that represents a Kubernetes cluster in OKE, where you can deploy your applications.

    2. Install Helm on the Cluster: The kubernetes.helm.v3.Chart resource from the Kubernetes provider is a high-level abstraction that allows you to deploy Helm charts in a Kubernetes cluster.

    3. Deploy the Helm Chart: With the OKE Cluster and Helm set up, we will deploy the tyk-dev-portal chart. You will need the Helm chart information, like its repository and version.

    Here is a complete Pulumi program written in TypeScript that performs these steps:

    import * as oci from "@pulumi/oci"; import * as k8s from "@pulumi/kubernetes"; // Create an Oracle Kubernetes Engine (OKE) cluster const okeCluster = new oci.ContainerEngine.Cluster("okeCluster", { // Specify the necessary properties for your OKE cluster; for example: compartmentId: "<compartment-id>", // Replace with the OCID of the compartment vcnId: "<vcn-id>", // Replace with your VCN ID in OCI kubernetesVersion: "v1.21.5", // Specify the Kubernetes version to use name: "tyk-dev-portal-cluster", // The name of your cluster // ... additional options as per your requirements }); // Obtain the kubeconfig file from the generated OKE cluster // This will authenticate the Kubernetes provider with the cluster const kubeconfig = okeCluster.kubeConfig. /* property to get kubeconfig */; // Check the OKE cluster object for the correct property // Set up the Kubernetes provider with the obtained kubeconfig const k8sProvider = new k8s.Provider("k8sProvider", { kubeconfig: kubeconfig, }); // Deploy the `tyk-dev-portal` Helm chart using the Kubernetes provider const tykDevPortalChart = new k8s.helm.v3.Chart("tykDevPortalChart", { chart: "tyk-dev-portal", // The name of the Helm chart version: "<chart-version>", // Specify the version of the chart you want to deploy repositoryOpts: { repo: "https://helm.tyk.io/public/helm/charts/", // The Helm repository URL where `tyk-dev-portal` is hosted }, // Define any custom values you want to pass into your Helm chart values: { // ...Provide the required values needed by tyk-dev-portal chart as per your needs }, }, { provider: k8sProvider }); // Export the URL of the deployed tyk-dev-portal instance export const tykDevPortalUrl = "http://..."; // Construct or obtain the URL to access the tyk-dev-portal using the service's LoadBalancer or Ingress

    In this program, you'll need to replace the placeholders such as <compartment-id>, <vcn-id>, <chart-version>, and any values specific to the 'tyk-dev-portal' Helm chart with actual values based on your OKE and Helm chart configuration.

    Also, adjust tykDevPortalUrl at the end to correctly reflect the service access point, which typically would be the Ingress URL or a LoadBalancer IP.


    • Make sure your OCI credentials are configured correctly to allow Pulumi to manage resources in your Oracle Cloud Infrastructure account.
    • Typically, the Helm repository URL is provided by the Helm chart documentation. Ensure you use the correct repository for the tyk-dev-portal chart.
    • You will likely need additional customization of values to configure tyk-dev-portal properly. The required values will be documented in the Helm chart's documentation.

    After the Pulumi program runs successfully, it will create the OKE cluster and deploy the tyk-dev-portal helm chart into it. Access to the Tyk Developer Portal can be setup through the various services (like LoadBalancer or Ingress) as per the Helm chart's outputs and documentation.