Skip to content

Latest commit

 

History

History
141 lines (112 loc) · 4.3 KB

manual-installation.md

File metadata and controls

141 lines (112 loc) · 4.3 KB

Manual installation

Install the Operator manually

Note: If you are running on Google Kubernetes Engine (GKE), please check this first.

In case you dont have a cert-manager, Install the cert-manager v0.15.0+ from the following link:-

https://cert-manager.io/docs/installation/kubernetes/

Install the issuer and certificate

$ kubectl create -f deploy/certificate.yaml

Install the webhook

$ kubectl create -f deploy/webhook.yaml

Install the version map for pravega-operator which contains the list of supported versions and supported upgrade paths for the pravega cluster

$ kubectl create -f  deploy/version_map.yaml

Register the Pravega cluster custom resource definition (CRD).

$ kubectl create -f deploy/crds/pravega.pravega.io_pravegaclusters_crd.yaml

Create the operator role, role binding and service account.

$ kubectl create -f deploy/role.yaml
$ kubectl create -f deploy/role_binding.yaml
$ kubectl create -f deploy/service_account.yaml

Install the operator.

$ kubectl create -f deploy/operator.yaml

Deploying in Test Mode

We can enable test mode on operator by passing an argument -test in operator.yaml file. Check out test mode

containers:
  - name: pravega-operator
    image: pravega/pravega-operator:0.5.0-rc1
    ports:
    - containerPort: 60000
      name: metrics
    command:
    - pravega-operator
    imagePullPolicy: Always
    args: [-test]

Set up LongTermStorage:-

Pravega requires a long term storage provider known as longtermStorage.

Check out the available options for longtermStorage and how to configure it.

In this example we are going to use a pravega-tier2 PVC using NFS as the storage backend.

Install the Pravega cluster manually

Once the operator is installed, you can use the following YAML template to install a small development Pravega Cluster (1 Controller, 3 Segment Stores). Create a pravega.yaml file with the following content.

apiVersion: "pravega.pravega.io/v1beta1"
kind: "PravegaCluster"
metadata:
  name: "pravega"
spec:
  version: 0.7.0
  zookeeperUri: [ZOOKEEPER_HOST]:2181
  bookkeeperUri: [BOOKKEEPER_SVC]:3181"
  pravega:
    controllerReplicas: 1
    segmentStoreReplicas: 3
    cacheVolumeClaimTemplate:
      accessModes: [ "ReadWriteOnce" ]
      storageClassName: "standard"
      resources:
        requests:
          storage: 20Gi
    image:
      repository: pravega/pravega
    longtermStorage:
      filesystem:
        persistentVolumeClaim:
          claimName: pravega-tier2

where:

  • [ZOOKEEPER_HOST] is the host or IP address of your Zookeeper deployment.
  • [BOOKKEEPER_SVC] is the name of the headless service of your Bookkeeper deployment.

Check out other sample CR files in the example directory.

Deploy the Pravega cluster.

$ kubectl create -f pravega.yaml

Verify that the cluster instances and its components are being created.

$ kubectl get PravegaCluster
NAME      VERSION   DESIRED MEMBERS   READY MEMBERS   AGE
pravega   0.7.0     4                 0               25s

Note: If we are installing pravega version 0.9.0 or above using operator version 0.5.1 or below, add the below JVM options for controller and segmentstore in addition to the current JVM options.

segmentStoreJVMOptions: ["-XX:+UseContainerSupport","-XX:+IgnoreUnrecognizedVMOptions"]

controllerjvmOptions: ["-XX:+UseContainerSupport","-XX:+IgnoreUnrecognizedVMOptions"]

Uninstall the Pravega cluster manually

$ kubectl delete -f pravega.yaml
$ kubectl delete pvc pravega-tier2

Uninstall the Operator manually

Note that the Pravega clusters managed by the Pravega operator will NOT be deleted even if the operator is uninstalled.

To delete all clusters, delete all cluster CR objects before uninstalling the operator.

$ kubectl delete -f deploy