Deploy the archiva helm chart on Kubernetes

Question

Pulumi · Accepted Answer

Deploying the Archiva Helm chart on a Kubernetes cluster using Pulumi is a multi-step process that involves:

1. Setting up a Kubernetes cluster (if not already available).
2. Installing and configuring Helm, and the Helm chart for Archiva.
3. Deploying the Helm chart to the Kubernetes cluster.

For the purpose of this guide, I'll assume that you already have a Kubernetes cluster running and accessible through your `kubectl` command-line tool. If you need to create a Kubernetes cluster, you can do so using Pulumi's EKS, AKS, or GKE resources, depending on your cloud provider of choice.

In this program, we will use the `kubernetes.helm.v3.Chart` resource from the `@pulumi/kubernetes` package to deploy the Archiva Helm chart onto the Kubernetes cluster.

Below is a complete Pulumi program written in TypeScript, which deploys the Archiva Helm chart:

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

// The name of the Helm chart you wish to deploy.
const chartName = "archiva";
// The repository where the Archiva Helm chart is hosted.
const chartRepo = "https://helm.alfresco.com/stable";
// The version of the Archiva Helm chart you wish to install.
const chartVersion = "1.0.0"; // Replace with the actual chart version you want to use.

// Create a Helm chart resource, using the Chart resource class.
const archivaHelmChart = new k8s.helm.v3.Chart(chartName, {
    chart: chartName,
    version: chartVersion,
    fetchOpts: {
        repo: chartRepo,
    },
    // Specify any custom values you'd like to use for the Archiva Helm chart.
    values: {
        // These values are placeholders and may not be the actual values you need.
        // They are here to illustrate how you can customize your Helm chart configuration.
        // Please refer to the Archiva Helm chart's documentation for configurable options.
        service: {
            type: "LoadBalancer",
        },
        // You can add more custom configuration according to the chart's values.yaml.
    },
});

// To access the resulting service, you can use archivaHelmChart.getResource <k8s.core.v1.Service>() or similar methods.
// For example, to export the load balancer URL, you can write code similar to the following, adjusted to your needs:
const service = archivaHelmChart.getResource("v1/Service", "archiva");
export const archivaUrl = service.status.loadBalancer.ingress[0].hostname;

```

Here's what the above program is doing:

- It imports the necessary `@pulumi/kubernetes` package to work with Kubernetes resources.
- It defines the name, repository, and version of the Archiva Helm chart you want to deploy.
- It then creates an instance of the `Chart` resource, which Pulumi uses to interact with Helm. It specifies the chart name, version, and repository URL, along with any custom `values` you wish to provide, which would override the chart's default values.
- Lastly, the program attempts to export the URL of the Archiva application if the service type is set to be a LoadBalancer. Please note that the specific field you'll need to access may vary based on the actual Helm chart and your Kubernetes configuration.

Remember, the custom `values` will depend on the actual Helm chart for Archiva you are trying to deploy. You would need to look at the `values.yaml` within the Archiva Helm chart or the documentation provided with the chart to know what options you have for customization.

The last part of the program is designed to potentially export the URL of the Archiva service. You'll need to adjust it based on your cluster's service configuration.

To run this Pulumi program, save it as `index.ts` in a new Pulumi project. You can create a new Pulumi project by running `pulumi new` in your command line and choosing the appropriate template. After you've created your project and saved this program, run `pulumi up` to execute the deployment. Pulumi will show you a preview of the actions it will take and, upon confirmation, will apply those actions to deploy the Archiva Helm chart to your cluster.