The Configurations dashboard includes Kubernetes Secret and Config Map.
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, Replica Set, Replication Controller, Daemon Set, Stateful Set, Job, and Cron Job.
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. |
The Load Balancer dashboard includes information about Kubernetes service, endpoint, and ingress. A Kubernetes ingress can provide load balancing, SSL termination, and name-based virtual hosting. A Kubernetes service is an abstraction which defines a logical set of pods and a policy by which to access them - sometime called micro-services. Kubernetes will update the endpoint whenever the set of pods in a service changes.
© ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center