Lyrid Community Glossary

Think of it as a box that contains everything an application needs to run. It has all the necessary codes, settings, and dependencies, and can be run anywhere without worrying about the host environment.

It's like a blueprint for containers. It's an unchangeable file with all the stuff needed to run an app.

It's like an air traffic controller for containers, taking care of all the tasks like deployment, management, scaling, and more.

These are the software wizards that help manage and choreograph your containers. Kubernetes is a big name here.

A big player in the world of containers that plays well with Kubernetes.

It's a group of environments (physical, virtual, cloud-based, etc.) where your applications run. It's got the brains (master components) and the brawn (worker nodes).

It's the brains of the operation, managing activities like scheduling and scaling apps, and keeping an eye on the state of the cluster.

This guy lets you talk to Kubernetes objects, it's like the spokesperson of the cluster.

It's the memory of the cluster, storing all the data.

The personal assistant for your pods, making sure they have a node to run on based on their needs.

Think of it as a manager supervising various controllers, each handling a part of the cluster's current state.

These guys are the persistent overseers, always working to match the cluster's current state to the desired one.

The worker bees in your cluster, running the pods and maintaining the environment.

This agent checks if the containers are running well.

It's the stage where the containers perform, thanks to Docker or containerd.

The traffic cop of the network, managing routing and forwarding rules.

The communication link between the cluster and you, helping your apps achieve the desired state.

Your command line buddy to control Kubernetes objects.

An expansion pack for Kubernetes, allowing more APIs than the core set.

These guys describe your workload in the cluster, telling Kubernetes what to run and where.

Unique names for your objects, kinda like a username.

Unique IDs for your objects, kinda like a user's ID number.

It's a way to organize and separate resources and objects.

Tags to help sort out objects.

Filters to find objects based on their labels.

Notes to help people or tools, but they don't affect Kubernetes directly.

This is your app running on Kubernetes, which can be one or many components working together.

The smallest unit in Kubernetes that houses the containers.

These guys help manage pods so you don't have to do it one by one.

Stateful applications remember past interactions while stateless ones don't.

They help automate things for specific software and cases in Kubernetes.

Stores non-confidential data in Kubernetes, like public credentials and URLs.

Holds confidential data, like passwords or keys.

It's like a budget, limiting how many resources a namespace can use.

Set boundaries for resource allocation to pods in a namespace.

Helps control the traffic in your cluster.

It's like a bouncer, deciding who gets access to the cluster resources.

Sets permissions for resources, either within a namespace (Roles) or the entire cluster (ClusterRoles).

Assign roles and subjects to namespaces or clusters.

Both are methods to authenticate users and services.

Allows pods to communicate with each other.

Handles the networking for containers.

Allows external traffic to reach your cluster's services.

Distributes network traffic to prevent any server from getting overloaded.

Helps locate applications and services on a network.

Tools that handle networking, routing, and DNS tasks within the cluster.

Matches pods with nodes for running them.

Helps you have more control over how your pods are scheduled.

Keeps track of resource usage and performance.

Metrics to keep an eye on the performance and health of your cluster and applications.

Tools for real-time monitoring, visualization, collection, and alerting of metrics in your cluster.

Collects and displays logs from Kubernetes, helpful for debugging.

Tools for processing, searching, and visualizing log data in your cluster.

Storage that's cleaned up when a workload or container is done.

Long-term storage that's independent of any pod or deployment.

Automatically adjusts capability based on demand, saving costs when demand is low.