Cilium OLM

Warning This repository has been deprecated. Please see the list of vendors that maintain OLM to install Cilium on Openshift.

Isovalent

NOTE: this documentation is for Cilium maintainers, the user guide for OpenShift is part of Cilium documentation

This repository contains Cilium packaging for OpenShift, which is centred around Operator Lifecycle Management APIs (OLM).

Key Components

On OpenShift Cilium has to be installed by an installer operator in order to comply with RedHat certification requirements.

To install Cilium on OpenShift, users must have the following:

standard Kubernetes manifests for Cilium installer operator - RBAC, Deployment, Service ...etc
OpenShift-specific manifests for the installer operator - Subscription, OperatorGroup, ClusterServiceVersion

Installer operator

The installer operator is based on RedHat's helm-operator, which was chosen for expediance. In the future it's expected that Cilium will have a general-purpose installation operator that will support OpenShift as well as other platforms.

The operator is configured using a CiliumConfig CRD. The operator watches a single CiliumConfig CR in cilium namespace. The CRD is a simple object that hold Helm values.

Default CR specs for each release are sourced from top-level manifest (e.g. ciliumconfig.v1.10.yaml), a copy is made for each release in manifests/ (e.g. manifests/cilium.v1.9.6/cluster-network-07-cilium-ciliumconfig.yaml.

Cofiguration source code

Since configuration for OLM was fairly complex to manage in static YAML format, it was written in CUE. CUE is not very easy to use on its own, so a simple opinionated utility called kuegen is being used to execute CUE templates and write out YAML files.

The CUE templates can be found in config/operator/. kuegen is invoked with a helper script, which is typically driven by make, e.g. make generate.configs.v1.9.6.

Generated configuration

Configuration that is generated from CUE templates will get used in variety of different ways:

contents of manifests/ are used during installation in user guides as well as CI
contents of bundles/ are used for building metadata bundle images

Images

The installation is reliant on operator application image, it is currently based on RedHat's helm-operator.

For the purposes of certfication, the operator application image is accompanied by a metadata bundle image. Both images have to undergo certification tests in RedHat Partner Connect registry, maintainers should be able to obtain access to this registry.

Image definitions for the operator application and the metadata bundle can be found under operator/ bundles/. Images are mapped to Cilium releases.

Images are built using GitHub Actions and pushed to quay.io/cilium/cilium-olm and quay.io/cilium/cilium-olm-metadata. imagine utility is being used to drive the builds.

The metadata bundle image contains just YAML files and no software as such, however it's a crucial part of OLM and when it comes to certification it's what is being tested the most. It's possible to install the operator based on this image, however it's not something that is recommended for Cilium, as Cilium should be installed during cluster bootstrap as otherwise users will have to carry out live network migration.

Useful Links

RedHat Partner Connect (maintainers will be able to obtain access)
operator-courier - tool used in certification tests
operator-test-playbooks - ansible playbooks used to drive certication test (see #37)
Cilium OLM (operator) in RedHat Catalog
Cilium OLM (bundle) in RedHat Catalog

Common Workflows

To work with this repository, a maintainer should have Docker with latest version of buildx plugin installed, as well as Go toolchain.

To install kuegen, imagine and opm utilities to GOPATH, run:

(cd tools ; go install github.com/errordeveloper/imagine github.com/errordeveloper/kuegen github.com/operator-framework/operator-registry/cmd/opm)

Publishing a Cilium release

All releases and release candidates should be added to this repo for testing, albeit only latest stable release should be published in the RedHat Catalog.

To add a Cilium release, run:

scripts/add-release.sh 1.10.0

This will do the following:

create new dirs {operator,manifests,bundles}/cilium.v1.10.0 populate these with generated configs
download Helm chart tarball and unpack it to
create a local commit that has all the changes that can be pushed to the repo

Now push changes to a named branch that ends with the version number you are trying to publish (e.g. "pr/myghhandle/oss/v1.10.0"). This will create development images, which can be inspeted in the github actions output.

Validate that the release works by creating an Openshift cluster and installing the new operator, by modifying the OLM manifests to use the CI generated images. Also, make sure to copy the custom CiliumConfig to ensure that the K8s networking e2e tests will pass. For example, assuming that you are releasing v1.12.0:

cp ciliumconfig.conformance.yaml manifests/cilium.v1.12.0/cluster-network-07-cilium-ciliumconfig.yaml

Run the Network Conformance tests according to these instructions to ensure that Cilium functions as expected. There are 3 exepected failures in these conformance tests. They are:

NetworkPolicy between server and client should not allow access by TCP when a policy specifies only SCTP
NetworkPolicy between server and client should allow egress access to server in CIDR block
NetworkPolicy between server and client should ensure an IP overlapping both IPBlock.CIDR and IPBlock.Except is allowed

Once these conformance tests are passed it is safe to assume that the generated manifests are working correctly. The branch PR can then be merged into master.

Once the branch PR is merged into master, run the publish action on the master branch, defining the version to be published ("1.10.0" for example).

Once the action has completed successfully, you can now submit the image conformance tests to Redhat. For this you will need to access RedHat Partner Connect registry and obtain credentials for logging into the regsitry and setting the preflight API key.

Export the following environment variables using the credentials from RedHat Partner Connect:

export RHPC_PASSWORD_FOR_OLM_OPERATOR_IMAGE="_____"
export RHCP_PREFLIGHT_API_KEY="_____"

Next, login to the registry:

podman login -u unused scan.connect.redhat.com -p $RHPC_PASSWORD_FOR_OLM_OPERATOR_IMAGE

Next, run the preflight checks on the image:

PFLT_DOCKERCONFIG=~/.docker/config.json preflight check container --pyxis-api-token=$RHCP_PREFLIGHT_API_KEY --submit --certification-project-id=ospid-104ec1da-384c-4d7c-bd27-9dbfd8377f5b scan.connect.redhat.com/ospid-104ec1da-384c-4d7c-bd27-9dbfd8377f5b/cilium-olm:v1.10.0

Next, login to [Redhat Parnter Connect][] and click "Publish" on the image (once the vulnerability scanning is done).

Once the image is published open a new PR in the cilium/certified-operators, by adding the new manifests to the appropriately named new directory under operators/cilium (operators/cilium/v1.10.0, for example). Before commiting your changes make sure to modify the image reference in the manifests/cilium.clusterserviceversion.yaml so that the sha256 tag of the image is used (rather than the semantic tag).

Create a new PR against the official Openshift certified operators repository. If the CI tests against the PR fails and you can't figure out why you can file a support case on Redhat Partner Connect. After the CI tests succeed the PR will automatically be merged and the verstion will be officially certified.

Updating helm-operator base image

TODO

Changing configuration