Deploy the kubernetes-dashboard-proxy helm chart on Kubernetes

Question

Pulumi · Accepted Answer

To deploy the Kubernetes Dashboard along with an ingress proxy using Helm through Pulumi, we will use the `kubernetes.helm.v3.Chart` resource from Pulumi Kubernetes provider. This resource allows you to deploy Helm charts into your Kubernetes cluster. Helms charts are collections of pre-configured Kubernetes resources.

The Helm chart for the Kubernetes Dashboard is a pre-packaged set of Kubernetes resources that installs and configures the Kubernetes Dashboard. The ingress proxy is typically configured as part of the values passed into the Helm chart, which might include setup for an Ingress resource or service of type LoadBalancer to expose the Dashboard.

Here is a program that demonstrates how to do this. Before running this code, make sure you have a Kubernetes cluster available and `kubectl` is configured correctly with the necessary privileges. You will also need to have Helm installed and Pulumi set up to run TypeScript programs.

```typescript
import * as k8s from "@pulumi/kubernetes";

// Name of the namespace where you want to deploy the Kubernetes Dashboard
const dashboardNamespace = new k8s.core.v1.Namespace("kubernetes-dashboard-namespace", {
    metadata: {
        name: "kubernetes-dashboard",
    },
});

// Values for the Kubernetes Dashboard Helm Chart
const dashboardValues = {
    // These values depend on the Helm chart and your specific requirements.
    // For example, you may want to enable ingress, RBAC, set service account name, etc.
    // Check the Helm chart's `values.yaml` for all available options.
    ingress: {
        enabled: true,
        annotations: {
            "kubernetes.io/ingress.class": "nginx",
        },
        paths: ["/"]
    },
};

// Deploy the Kubernetes Dashboard using a Helm Chart
const kubernetesDashboard = new k8s.helm.v3.Chart("kubernetes-dashboard", {
    namespace: dashboardNamespace.metadata.name,
    chart: "kubernetes-dashboard",
    // Use the Helm repo URL where the chart is located
    // The URL is just an example, use the correct one for your case
    fetchOpts: {
        repo: "https://kubernetes.github.io/dashboard/",
    },
    values: dashboardValues,
});

// Export the namespace and ingress endpoint
export const dashboardNs = dashboardNamespace.metadata.name;
export const ingressEndpoint = kubernetesDashboard.getResourceProperty("v1/Service", "kubernetes-dashboard", "status").apply(status => status.loadBalancer.ingress[0].ip);

```

When you run this program with Pulumi (`pulumi up`), it will create a new namespace for the Kubernetes Dashboard if it doesn't exist, and deploy the Helm chart for the Kubernetes Dashboard into that namespace. The `dashboardValues` object is where you would specify any custom configuration for the Dashboard and its ingress proxy. In this case, it's setup to configure an Ingress resource.

The `ingressEndpoint` export will give you the load balancer IP address or hostname you can use to access your Kubernetes Dashboard after the Helm chart has been successfully deployed. This will only work if your Kubernetes cluster supports LoadBalancer service types and Ingress resources properly.

Remember to customize the `chart` and `repo` fields based on the Helm Chart you are using. This example uses a placeholder URL, you need to replace it with the URL where your actual kubernetes-dashboard chart is located. Additionally, any specific customizations you need can be added to the `dashboardValues` object; these are specific to each Helm chart and can be found within the chart's `values.yaml` file.

If you do not have the Ingress controller set up already (like NGINX Ingress Controller) in your cluster, you may need to install it first; otherwise, the Ingress resource won't work.