Deploying with a Custom Resource Definition

Once the operator is installed, the Kubernetes API servers becomes aware of the Kubernetes customer resource (CR). The installation process registers the:

CR
API for managing the CR
Controller that handles the requests, for the CR, from the API Server

To instantiate the CR:

Click View Operator on the page displayed immediately after the operator is installed.
Alternatively:
1. Expand “Operators” section and click Installed Operators page from the left hand bar on the page.
2. Click on the Name of the operator installed.
3. Click Create Instance link on the page displayed.
4. Click Create to deploy CTE for Kubernetes.

Deploying with a Custom Resource Definition

You can deploy CTE for Kubernetes using a Custom Resource Definition (CRD). The following displays a sample CRD used to create an instance of the CTE for Kubernetes:

CTE-K8S-Operator-crd.yaml

    apiVersion: cte-k8s-operator.csi.cte.cpl.thalesgroup.com/v1
    kind: CteK8sOperator
    metadata:
        labels:
            app.kubernetes.io/name: ctek8soperator
            app.kubernetes.io/instance: ctek8soperator
            app.kubernetes.io/part-of: cte-k8s-operator
            app.kubernetes.io/managed-by: kustomize
            app.kubernetes.io/created-by: cte-k8s-operator
        name: ctek8soperator
    spec:
        replicas: 1
        image: "docker.io/thalesciphertrust/ciphertrust-transparent-encryption-kubernetes"
        version: "1.2.0-latest"
        imagePullPolicy: Always
        logLevel: 5
        apiburst: 300
        apiqps: 200
        imagePullSecrets:
            - name: cte-csi-secret
        registrationCleanupInterval: 10
        pauseimage: "k8s.gcr.io/pause:latest"
        volumes:
          - name: cri-sock
          hostPath:
            path: "/run/crio/crio.sock"
        # The following parameters are optional. If values are not specified, CTE-K8s uses the default values
        csiProvisionerImage: registry.k8s.io/sig-storage/csi-provisioner:v4.0.0
        csiNodeDriverRegistrarImage: k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.0.1
        csiAttacherImage: k8s.gcr.io/sig-storage/csi-attacher:v3.3.0
        csiSnapshotterImage: registry.k8s.io/sig-storage/csi-snapshotter:v6.3.3
        snapImagePullPolicy: IfNotPresent

Applying a CRD

To apply the CRD, type:

    kubectl apply –f `<path to\cte-k8s-operator.yaml>`

Suggest A Change

Deploying with a Custom Resource Definition

Deploying with a Custom Resource Definition

Applying a CRD

On this page