CloudBees Core for PCF (PKS) (Beta)

WARNING! The CloudBees Core for Pivotal Cloud Foundry (PCF) (PKS) tile is currently in beta and is intended for evaluation and test purposes only Do not use this product in a PCF production environment.

This documentation describes CloudBees Core for Pivotal Cloud Foundry (PCF)(PKS). CloudBees Core enables companies to deliver better software faster by facilitating Continuous Integration (CI) and Continuous Delivery (CD) at any scale, for both modern and legacy applications. It is deployed to Pivotal Container Service (PKS) using standard Kubernetes manifests and Docker images, both of which are provided in the distribution.

Overview

Survey after survey shows JenkinsĀ® is the most popular open source automation server— and for good reason. However, Jenkins alone often lacks what teams need as continuous delivery scales across an organization. CloudBees Core extends Jenkins with functionality that embeds best practices, supports rapid onboarding, provides tools for easier admin management, and is based on an architecture that was built for scalability. You get enterprise-level benefits along with the Jenkins automation you already love.

CloudBees Core for PCF (PKS) is deployed to Pivotal Container Service (PKS) using standard Kubernetes manifests and Docker images, both of which are provided in the distribution.

Key Features

CloudBees Core for PCF (PKS) includes the following key features:

  • Go beyond physical scaling and drive collaboration among teams, easily propagating best practices. Offer a central CD as a Service across your organization, reducing the admin burden.
  • Autoscale up and down, on-demand, with elasticity at the cluster level provided by PKS. Utilize health checks to identify failing pods and spin up replacements as needed.
  • Utilize a sophisticated authorization strategy to reduce risks to software delivery by ensuring credentials and resources are not misused. Create compliance without hindering agility.
  • CloudBees Role-Based Access Control plus additional security features enable permissions to be defined by user, team, agents, folders, and jobs.
  • Regardless of what type of application you are delivering: Java, mainframe, or .NET. CloudBees Core is the one CI/CD solution for all your application environments.

Product Snapshot

The following table provides version and version-support information about CloudBees Core for PCF (PKS).

Element Details
Version v2.138.4.3
Release date December 7, 2018
Compatible Pivotal Container Service version(s) v1.0.0+
IaaS support AWS, Azure, GCP, and vSphere

Requirements

CloudBees Core for PCF (PKS) has the following requirements:

  • A PKS cluster with sufficient hardware resources available (for example, two 4CPU/16GB nodes).
  • On your local computer or bastion host, a Kubernetes client kubectl installed and configured to work with your PKS cluster (see: Obtain Cluster Access).
  • A namespace in the cluster with permissions to create Role and RoleBinding objects.
  • Network access to container images (Docker Hub or private registry).
  • The Nginx Ingress Controller installed and configured with a load balancer pointing to it (see: Install Nginx Ingress Controller).
  • A DNS record that points to the ingress controller’s load balancer.
  • An SSL certificate, if available.
  • A persistent StorageClass available within the cluster, ideally backed by SSDs.

Limitations

  • Internet access may be required in order to install the Nginx Ingress Controller.

Feedback

If you have a feature request, questions, or information about a bug, please email CloudBees Support.

License

Click the Request a Trial button in CloudBees Core Cloud Operations Center after the installation to receive a FREE 15-day license. Note that Internet access is required to use this option. Contact CloudBees Support to request a license that can be entered manually. Please indicate that it is a PKS environment, and provide your Instance ID. For purchasing information, submit a Pricing Request.

Create a pull request or raise an issue on the source for this page in GitHub