Chat now with support
Chat mit Support

Foglight for Container Management 1.0 - User Guide

Monitoring Kubernetes Other Components

Kubernetes other components here including pods controllers, services, ingresses, persistent volumes, secrets and so on. All these components are grouped and displayed in tabs.

•
Configurations
•
Controllers
•
Storage
•
Load Balancer

Configurations

Figure 11. Kubernetes Configuration Dashboard

The Configurations dashboard includes Kubernetes secret and config map.

•
A Kubernetes secret is an object that contains a small amount of sensitive data such as a password, a token, or a key. Such information might otherwise be put in a Pod specification or in an image; putting it in a Secret object allows for more control over how it is used, and reduces the risk of accidental exposure.
•
A Kubernetes config map binds configuration files, command-line arguments, environment variables, port numbers, and other configuration artifacts to your Pods' containers and system components at runtime. Config maps allow you to separate your configurations from your Pods and components, which helps keep your workloads portable, makes their configurations easier to change and manage, and prevents hardcoding configuration data to Pod specifications.

Controllers

Figure 12. Kubernetes Controllers Dashboard

A controller manages a set of pods and ensures that the cluster is in the specified state. Instead of manually creating a pod, controllers can be used to create pods and to manage the pods. For example, the pods maintained by a replication controller are automatically replaced if they fail, get deleted, or are terminated. The Controllers dashboard presents the information related to the following controller types: Deployment, Replication Set, Replication Controller, Daemon Set, Stateful Set, Job, and Cron Job.

Storage

Figure 13. Kubernetes Storage Dashboard

The Kubernetes storage contains volumes, storage class, persistent volume, and persistent volume claim. Volumes are on-disk files used by the containers for persistent their data as well as sharing with other containers.The Storage dashboard shows the information about the following storage classes:

•
Storage Class provides a way for the administrator to describe the "class" of storage they offer.
•
Persistent Volume subsystem provides an API for users and administrators that abstracts details of how storage is provided from how it is consumed.
•
Persistent Volume Claim is used for dynamic volume provisioning which allow storage volumes to be created on-demand.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen