Configuring tolerations and node selectors
On a self-hosted instance of Ephemeral, you can configure the nodes where Ephemeral can schedule pods.
If your Kubernetes nodes are configured with taints, then you can configure the tolerations that enable the pods to be scheduled on the nodes. Overview of taints and tolerations in Kubernetes documentation.
You can also configure node selectors. Overview of node selectors in the Kubernetes documentation.
Helm chart settings for tolerations and node selectors
In the Helm chart, you use the following settings to configure the tolerations and node selectors.
Node selector settings
Here are the settings for node selectors:
| Whether to use a node selector to manage node access. The default is To enable the node selector, set this to |
| The node selector key. |
| The label to apply to the pod that runs the Ephemeral API. |
| The label to apply to the pod that manages SSH access to Ephemeral databases. |
| The label to apply to the pod that Ephemeral creates for databases. |
| The label to apply to the pod that prepares a registry artifact to be used to start a new Ephemeral database. |
| The label to apply to the pod that processes the API option to create a snapshot when a database expires. |
Tolerations settings
Here are the settings for tolerations:
| Whether to use tolerations to manage node access. The default is To enable tolerations, set this to |
| The tolerations key. |
| The tolerations operator. |
| The tolerations value to apply to the pod that runs the Ephemeral API. |
| The tolerations value to apply to the pod that manages SSH access to Ephemeral databases. |
| The tolerations value to apply to the pods that Ephemeral creates for databases. |
| The tolerations value to apply to the pod that prepares a registry artifact to be used to start a new Ephemeral database. |
| The tolerations value to apply to the pod that processes the API option to create a snapshot when a database expires. |
| The tolerations effect. |
Last updated