Supported platforms for CloudBees Core on modern cloud platforms


When running CloudBees Core on modern cloud platforms, consult this page for supported platforms.

Supported Kubernetes

For CloudBees Core on modern cloud platforms, CloudBees supports Kubernetes 1.x, starting with 1.10, as long as it is actively supported by the Kubernetes distribution provider and is one of the following implementations:

  • Amazon EKS

  • Azure Kubernetes Service (AKS)

  • Google Kubernetes Engine (GKE)

  • Pivotal Container Service (PKS)

  • Red Hat OpenShift

  • CNCF-certified Kubernetes

The version used must be Generally Available. CloudBees does not support or recommend "proof of concept" offering of Kubernetes platforms or Beta or Public preview versions.

Supported Docker environments

CloudBees supports running CloudBees Core on modern cloud platforms in Docker containers, subject to the following constraints:

  1. The Docker image must be the image provided by CloudBees, which is cloudbees/cloudbees-cloud-core-cm or cloudbees-core-mm for CloudBees Core on modern cloud platforms

  2. The Docker Engine used to run these containers must run on a Linux platform and must be a standalone Docker Engine provided by Docker, Inc. or by a Linux distribution provider (such as Red Hat or CentOS).

Supported NFS versions

CloudBees supports the following versions of NFS:

  • NFS v.3.x

  • NFS v4.1 and higher

Note
There are known performance issues with NFS v4.0. CloudBees supports NFS v4.1 and higher, but CloudBees does not support NFS v4.0.

Configuration as Code (CasC) support in CloudBees Core

As of August 2019, the Jenkins Configuration as Code Plugin is not fully supported in CloudBees Core.

Specific issues with the Jenkins Configuration as Code Plugin within CloudBees Core include:

  • Enabling the Jenkins Configuration as Code Plugin on Core instances may lead to system instability, because CloudBees products have not been fully tested against the Configuration as Code Plugin.

  • Although it is technically possible to use the Jenkins Configuration as Code Plugin with Team, Client or Managed Masters in the CloudBees Core environment, you will not be able to configure:

    • CloudBees proprietary plugins, including those delivered through CAP. The plugin manager will override configuration properties set by the Jenkins Configuration as Code plugin.

    • CloudBees-specific configurations in masters or CloudBees Operation Center.

    • Any community/open source plugins that do not support or are not compatible with the Jenkins Configuration as Code Plugin.

    • Some configuration changes made by the Jenkins Configuration as Code Plugin on a master may be overwritten by values from CloudBees Operations Center.