Install Kubermatic Kubernetes Platform (KKP) EE on vSphereEnterprise Edition
This chapter explains the installation procedure of KKP Enterprise Edition (EE) into a pre-existing
At the moment you need to be invited to get access to Kubermatic’s EE Docker repository before you can try it out.
Please contact sales to receive your credentials.
- User cluster – A Kubernetes cluster created and managed by KKP
- Seed cluster – A Kubernetes cluster which is responsible for hosting the master components of a user cluster
- Master cluster – A Kubernetes cluster which is responsible for storing the information about users, projects and SSH keys. It hosts the KKP components and might also act as a seed cluster.
- Seed datacenter – A definition/reference to a seed cluster
- Node datacenter – A definition/reference of a datacenter/region/zone at a cloud provider (aws=zone, digitalocean=region, openstack=zone)
Before installing, make sure your Kubernetes cluster meets the minimal requirements
and make yourself familiar with the requirements for your vSphere cloud provider.
For this guide you will have to have
kubectl and Helm (version 3) installed locally.
This guide assumes a clean installation into an empty cluster. Please refer to the upgrade notes
for more information on migrating existing installations to the Kubermatic Installer.
The installation procedure is identical to the Community Edition, with the exception that
a different installer needs to be downloaded and that the Docker credentials need to be configured.
When downloading the installer, make sure to choose the
-ee- variant on GitHub. Extract it like documented in the CE install
During configuration, it’s required to set the Docker Pull Secret, which allows the local Docker daemons to pull the KKP
images from the private Docker repository. The Docker Pull Secret is a tiny JSON snippet and needs to be configured in the
KubermaticConfiguration (e.g. in the
# skipping everything else in this file
# for demonstration purposes
# This is where the JSON snippet needs to be configured. It does not need to be
# a multiline JSON string.
Follow the CE install guide on vSphere as normal, the remaining steps apply equally to the Enterprise Edition.