CloudBees Core on EKS installation guide

This guide shows you how to install CloudBees Core on Amazon Elastic Kubernetes Service (EKS). To perform the installation, you should be knowledgeable in AWS, Kubernetes, and NGINX Ingress.

CloudBees Core is a fully-featured, cloud native CD solution that can be hosted on-premise or in the public cloud. It provides a shared, centrally managed, self-service experience for all your development teams.

Before you install CloudBees Core on EKS, decide which installation method you want to use.

Pre-installation 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 following items are required to install CloudBees Core on EKS using the CloudBees installer.

  • An AWS account.

  • A Kubernetes client version 1.10 or later on your local computer or bastion host.

  • An AWS EKS cluster with the following requirements:

    • Runs Kubernetes version 1.10 or later. You must use a version that is actively supported by the Kubernetes distribution provider and is generally available.

    • Has nodes that have at least 2 CPUs and 4 GiBs of memory. Be sure that the cluster meets the sizing and scaling requirements in CloudBees Core Reference Architecture - Kubernetes on AWS EKS. NOTE: Having fewer masters on each VM means that losing a VM unexpectedly does not impact service.

    • Has N+1 worker nodes, where N is the number of managed masters and +1 is the CloudBees Operations Center.

    • Has network access to container images, either a public Docker Hub or a private Docker Registry.

  • An NGINX Ingress controller with Elastic Load Balancer (ELB) Layer 4 or Layer 7. For instructions on setting up NGINX Ingress Controller with ELB, see About networking modes for NGINX Ingress Controller.

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.