CloudBees Core on OpenShift installation guide

Helm is the recommended method for installing and managing CloudBees Core. If your current CloudBees Core installation wasn’t installed using Helm, you can migrate your existing CloudBees Core installation to use Helm. For Helm installation instructions, see Installing CloudBees Core on OpenShift using Helm.

Please be aware that as of CloudBees Core version, the CloudBees Core upgrade process has changed.

This document explains the cluster requirements, points you to the Red Hat OpenShift documentation you will need to create a cluster and explains how to install CloudBees Core in your new OpenShift cluster.

The OpenShift cluster requirements must be satisfied before CloudBees Core can be installed.

OpenShift cluster requirements

For details about supported platforms for CloudBees Core on modern cloud platforms, such as supported Kubernetes, Helm, and NFS versions, refer to Supported platforms for CloudBees Core on modern cloud platforms.

The OpenShift requirements for this product include:

  • A supported version of OpenShift

    • Must have network access to container images (public Docker Hub or a private Docker Registry)

  • Load balancer configured and pointing to the Router service

    • A DNS record that points to the load balancer

    • TLS certificates (needed when you deploy CloudBees Core)

  • Project assigned for your CloudBees product

Only production releases of OpenShift are supported. Beta releases are not supported.

Creating your OpenShift cluster

Refer to the Red Hat OpenShift documentation for complete instructions on how to deploy an OpenShift cluster on your own infrastructure or create an OpenShift cluster via the OpenShift online service.

Security considerations

OpenShift comes with some security constraints that make it slightly harder to work with when running Jenkins agents.

Make sure to read Why do my applications run as a random user ID? and instructions to create images to make sure you are running docker images that behave correctly on this platform.

Copyright © 2010-2020 CloudBees, Inc.Online version published by CloudBees, Inc. under the Creative Commons Attribution-ShareAlike 4.0 license.CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Core, CloudBees Flow, CloudBees Flow Deploy, CloudBees Flow DevOps Insight, CloudBees Flow DevOps Foresight, CloudBees Flow Release, CloudBees Accelerator, CloudBees Accelerator ElectricInsight, CloudBees Accelerator Electric Make, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center, and DEV@cloud are trademarks of CloudBees, Inc. Most CloudBees products are commonly referred to by their short names — Accelerator, Automation Platform, Flow, Deploy, Foresight, Release, Insight, and eMake — throughout various types of CloudBees product-specific documentation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Jenkins is a registered trademark of the non-profit Software in the Public Interest organization. Used with permission. See here for more info about the Jenkins project. The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at Apache, Apache Ant, Apache Maven, Ant and Maven are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.Other names may be trademarks of their respective owners. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this content, and CloudBees was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this content, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.