LogoLogo
Release notesAPI docsDocs homeEphemeral CloudTonic.ai
  • Tonic Ephemeral guide
  • About Tonic Ephemeral
  • Getting started with the Ephemeral free trial
  • Managing your Ephemeral account
  • Managing Databases
    • Viewing the list of databases
    • Starting a database
    • Changing the database configuration
    • Database configuration settings
      • Setting the required resources for a database
      • Setting the database expiration
      • Providing a custom configuration file
    • Connecting to a database
    • Resetting a database
    • Deactivating and reactivating databases
    • Managing auto snapshots
    • Tracking database activity
    • Deleting a database
  • Managing user snapshots
    • About user snapshots
    • Viewing the user snapshot list
    • Creating a user snapshot from an Ephemeral database
    • Creating a user snapshot from imported data
    • Editing a user snapshot
    • Creating a database from a user snapshot
    • Deleting a user snapshot
  • Installing and configuring Ephemeral
    • Ephemeral architecture
    • Configuring an allowlist for Ephemeral Cloud database connections
    • Installing a self-hosted instance of Ephemeral
      • System requirements
      • Deploying Ephemeral with Helm
    • Configuring database access on a self-hosted instance
    • Configuring tolerations and node selectors
    • Managing access to Ephemeral
      • Managing Ephemeral users
      • Enabling SSO on a self-hosted instance
        • Google
        • Okta
    • Setting the registry location for data volumes
    • Managing custom images
      • Creating, editing, and deleting custom images
      • Oracle image configuration
    • Configuring automatic deletion of snapshots
  • Monitoring and data collection
    • Monitoring your Ephemeral billed usage
    • Monitoring your disk storage
    • Data that Tonic.ai collects
  • Using the Ephemeral API
    • About the Ephemeral API
    • Configuring Ephemeral
    • Getting information about Ephemeral databases
    • Starting a database
    • Managing databases
    • Managing snapshots
Powered by GitBook
On this page
  • Helm chart settings for tolerations and node selectors
  • Node selector settings
  • Tolerations settings

Was this helpful?

Export as PDF
  1. Installing and configuring Ephemeral

Configuring tolerations and node selectors

PreviousConfiguring database access on a self-hosted instanceNextManaging access to Ephemeral

Last updated 3 months ago

Was this helpful?

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. .

You can also configure node selectors. .

Helm chart settings for tolerations and node selectors

In the Helm chart, you use the following settings to configure the tolerations and node selectors.

# For each workload type (app, bastion, database, volumeExtractor, dataPacker):
  # To use node selectors, set useNodeSelector to true, then provide the node selector key and labels. Each workload type must have a label. However, different workloads can have the same label.
  # To use tolerations, set useTolerations to true, then provide the tolerations key, operator, values, and effect. Each workload type must have values. However, different workloads can use the same values.

workload:
  useNodeSelector: false
  nodeSelectorKey: null
  appWorkloadLabel: null
  bastionWorkloadLabel: null
  databaseWorkloadLabel: null
  volumeExtractorWorkloadLabel: null
  dataPackerWorkloadLabel: null

  useTolerations: false
  tolerationsKey: null
  tolerationsOperatorProperty: null
  appTolerationsValue: null
  bastionTolerationsValue: null
  databaseTolerationsValue: null
  volumeExtractorTolerationsValue: null
  dataPackerTolerationsValue: null
  tolerationsEffect: null

Node selector settings

Here are the settings for node selectors:

useNodeSelector

Whether to use a node selector to manage node access.

The default is false.

To enable the node selector, set this to true.

nodeSelectorKey

The node selector key.

appWorkloadLabel

The label to apply to the pod that runs the Ephemeral API.

bastionWorkloadLabel

The label to apply to the pod that manages SSH access to Ephemeral databases.

databaseWorkloadLabel

The label to apply to the pod that Ephemeral creates for databases.

volumeExtractorWorkloadLabel

The label to apply to the pod that prepares a registry artifact to be used to start a new Ephemeral database.

dataPackerWorkloadLabel

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:

useTolerations

Whether to use tolerations to manage node access.

The default is false.

To enable tolerations, set this to true.

tolerationsKey

The tolerations key.

tolerationsOperatorProperty

The tolerations operator.

appTolerationsValue

The tolerations value to apply to the pod that runs the Ephemeral API.

bastionTolerationsValue

The tolerations value to apply to the pod that manages SSH access to Ephemeral databases.

databaseTolerationsValue

The tolerations value to apply to the pods that Ephemeral creates for databases.

volumeExtractorTolerationsValue

The tolerations value to apply to the pod that prepares a registry artifact to be used to start a new Ephemeral database.

dataPackerTolerationsValue

The tolerations value to apply to the pod that processes the API option to create a snapshot when a database expires.

tolerationsEffect

The tolerations effect.

Overview of taints and tolerations in Kubernetes documentation
Overview of node selectors in the Kubernetes documentation