Skip to content

Latest commit

 

History

History
122 lines (87 loc) · 4.31 KB

README.md

File metadata and controls

122 lines (87 loc) · 4.31 KB

kubevirt-template-validator

kubevirt-template-validator is a kubevirt addon to check the annotations on templates and reject them if unvalid. It is implemented using a validating webhook.

The validating webhook uses two VM object metadata to get the parent template from which the VM was created: vm.kubevirt.io/template and vm.kubevirt.io/template.namespace. If either of these two metadata is missing, the webhook silently succeeds and the VM flow goes on as usual. The metadata are looked into the VM object metadata.labels first, and in the metadata.annotations then. If both are present, metadata.labels always prevails, because the webhook exits early at first fit. The webhook uses the VM metadata to fetch the validation annotations from the parent template metadata. Should validation annotation be missing, the webhook silently succeeds and the VM flow goes on as usual. Otherwise the annotations are parsed and evaluated against the VM object being validated.

Under no circumstances the validating webhook is allowed to mutate any of the objects (VM, template) it works with.

Go Report Card

License

Apache v2

Dependencies

Building

VERSION=devel make binary

tests

unit tests

make unittests

functional tests

Requirements:

  • OKD/OCP cluster >= 3.11
  • jq
  • oc (origin client tools)

You also need access to a running OCP/OKD >= 3.11 cluster. Example scripts are provided to set up a minishift cluster from scratch. Make sure you have the minishift binary on the testing system, then run

./hack/tests/setup.sh

Once the environment is up and running, you can run the tests themselves with

make functests

Installation - K8S

PLEASE NOTE: vanilla kubernetes does not support openshift templates so the webhook cannot function properly. Anyway, if you want to install it in your kubernetes cluster anyway, follow these steps:

  1. Create and deploy the certificates in a Kubernetes Secret, to be used in the following steps:
./cluster/k8s/webhook-create-signed-cert.sh
  1. [OPTIONAL] Check that the secret exists:
kubectl get secret -n kubevirt kubevirt-template-validator-certs
NAME                                TYPE      DATA      AGE
kubevirt-template-validator-certs   Opaque    2         1h
  1. Deploy the service:
kubectl create -f ./cluster/k8s/manifests/service.yaml
  1. Register the webhook. In order to set up the webhook, we need a CA bundle. We can reuse the one from the certs we create from the step #1.
cat ./cluster/k8s/manifests/validating-webhook.yaml | ./cluster/k8s/extract-ca.sh | kubectl apply -f -

Done!

installation on OKD/OCP

  1. Make sure the validating webhooks are enabled. You either need to configure the platform when you install it or to use OKD/OCP >= 4.0. See:
  1. Then, make sure you have the template:view cluster role binding in your cluster. If not, add it:
oc create -f ./cluster/okd/manifests/template-view-role.yaml
  1. Deploy the service:
kubectl create -f ./cluster/okd/manifests/service.yaml

OKD can automatically generate the TLS certificates thanks to the annotation in the provided manifests. So, unlike the steps for kubernetes#1, you don't have to do this manually.

  1. Register the webhook. Like for Kubernetes, we need to set up the CA bundle
./cluster/okd/extract-ca.sh ./cluster/okd/manifests/validating-webhook.yaml | oc apply -f -

Disable the webhook

To disable the webhook, just de-register it from the apiserver:

$KUBECTL delete -f ./cluster/$PLATFORM/manifests/validating-webhook.yaml

Caveats & Gotchas

There is no automation to tear down the minishift cluster for functests. You need to do it manually.