Skip to content

Latest commit

 

History

History
64 lines (46 loc) · 3.12 KB

README.md

File metadata and controls

64 lines (46 loc) · 3.12 KB

Continuous Integration (CI) for Cloud Foundry Container Runtime (CFCR)

Coverage

Repos covered by the pipelines:

Other related repos:

  • Kubo disaster recovery acceptance tests (kdrats) - Provides tests used by pipelines contained within this repo.
  • [Kubo locks] - provides configuration information for the CI environments used by the pipelines. Private repo for CFCR team use.

Pipelines

To view the pipelines visit ci.kubo.sh

Testing

Kubo-deployment

The main pipeline, runs on every commit in kubo-release and kubo-deployment. Is also used to create Github releases. Runs tests on GCP, AWS and vSphere.

Long-lived-openstack

Runs tests on Openstack with a long-lived director instead of a freshly-deployed one for each run. Configuring OpenStack and Creating New Environments

custom-CIDRs

Tests the CIDRS suite of the integration tests. It tests changing the Pod and Service CIDRs for kubernetes.

Istio

Tests whether Istio specifications can be deployed on CFCR, and the Istio integration tests are run.

Gaffer

Attempts to update the CFCR deployment on which the gaffer application is run. The gaffer application backs https://gaffer.kubo.sh

kubo-release-pr & kubo-deployment-pr

Test pull requests to the repos. Have to be triggered manually.

pod-security-policy

Tests that the PodSecurityPolicy admission controller and policies work as expected.

CFCR-etcd

Tests the etcd release used in CFCR with different configurations. Creates and destroys the cluster at each run.

CFCR-etcd-long-running

Uses a long-lived etcd cluster and specifically focuses on potential “split brain” failure scenarios, centred around network partitions and VM restarts.

Bumping components

The bump-* pipelines are used to automatically update components of CFCR or the CI infrastructure. The docker-boshrelease pipeline tests and releases new versions of the docker release.

Building docker images

This pipeline builds all the images used in the other pipelines based on the dockerfiles located in kubo-ci.

Maintaining CI IaaS environments

The recycle pipeline is used to clean up environments. It is triggered automatically whenever a lock is released by the pipeline using that environment. The cleanup-gcp is used to clean up leftover LoadBalancers and Disks in GCP. The vsphere-cleaner pipeline generates a binary which is used by the recycle pipeline to clean vsphere environments.