The Data Center’s Config sub-menu contains, as you may have guessed, configuration components for your cluster. Here you find:
PodPresets contain information for a Pod or Pod template for later use. You select a Pod based on the specified services provided by the Pod Preset. Labels determine where PodPresets get applied.
Network Policies define the traffic and communication flow between Pods and other network endpoints. Labels denote which Pods and rules to use within a given pod.
Secrets are objects that contain sensitive information. Critical Stack stores and manages this information. View or Create Secrets using the Simple Form or Advanced Editor. Secrets allow access to internal cluster resources while protecting sensitive data.
Kubernetes defines a Service Account as “an identity for processes that run in a Pod”. Container processes need Service Accounts so the apiserver knows what that process is allowed to do based on the parameters set by the admin when creating the Service Account.
Creating a new Service Account is quick and easy with the Simple form or Advanced Editor. Name your Service Account and select from Image Pull Secrets or Secrets by placing a check in the box next to the necessary account(s).
Config Maps store non-sensitive data separate from container images. Separating sensitive data from the application code makes apps more portable. For sensitive data use a secret instead.
Horizontal Pod Autoscalers periodically adjusts the number of Pods based on the targets you or an admin set. The Horizontal Pod Autoscalers runs as both a resource and a controller. The controller takes its direction from the resource.
Critical Stack streamlines the creation of Horizontal Pod Autoscalers with a Simple form or the Advanced Editor. Select a Workload, specifiy the minimum and maximum replicas, then decide whether to include CPU Metrics, Memory Metrics, or both.