Config View

Documentation > User Interface > Config View

Config Section in Orchetrix

The Config Section in Orchetrix offers a unified view of Kubernetes configuration resources, including Config Maps, Secrets, Resource Quotas, Limit Ranges, horizontal pod auto scalers, pod disruption budget, priority classes, leases, mutating webhook configs and validating webhook configs. These resources allow you to manage application settings, define resource limits, and control traffic flow within the cluster, ensuring that your environment runs securely and efficiently.

Config Maps

In Kubernetes, a Config Map is used to store non-sensitive configuration data as key-value pairs. It allows you to decouple configuration from your container images, so the same application image can be reused with different configs. ConfigMaps can be consumed by Pods as environment variables or mounted as volumes.

Learn more about ConfigMaps in the official Kubernetes documentation

The ConfigMaps table lists all configuration maps in the cluster. Clicking on a ConfigMap opens a details panel with tabs such as Overview, Data, YAML, and Events. Use the Namespace drop-down and Search Resources field to filter or find specific ConfigMaps.

Columns can be sorted, and multiple items can be selected via checkboxes for bulk deletion using the Delete Selected button. The Refresh button reloads the list. Use the More Actions menu for quick access to Edit and Delete.

Default Columns:

Name: Config Map name
Namespace: Target namespace
Keys: Number of key-value pairs
Age: Time since creation
Options: Edit, Delete

Secrets

A Secret in Kubernetes is used to store sensitive information like passwords, tokens, or TLS certificates. Secrets are base64-encoded and intended to be used securely with RBAC to limit access. They can be injected into Pods as environment variables or mounted volumes.

Learn more about Secrets in the official Kubernetes documentation

The Secrets table displays all Secrets with optional masked/unmasked viewing. Clicking a Secret shows the details panel with Overview, Data, YAML, and Events. Use Namespace filtering or the Search Resources field to locate items.

You can sort columns, select multiple Secrets with checkboxes, and delete them in bulk. The More Actions menu allows direct Edit and Delete operations.

Default Columns:

Name: Secret name
Namespace: Where the secret resides
Keys: Number of data keys stored
Type: Generic, TLS, Docker config, etc.
Age: When it was created
Options: Edit, Delete

Resource Quotas

Resource Quotas help enforce resource limits at the namespace level by defining constraints on compute resources, storage, or object count. They ensure fair resource usage across teams or workloads.

Learn more about ResourceQuotas in the official Kubernetes documentation

The Resource Quotas table lists active quotas with data on limits and usage. Click an entry to open the details panel with Overview, Details, YAML, and Events. Filter by namespace or search using the Search Resources field.

Columns support sorting, and multiple quotas can be removed using Delete Selected. Use Refresh to update the view. Edit/Delete options are under More Actions.

Default Columns:

Name: Quota name
Namespace: Namespace where it applies
Age: Created time
Options: Edit, Delete

Limit Ranges

Limit Ranges define default and maximum CPU/memory resource requests per Pod or container within a namespace. They help prevent overconsumption of cluster resources and set boundaries for workloads.

Learn more about Limit Ranges in the official Kubernetes documentation

The Limit Ranges table shows limits applied to containers and Pods. Clicking opens a details panel with key configuration data under Overview, YAML, and Events. Filter using Namespace drop-down or Search Resources.

Columns are sortable, and selected items can be deleted in bulk using Delete Selected. Edit and Delete options appear in the More Actions menu.

Default Columns:

Name: Limit Range name
Namespace: Applied namespace
Age: Created time
Options: Edit, Delete

Horizontal Pod Autoscalers

A Horizontal Pod Auto scaler automatically adjusts the number of pod replicas based on observed CPU, memory, or custom metrics. It helps maintain optimal performance and resource efficiency.

Learn more about HPAs in the official Kubernetes documentation

The HPA table lists all auto scalers, showing target workloads, replica counts, and metrics. Click an item to open the details panel with tabs for Overview, Metrics, YAML, and Events. Use Namespace filtering and Search Resources for navigation.

You can sort, bulk delete, or use the More Actions menu for quick Edit and Delete operations. Use Refresh to reload the data.

Default Columns:

Name: HPA name
Namespace: Target namespace
Metrics: CPU, memory, or custom metrics
Min Pods:
Max Pods:
Replicas:
Age: Created time
Status:
Options: Edit, Delete

Pod Disruption Budget

A Pod Disruption Budget ensures that a minimum number of replicas for a workload remain available during voluntary disruptions (e.g., node drains). It safeguards application availability during maintenance events.

Learn more about PDBs in the official Kubernetes documentation

The PDB table displays budget policies for workloads. Clicking a row opens a details panel with Overview, Details, YAML, and Events. You can filter by Namespace or search using Search Resources.

Supports column sorting, multi-select delete, and Refresh. The More Actions menu provides Edit and Delete options.

Default Columns:

Name: PDB name
Namespace: Applied namespace
Min Available: Disruption rule
Max Unavailable:
Current Healthy Pods: Live pod count
Age: Created time
Options: Edit, Delete

Priority Classes

Priority Classes influence pod scheduling during resource constraints. Higher-priority Pods are scheduled first and can preempt lower-priority Pods. They’re essential in multi-tenant clusters or workloads with strict availability needs.

Learn more about Priority Classes in the official Kubernetes documentation

The Priority Classes table lists all configured priority levels. Click an item to open the details panel with tabs for Overview, YAML, and Events. Filter and search using standard controls.

Sorting, bulk deletion, and quick actions (Edit/Delete) are supported via the table and More Actions menu. Use Refresh for updates.

Default Columns:

Name: Priority class name
Value: Integer priority level
Global Default: Used when no other priority is set
Age: Created time
Options: Edit, Delete

Runtime Classes

Runtime Classes specify alternative container runtimes (like gVisor or Kata Containers) for pods that need specialized isolation or behavior.

Learn more about Runtime Classes in the official Kubernetes documentation

The Runtime Classes table shows all supported runtimes with handler names and config details. Selecting a row opens the details panel with Overview, YAML, and Events. Filter by name or handler.

You can sort, refresh, and manage items with Edit/Delete options in the More Actions menu.

Default Columns:

Name: Runtime Class name
Handler: Runtime interface (e.g., runc, kata)
Age: Created time
Options: Edit, Delete

Leases

Leases are part of Kubernetes’ coordination mechanism, primarily used for leader election between controllers. They track ownership and renewal times to manage high availability.

Learn more about Leases in the official Kubernetes documentation

The Leases table lists all lease objects with holder identity and renewal info. Clicking opens a read-only details panel with Overview and YAML tabs. Filtering and searching is supported.

Leases are typically view-only and not manually edited or deleted. The Refresh button updates their state.

Default Columns:

Name: Lease name
Namespace: Applied namespace
Age: Created time
Options: Edit/Delete

Mutating Webhook Configs

Mutating Webhooks intercept Kubernetes API requests and allow you to modify them (e.g., inject sidecars, labels) before they're persisted. They are part of the admission control system.

👉 Learn more about Mutating Webhooks in the official Kubernetes documentation

The Mutating Webhooks table shows all registered webhook configurations. Clicking an entry opens the details panel with Overview, YAML, and Events. Filtering and searching help you locate specific configs.

You can sort, bulk delete, or use the More Actions menu for Edit/Delete. Refresh updates webhook status.

Default Columns:

Name: Webhook config name
Webhooks: Number of webhooks defined
Age: Created time
Options: Edit, Delete

Validating Webhook Configs

Validating Webhooks intercept and validate requests to the Kubernetes API without modifying them. They're used to enforce security, policy, or schema compliance.

Learn more about Validating Webhooks in the official Kubernetes documentation

The Validating Webhooks table lists all validation hooks with scope and match rules. Clicking reveals Overview, YAML, and Events in the details panel. Filter by name or use search.

All columns are sortable, and items can be deleted in bulk. Use More Actions for individual Edit/Delete, and click Refresh to reload data.

Default Columns: