Data Plane Installation
This chart installs the TSB Data Plane operator. It's not required if the TSB Control Plane operator is installed with a revision. If you install it with a revision, gateways are handled by TSB Control Plane operator itself.
Install
helm install dp tetrate-tsb-helm/dataplane --namespace istio-gateway --create-namespace -f values.yaml
Usage
Once the TSB Data Plane installation is finished all the Data Plane resources are allowed to be run.
Check the available resources in the documentation.
Configuration
| Name | Description | Default value |
|---|---|---|
image.registry | Registry used to download the operator image | gcr.io/tetrate-internal-containers |
image.tag | The tag of the operator image | same as the Chart version |
Operator extended configuration
The TSB operator related resources like the deployment, the service or the service account can be extended using the following optional properties:
| Name | Description | Default value |
|---|---|---|
operator.deployment.affinity | Affinity configuration for the pod | |
operator.deployment.annotations | Custom collection of annotations to add to the deployment | |
operator.deployment.env | Custom collection of environment vars to add to the container | |
operator.deployment.podAnnotations | Custom collection of annotations to add to the pod | |
operator.deployment.replicaCount | Number of replicas managed by the deployment | |
operator.deployment.strategy | Deployment strategy to use | |
operator.deployment.tolerations | Toleration collection applying to the pod scheduling | |
operator.service.annotations | Custom collection of annotations to add to the service | |
operator.serviceAccount.annotations | Custom collection of annotations to add to the service account | |
operator.serviceAccount.imagePullSecrets | Collection of secrets names required to be able to pull images from the registry | |
operator.pullSecret | A Docker JSON config string that will be stored as an image pull secret |