knative-serving-operator

knative-serving-operator

If you don't already have it, install the latest operator-sdk

Before doing anything else, grab your dependencies:

$ dep ensure -v

Version 0.5.1 of knative-serving refers to Istio CRD's:

$ kubectl apply -f https://github.com/knative/serving/releases/download/v0.5.1/istio-crds.yaml

Run the Operator

The operator watches for an Install custom resource, so you'll need to register it:

$ kubectl apply -f deploy/crds/serving_v1alpha1_install_crd.yaml

Once the operator is up (see next sections), trigger the installation by creating an Install CR. There are currently no fields expected in its spec but its status should contain a list of the installed resources and their version.

$ kubectl apply -f deploy/crds/serving_v1alpha1_install_cr.yaml
$ kubectl get install -oyaml

To uninstall,

$ kubectl delete -f deploy/crds/serving_v1alpha1_install_cr.yaml

Outside Cluster

$ operator-sdk up local

To see the flags supported by the operator,

$ operator-sdk up local --operator-flags "--help"

Inside Cluster

We give the operator's service account cluster-admin privileges in the default namespace.

$ kubectl apply -f deploy/

Create a Release

Verify that version.go matches the contents of deploy/resources and then run the following to build and push an image for the operator to quay.io.

./hack/release.sh

Create a CatalogSource for OLM

The OLM requires special manifests that the operator-sdk can help generate. First we extract the CRD's from the upstream manifest[s] contained within deploy/resources:

./hack/extract-crds.sh

Update deploy/role.yaml to match the RBAC policies in the upstream manifest[s].

And then generate a basic ClusterServiceVersion passing in a version that corresponds to those manifests:

operator-sdk olm-catalog gen-csv --csv-version 0.5.1

Some post-editing of the file it generates is required:

• Add fields to address any warnings it reports
• Add description and displayName fields for all owned CRD's
• Add args: ["--olm", "--install"] to the operator's container spec.
• Add a replaces field referencing the previous CSV

With the above in place, the catalog.sh script should yield a valid CatalogSource for you to publish.

Using OLM on Minikube

You can test the operator using minikube after installing OLM on it:

minikube start
kubectl apply -f https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.9.0/olm.yaml

Once all the pods in the olm namespace are running, install the operator like so:

./hack/catalog.sh | kubectl apply -n olm -f -

Interacting with OLM is possible using kubectl but the OKD console is "friendlier". If you have docker installed, use this script to fire it up on http://localhost:9000.