Skip to content

Latest commit

 

History

History
160 lines (124 loc) · 7.54 KB

install.md

File metadata and controls

160 lines (124 loc) · 7.54 KB
title toc weight indent
Install
true
301
true

Install Crossplane

Crossplane can be easily installed into any existing Kubernetes cluster using the regularly published Helm chart. The Helm chart contains all the custom resources and controllers needed to deploy and configure Crossplane.

Pre-requisites

Installation

Helm charts for Crossplane are currently published to the stable and master channels.

Stable

The stable channel is the most recent release of Crossplane that is considered ready for the community.

kubectl create namespace crossplane-system

helm repo add crossplane-stable https://charts.crossplane.io/stable
helm repo update

helm install crossplane --namespace crossplane-system crossplane-stable/crossplane

Master

The master channel contains the latest commits, with all automated tests passing. master is subject to instability, incompatibility, and features may be added or removed without much prior notice. It is recommended to use one of the more stable channels, but if you want the absolute newest Crossplane installed, then you can use the master channel.

To install the Helm chart from master, you will need to pass the specific version returned by the search command:

kubectl create namespace crossplane-system
helm repo add crossplane-master https://charts.crossplane.io/master/
helm repo update
helm search repo crossplane-master --devel

helm install crossplane --namespace crossplane-system crossplane-master/crossplane --devel --version <version>

Uninstalling the Chart

To uninstall/delete the crossplane deployment:

helm delete crossplane --namespace crossplane-system

That command removes all Kubernetes components associated with Crossplane, including all the custom resources and controllers.

Configuration

The following tables lists the configurable parameters of the Crossplane chart and their default values.

Parameter Description Default
affinity Enable affinity for Crossplane pod {}
image.repository Image crossplane/crossplane
image.tag Image tag master
image.pullPolicy Image pull policy used in all containers IfNotPresent
imagePullSecrets Names of image pull secrets to use dockerhub
replicas The number of replicas to run for the Crossplane pods 1
deploymentStrategy The deployment strategy for the Crossplane and RBAC Manager (if enabled) pods RollingUpdate
leaderElection Enable leader election for Crossplane Managers pod true
nodeSelector Enable nodeSelector for Crossplane pod {}
priorityClassName Priority class name for Crossplane and RBAC Manager (if enabled) pods ""
resourcesCrossplane.limits.cpu CPU resource limits for Crossplane 100m
resourcesCrossplane.limits.memory Memory resource limits for Crossplane 512Mi
resourcesCrossplane.requests.cpu CPU resource requests for Crossplane 100m
resourcesCrossplane.requests.memory Memory resource requests for Crossplane 256Mi
securityContextCrossplane.runAsUser Run as user for Crossplane 65532
securityContextCrossplane.runAsGroup Run as group for Crossplane 65532
securityContextCrossplane.allowPrivilegeEscalation Allow privilege escalation for Crossplane false
securityContextCrossplane.readOnlyRootFilesystem ReadOnly root filesystem for Crossplane true
provider.packages The list of Provider packages to install together with Crossplane []
configuration.packages The list of Configuration packages to install together with Crossplane []
packageCache.medium Storage medium for package cache. Memory means volume will be backed by tmpfs, which can be useful for development. ""
packageCache.sizeLimit Size limit for package cache. If medium is Memory then maximum usage would be the minimum of this value the sum of all memory limits on containers in the Crossplane pod. 5Mi
packageCache.pvc Name of the PersistentVolumeClaim to be used as the package cache. Providing a value will cause the default emptyDir volume to not be mounted. ""
tolerations Enable tolerations for Crossplane pod {}
resourcesRBACManager.limits.cpu CPU resource limits for RBAC Manager 100m
resourcesRBACManager.limits.memory Memory resource limits for RBAC Manager 512Mi
resourcesRBACManager.requests.cpu CPU resource requests for RBAC Manager 100m
resourcesRBACManager.requests.memory Memory resource requests for RBAC Manager 256Mi
securityContextRBACManager.runAsUser Run as user for RBAC Manager 65532
securityContextRBACManager.runAsGroup Run as group for RBAC Manager 65532
securityContextRBACManager.allowPrivilegeEscalation Allow privilege escalation for RBAC Manager false
securityContextRBACManager.readOnlyRootFilesystem ReadOnly root filesystem for RBAC Manager true
rbacManager.affinity Enable affinity for RBAC Managers pod {}
rbacManager.deploy Deploy RBAC Manager and its required roles true
rbacManager.nodeSelector Enable nodeSelector for RBAC Managers pod {}
rbacManager.replicas The number of replicas to run for the RBAC Manager pods 1
rbacManager.leaderElection Enable leader election for RBAC Managers pod true
rbacManager.managementPolicy The extent to which the RBAC manager will manage permissions. All indicates to manage all Crossplane controller and user roles. Basic indicates to only manage Crossplane controller roles and the crossplane-admin, crossplane-edit, and crossplane-view user roles. All
rbacManager.tolerations Enable tolerations for RBAC Managers pod {}
rbacManager.skipAggregatedClusterRoles Opt out of deploying aggregated ClusterRoles false
metrics.enabled Expose Crossplane and RBAC Manager metrics endpoint false
extraEnvVarsCrossplane List of extra environment variables to set in the crossplane deployment. Any . in variable names will be replaced with _ (example: SAMPLE.KEY=value1 becomes SAMPLE_KEY=value1). {}
extraEnvVarsRBACManager List of extra environment variables to set in the crossplane rbac manager deployment. Any . in variable names will be replaced with _ (example: SAMPLE.KEY=value1 becomes SAMPLE_KEY=value1). {}

Command Line

You can pass the settings with helm command line parameters. Specify each parameter using the --set key=value[,key=value] argument to helm install. For example, the following command will install Crossplane with an image pull policy of IfNotPresent.

helm install --namespace crossplane-system crossplane-stable/crossplane --set image.pullPolicy=IfNotPresent

Settings File

Alternatively, a yaml file that specifies the values for the above parameters (values.yaml) can be provided while installing the chart.

helm install crossplane --namespace crossplane-system crossplane-stable/crossplane -f values.yaml

Here are the sample settings to get you started.

replicas: 1

deploymentStrategy: RollingUpdate

image:
  repository: crossplane/crossplane
  tag: alpha
  pullPolicy: Always

imagePullSecrets:
- dockerhub