Using kubernetes argoproj.io with operators.coreos.com

Question

Pulumi · Accepted Answer

To integrate Argoproj, which relates to Kubernetes continuous delivery, with Kubernetes Operators (managed by Operator Lifecycle Manager or OLM), you must handle CustomResourceDefinitions (CRDs) and Namespaces, as these are fundamental resources in a Kubernetes cluster that support custom operators and resources.

To use Argo CD with operators from `operators.coreos.com`, which is part of the Operator Lifecycle Manager (OLM), you'll need to deploy Argo CD itself, and ensure that the necessary CRDs and other resources for the operators are installed in your cluster.

Below is a basic TypeScript program using Pulumi to achieve this. The program includes:

1. Import statements to include necessary Pulumi packages.
2. A Namespace resource, which serves as a way to divide cluster resources between multiple users.
3. A CustomResourceDefinition (CRD) resource, which defines a new, custom object type in your Kubernetes cluster necessary for Argo and OLM.
4. Commentary on some steps required to deploy Argo and OLM resources that are not directly representable as Pulumi resources, like applying raw YAML manifests or referring to helm charts.

As both Argoproj and OLM have several components and configurations, the program focuses on setting the basic requirements. For detailed configurations and setups, you will typically refer to the documentation of each project.

Here's a simplified Pulumi program written in TypeScript:

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

// Initialize a Pulumi project with the appropriate Kubernetes provider configuration.
// Ensure that you're authenticated to your Kubernetes cluster where you want to deploy these resources.

// Create a new Kubernetes Namespace for Argo CD resources
const argoCdNamespace = new k8s.core.v1.Namespace("argocd-namespace", {
    metadata: { 
        name: "argocd" // This is where Argo CD components will reside
    }
});

// CustomResourceDefinition for an Operator managed by OLM
// In a real-world scenario, you would include the definitions of the specific CRDs you're interested in.
const operatorCrd = new k8s.apiextensions.v1.CustomResourceDefinition("operator-crd", {
    metadata: {
        // Typically, OLM Operators have their own set names for CRDs
        name: "clusterserviceversions.operators.coreos.com"
    },
    spec: {
        group: "operators.coreos.com",
        versions: [
            {
                name: "v1alpha1",
                served: true,
                storage: true
            }
        ],
        scope: "Namespaced",
        names: {
            plural: "clusterserviceversions",
            singular: "clusterserviceversion",
            kind: "ClusterServiceVersion",
            shortNames: ["csv"]
        }
    }
});

// The following are dummy placeholders for the actual steps you'd
// take to deploy Argo CD and your desired OLM operators.
// For Argo CD,
// You would typically use the Argo CD Helm chart to deploy it to your cluster.
// For that, you can use Pulumi's Helm integration.

// For OLM Operators,
// You would install them by applying the appropriate Subscription and ClusterServiceVersion objects,
// which you'd define with raw YAML or Helm charts provided by the operator maintainers.

// Remember to check both the Argo project and Operator Lifecycle Manager documentation for detailed instructions.

// Export relevant resources
export const argoCdNamespaceName = argoCdNamespace.metadata.name;
export const operatorCrdName = operatorCrd.metadata.name;
```

This program provides a namespace and CRD which are common prerequisites for working with Kubernetes operators and custom resources, and sets a foundation to start deploying Argo CD and OLM-managed operators.

In the real-world usage, the next steps include:

- Fetching and applying the necessary Helm charts or YAML manifests for deploying Argo CD.
- Installing Operators via OLM by applying their Subscription manifests to the cluster. This will automatically install the necessary CRDs and operator logic on the cluster.

Please note that for a complete setup, one must follow the exact procedures and configurations as detailed in the official documentation of Argo CD and the specific operators you wish to deploy.