Table of Contents

Search

  1. Preface
  2. Advanced clusters
  3. Setting up AWS
  4. Setting up Google Cloud
  5. Setting up Microsoft Azure
  6. Setting up a self-service cluster
  7. Setting up a local cluster
  8. Advanced configurations
  9. Troubleshooting
  10. Appendix A: Command reference

Advanced Clusters

Advanced Clusters

Add annotations and tolerations (optional)

Add annotations and tolerations (optional)

You can define annotations to attach metadata to the cluster and tolerations to control the nodes that the cluster runs on.
Annotations
Annotations can add non-identifying metadata to Kubernetes objects. Some examples of annotations are the date the object was last updated, the name of the user who manages the object, phone numbers of persons responsible for the object, or tool information for debugging purposes. Annotations can hold any kind of information that is useful and can provide context about the resource. Annotations usually consist of machine-generated data. The metadata in an annotation can be small or large, structured or unstructured, and can include characters not permitted by labels. Clients such as tools and libraries can retrieve this metadata.
Tolerations
Tolerations are a Kubernetes Pod property that allows the Kubernetes scheduler to schedule Pods with matching taints. A taint is a Kubernetes node property that allows a node to repel a set of Pods. Tolerations are applied to Pods. Taints and tolerations work together to ensure that Pods are not scheduled on inappropriate nodes.
For more information about annotations and tolerations, see the Kubernetes documentation.
After you attach annotations and tolerations to the cluster, ensure that you configure them as key-value pairs in the
Advanced Configuration
tab of the
advanced configuration
. For more information, see Advanced configuration.

0 COMMENTS

We’d like to hear from you!