CloudBees Core on Azure Kubernetes Service (AKS) installation guide

This guide shows you how to install CloudBees Core on Azure Kubernetes Service (AKS).

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 AKS, decide which installation method you want to use.

Pre-installation checklist

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.

Before you can install CloudBees Core on AKS using the CloudBees installer, you must have the following items configured correctly.

To perform the required pre-installation setup, you should be knowledgeable in AKS, Kubernetes, and NGINX Ingress.

Failure to complete the pre-installation checklist correctly may lead to installation errors and delayed installation.

  • Install and configure Kubernetes client version 1.10 or later on your local computer or bastion host.

  • Set up an AKS 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, so nodes have 1 full CPU/1GiB available after running a master with default settings.

    • Uses an instance type that allows premium disks (for example: Standard_D4s_v3).

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

  • Install the NGINX Ingress Controller in the cluster. Ensure the following are completed:

    • Configure the load balancer to point to the NGINX Ingress Controller.

    • Create a DNS record for the domain you want to use for CloudBees Core, and point it to the Azure Load balancer.

    • Create TLS certificates. These are required when you deploy CloudBees Core.

  • Create a CloudBees Core namespace in the cluster with permissions to create Role and RoleBinding objects.

  • Define a Kubernetes cluster Default Storage Class.

Creating your AKS cluster

To create a Kubernetes cluster using Azure Kubernetes Service (AKS), refer to Create an Azure Container Service (AKS) cluster on the Microsoft Azure website.

More information on administering an AKS cluster is available from the full documentation.

More information on Kubernetes concepts is available from the Kubernetes site, including:

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.