Glossary of terms
Use this glossary to familiarize yourself with the key terminology and concepts used in Container Cluster Management. Understanding these terms will help you navigate the platform more effectively and better understand the configuration, management and operation of container clusters throughout their lifecycle.
Container Cluster Management Glossary:
Service Account (In Progress):
- A principal identity recognizable by users and peripheral systems, composed of a set of secrets for authentication and authorization.
Cluster Role (In Progress):
- A cluster-level logical grouping of Policy Rules, accessible as a unit by Role Binding or Cluster Role Binding.
Role (In Progress):
- A name spaced logical grouping of Policy Rules, accessible as a unit by Role Binding.
Cluster Role Binding (In Progress):
- Links to a Cluster Role without containing it. It references a Cluster Role in the global namespace and adds information through Subject.
Role Binding (In Progress):
- References a Role without containing it. It can link to a Role in the same namespace or a Cluster Role in the global namespace, adding 'who' information via Subjects and specifying the namespace of existence.
Config Map:
- Holds configuration data for pods to utilize.
Secret:
- Contains secret data of a certain type. A Service is a named software service abstraction (e.g., MySQL), comprising a local port and a selector to determine which pods respond to requests.
Ingress:
- A collection of rules enabling inbound connections to reach backend-defined endpoints. It can configure services for external URLs, load balance traffic, terminate SSL, and more.
Persistent Volume (PV):
- A storage resource provisioned by an administrator.
Persistent Volume Claim:
- A user's request for and claim to a Persistent Volume.
Pod:
- A collection of containers that can operate on a host.
Deployment:
- Facilitates declarative updates for Pods and Replica Sets.
Replica Set:
- Ensures a specified number of pod replicas are running at any given time.
Daemon Set:
- Represents the configuration of a daemon set.
Stateful Set:
- Represents a set of pods with consistent identities, defined by network and storage attributes.
Job:
- Represents the configuration of a single job.
CronJob:
- Represents the configuration of a single cronjob.