call
Go to Console

 

 

 

Kubernetes Console Guide

 

This page provides a complete guide to using the Kubernetes entity of the Namirasoft Infra Console. You will find a detailed explanation of how Kubernetes clusters are connected and structured for infrastructure monitoring, along with descriptions of each field used when creating and managing Kubernetes configurations. Use this guide to understand how Kubernetes connections allow Namirasoft Infra to collect operational data from container orchestration environments and serve as a connection method for other infrastructure components.

 

What Is a Kubernetes?

A Kubernetes in Namirasoft Infra represents a connection configuration that allows the platform to access and structure operational data from Kubernetes clusters. Kubernetes is a system for automating the deployment, scaling, and management of containerized applications (applications that run in isolated software containers).

 

Kubernetes configurations serve two primary purposes in Namirasoft Infra:

 

  • Direct Cluster Monitoring: They define how Namirasoft Infra communicates with your clusters to collect information about containers, pods, nodes, services, and other Kubernetes resources. This data includes performance metrics, health status, resource utilization, and operational events that are essential for monitoring containerized workloads.

 

  • Connection Method for Other Services: Kubernetes configurations also serve as a connection bridge to access other infrastructure components running inside Kubernetes clusters. When connecting to services like databases, caches, or messaging systems that are deployed within Kubernetes, users can select “Kubernetes” as the connection type, which then uses this Kubernetes configuration to establish the connection.

 

Each Kubernetes configuration belongs to a specific Project and Environment, ensuring that container monitoring data remains organized according to your operational context. By connecting Kubernetes clusters, Namirasoft Infra provides visibility into how your containerized applications are performing across development, staging, and production environments.

The Challenge in Managing Kubernetes Infrastructure

Kubernetes environments can be complex, with many moving parts including nodes, pods, services, deployments, and namespaces. As organizations scale their containerized applications, managing and monitoring these distributed systems becomes increasingly challenging.

 

Without proper Kubernetes monitoring, teams often face several problems:

 

  • Visibility Gaps: Difficulty seeing what’s happening inside containers and across the entire cluster

 

  • Access Complexity: Hard to establish consistent connection methods to services running inside Kubernetes

 

  • Resource Management: Challenges in optimizing CPU and memory allocation across containers

 

  • Connection Fragmentation: Different methods needed to access services based on their deployment location (direct, via server, or via Kubernetes)

 

  • Scale Complexity: Monitoring becomes harder as the number of containers grows into hundreds or thousands

 

While Kubernetes provides basic monitoring tools, they often don’t integrate well with broader infrastructure monitoring or provide the intelligent analysis needed for proactive operations.

How Namirasoft Infra Solves the Problem

Namirasoft Infra addresses Kubernetes monitoring challenges through structured Kubernetes configurations that provide comprehensive visibility into your container environments while also serving as a unified connection method.

 

Kubernetes configurations establish a secure connection between Namirasoft Infra and your clusters, enabling two-way communication:

 

  • Data Collection Outward: Namirasoft Infra collects detailed operational data from the cluster including container performance metrics, pod health status, node resource utilization, and deployment information.

 

  • Access Inward: Other infrastructure components can use the Kubernetes configuration as a connection method to access services running inside the cluster. This eliminates the need for separate connection setups for each service.

 

All collected data is structured and delivered to Namirasoft Expert, where it can be analyzed alongside other infrastructure data for complete situational awareness. By treating Kubernetes as both a monitoring target and a connection gateway, Namirasoft Infra provides a unified approach to managing containerized environments.

Overview of Server Fields and Options

Below is a detailed explanation of the fields available when creating or managing a Kubernetes configuration. Understanding these fields helps ensure your Kubernetes clusters are properly connected and structured for monitoring and operational analysis.

 

  • ID (string): This is a unique identifier automatically assigned to the Kubernetes configuration when it is created. Users cannot modify or manually define this value.

 

  • User ID (Namirasoft Account’s ID): This is the unique identifier assigned to the Namirasoft Account user who owns the Kubernetes configuration. It is used internally to track who created and has access to this Kubernetes monitoring setup.

 

  • Workspace ID (Namirasoft Workspace’s ID): This refers to a workspace created in the Namirasoft Workspace app, which identifies the workspace where the Kubernetes configuration is created. This ensures your Kubernetes monitoring is organized within the correct workspace.

 

  • Service User ID (string): This is an internal identifier used by Namirasoft Infra to manage service-level access to the Kubernetes cluster. Think of this as a special service account that Namirasoft Infra uses to securely connect to and monitor your Kubernetes environment without requiring personal credentials.

 

  • Service Session ID (string): This is a unique session identifier generated for each monitoring connection to the Kubernetes cluster. Similar to a unique meeting link, this identifier ensures secure, traceable communication between Namirasoft Infra and your Kubernetes environment for each monitoring session.

 

  • Name (String): This is a human-readable label used to identify the Kubernetes configuration. The name helps teams distinguish between multiple Kubernetes clusters.

 

  • Cloud (Enum): This field specifies which cloud provider hosts the Kubernetes cluster. Selecting the correct provider ensures proper integration with cloud-specific Kubernetes services and features.

 

    • AWS (Amazon Web Services): Amazon Web Services is a cloud computing platform providing infrastructure services such as virtual servers, storage, networking, and managed application services.

 

    • GCP (Google Cloud Platform): Google Cloud Platform provides cloud infrastructure services including computing, container orchestration, storage, and distributed application services.

 

    • Azure (Microsoft Azure): Microsoft Azure is a cloud computing platform that provides infrastructure, platform services, and application hosting environments.

 

    • Other: This option is used when connecting private cloud environments or cloud providers that are not AWS, GCP, or Azure. Users typically select this option for custom infrastructure or unsupported cloud platforms.

 

  • Project (Enum): This field specifies which Project the Kubernetes configuration belongs to. A Project is a logical container that groups related infrastructure components together, similar to how a folder organizes related files.

 

You must create a Project before creating a Kubernetes configuration. If no Project exists, you can click the “+” icon next to this field, which redirects you to the Project configuration page. For more information about Projects, visit the Project Console Guide.

 

  • Environment (Enum): This field specifies which Environment the Kubernetes cluster operates within. An Environment represents a stage in your development lifecycle, such as production (live systems), staging (final testing), or development (early development work).

 

You must create an Environment before creating a Kubernetes configuration. If no Environment exists, you can click the “+” icon next to this field, which redirects you to the Environment configuration page. For more information about Environments, visit the Environment Console Guide.

 

  • Log Group (Enum): A Log Group is a logical container that stores and organizes log files from your applications and systems in Namirasoft Log. In the context of Kubernetes, this Log Group will contain logs from all containers running in the cluster.

 

You can click the “+” icon next to this field to create a new Log Group if one doesn’t exist. For more information about Log Groups and log management, visit Namirasoft Log.

 

  • Agent Pod Installation Enabled (Yes/ No): When enabled, Namirasoft Infra automatically deploys an Agent Pod inside your Kubernetes cluster. This Agent Pod collects operational metrics, logs, and other telemetry data, eliminating the need for pre-configured servers for Kubernetes communication.

 

  • Description (String): This field allows you to document the purpose, role, or special characteristics of the Kubernetes cluster. It helps teams understand the cluster’s function within your infrastructure.

 

  • Kubectl Conneect Type (Enum): This field defines how Namirasoft Infra connects to your Kubernetes cluster to execute kubectl commands. The selected connection type determines the authentication method, required configuration fields, and how commands are executed against the cluster.

 

Users should choose the connection type that matches how their Kubernetes cluster is deployed and accessed.

 

    • Agent Pod: This connection type allows Namirasoft Infra to connect to the Kubernetes cluster through a monitoring agent deployed inside the cluster. The agent securely communicates with Namirasoft Infra and executes kubectl commands internally, eliminating the need for external authentication or server configuration.

 

This method is recommended for users who prefer cluster-native monitoring or operate in restricted network environments.

 

    • Pre-Configured Server: This connection type allows Namirasoft Infra to connect to the Kubernetes cluster through a server that has already been configured with Kubernetes access. The server acts as an execution environment where kubectl commands are run.

 

This method is useful when organizations already maintain administrative or bastion servers that manage Kubernetes clusters.

 

      • Connect Server (Enum): This field specifies the server resource that will execute kubectl commands to communicate with the Kubernetes cluster.

 

The selected server must:

 

        • Have kubectl installed

 

        • Already be authenticated with the Kubernetes cluster

 

        • Have network access to the Kubernetes API server

 

If no server exists, users can create one from Server entity. For more information, visit Server Configuration Guide.

 

    • AWS CLI: This connection type uses AWS command-line authentication to connect to an Amazon Elastic Kubernetes Service (EKS) cluster. Namirasoft Infra retrieves cluster configuration using AWS credentials and then executes kubectl commands through a selected server.

 

This method is recommended for users running Kubernetes clusters on AWS EKS.

 

      • Credential (Enum): This field specifies the AWS credential stored in Namirasoft Credential. The credential must have permissions to access EKS cluster configuration and authentication services.

 

Users must first connect their AWS account using the Namirasoft Credential. For more information, visit Namirasoft Credential How It Works page.

 

      • Region (String): This field specifies the AWS region where the EKS cluster is deployed. The region ensures Namirasoft Infra connects to the correct geographic AWS environment.

 

Where to Find AWS Region?

 

 

        • Open Amazon EKS

 

        • The region appears in the top-right corner of the console

 

      • Cluster Name (String): This field defines the exact name of the Amazon EKS cluster that will be monitored.

 

Where to Find AWS Cluster Name?

 

 

        • Navigate to EKS → Clusters

 

        • Select your cluster

 

        • The cluster name appears on the overview page

 

        • Example: production-eks-cluster

 

      • Kubectl Runs on Server (Enum): This field specifies which server executes kubectl commands after AWS authentication is completed.

 

The selected server must have:

 

          • Network access to AWS Kubernetes endpoints

 

          • kubectl installed

 

If no server exists, users can create one from Server entity. For more information, visit Server Configuration Guide.

 

 

    • Azure CLI: This connection type uses Microsoft Azure authentication to connect to an Azure Kubernetes Service (AKS) cluster. Namirasoft Infra retrieves cluster credentials through Azure APIs and then executes monitoring commands through a selected server.

 

      • Credential (Enum): This field specifies the Azure credential stored in Namirasoft Credential. The credential must allow access to Azure Kubernetes Service resources.

 

Users must first connect their Azure account using the Namirasoft Credential. For more information, visit Namirasoft Credential How It Works page.

 

      • Subscription ID (String): This field identifies which Azure subscription contains the Kubernetes cluster.

 

Where to Find Azure Subscription ID?

 

 

        • Navigate to Subscriptions

 

        • Select your subscription

 

        • Copy the Subscription ID

 

 

 

      • Group Name (String): This field specifies the Resource Group that contains your AKS cluster.

 

Where to Find Azure Resource Group Name?

 

 

        • Navigate to Kubernetes Services

 

        • Select your cluster

 

        • Resource Group appears in cluster overview

 

      • Cluster Name (String): This field defines the name of the Azure Kubernetes Service cluster.

 

Where to Find Azure Cluster Name?

 

 

        • Navigate to Kubernetes Services

 

        • Select your cluster

 

        • The cluster name appears there

 

      • Kubectl Runs on Server (Enum): This field specifies the server used to execute kubectl commands after Azure authentication is completed.

 

The selected server must have:

 

          • Have Azure CLI installed

 

          • kubectl installed

 

          • Be authenticated to Azure

 

If you have not added your Servers in Namirasoft Infra, you can create one from Server entity. For more information, visit Server Configuration Guide.

 

 

    • GCP CLI: This connection type allows Namirasoft Infra to connect to Google Kubernetes Engine (GKE) clusters using Google Cloud authentication. Cluster configuration and credentials are retrieved using GCP APIs.

 

      • Credential (Enum): This field specifies the Google Cloud credential stored in Namirasoft Credential. The credential must allow access to Google Kubernetes Engine.

 

Users must first connect their GCP account using the Namirasoft Credential. For more information, visit Namirasoft Credential How It Works page.

 

      • Project ID (String): This field defines the Google Cloud project that contains the Kubernetes cluster.

 

Where to Find Google Cloud Project ID?

 

 

        • From the projects list, select Manage all projects.

 

        • The names and IDs for all the projects are displayed.

 

      • Region Name (String): This field specifies the region or zone where the GKE cluster is deployed.

 

Where to Find Google Cloud Region Name?

 

 

        • Navigate to Kubernetes Engine → Clusters

 

        • Select your cluster

 

        • The region is listed in the cluster details

 

      • Cluster Name (String): This field specifies the name of the GKE cluster.

 

Where to Find Google Cloud Cluster Name?

 

 

        • Navigate to Kubernetes Engine

 

        • Select your cluster

 

        • The cluster name appears there

 

      • Kubectl Runs on Server (Enum): This field specifies the server used to execute GCP CLI and kubectl commands.

 

The selected server must have:

 

          • Have Google Cloud CLI installed

 

          • kubectl installed

 

          • Be authenticated to GCP

 

If you have not added your Servers in Namirasoft Infra, you can create one from Server entity. For more information, visit Server Configuration Guide.

 

 

    • Client Certificate Authentication: This connection type allows Namirasoft Infra to securely identify itself to your Kubernetes cluster using trusted digital certificates instead of usernames, passwords, or cloud logins, which is required in private or security-restricted environments..

 

      • Kubernetes API Server Endpoint (String): This field specifies the network address of your Kubernetes API Server. It is the primary communication endpoint that Namirasoft Infra uses to send monitoring requests to your cluster.

 

This value typically looks like: https://192.168.1.10:6443 or https://k8s.example.internal:6443

 

How can I find Kubernetes API Server Endpoint?

 

        • Access the machine where kubectl is installed and already configured.

 

        • Open your terminal.

 

        • Run the following command:
          kubectl config view

 

        • Locate the following section in the output:

          clusters:
            - cluster:
                 server: https://XXX.XXX.XXX.XXX:6443

 

        • Copy the full value listed after server:

 

        • Paste it into the Kubernetes API Server Endpoint field.

 

      • Client Certificate (String): The Client Certificate is used to identify Namirasoft Infra as an authorized user when connecting to the Kubernetes API Server.

 

How Can I Get Client Certificate?

 

        • Run the following command:
          kubectl config view --raw

 

        • Locate one of the following:

          client-certificate-data:

          OR

          client-certificate: /path/to/client.crt

 

        • If you see a file path:

 

          • Open the referenced .crt file using a text editor.

 

          • Copy the entire certificate content.

 

        • Paste the copied value into the Client Certificate field.

 

Namirasoft Infra will automatically encrypt and store this value in Namirasoft Secret. For more information, visit Namirasoft Secret website.

 

      • Client Private Key (String): The Private Key is used together with the Client Certificate to cryptographically sign requests sent to the Kubernetes API Server.

 

How to Find Client Private Key?

 

        • Run the following command:
          kubectl config view --raw

 

        • Locate:

          client-key-data:

          OR

          client-key: /path/to/client.key

 

        • If you see a file path:

 

          • Open the referenced .key file.

 

          • Copy the entire key content.

 

        • Paste the copied value into the Client Private Key field.

 

Namirasoft Infra will automatically encrypt and store this value in Namirasoft Secret. For more information, visit Namirasoft Secret website.

 

      • Cluster CA Certificate (String): The Cluster CA Certificate allows Namirasoft Infra to verify the identity of the Kubernetes API Server before establishing a trusted connection.

 

Where to Find Cluster CA Certificate?

 

        • Run:
          kubectl config view --raw

 

        • Locate:

          certificate-authority-data:

          OR

          certificate-authority: /path/to/ca.crt

 

        • If you see a file path:

 

          • Open the referenced .crt file.

 

          • Copy the entire certificate content.

 

        • Paste the copied value into the Cluster CA Certificate field.

 

Namirasoft Infra will automatically encrypt and store this value in Namirasoft Secret. For more information, visit Namirasoft Secret website.

 

      • Kubectl Runs on Server (Enum): This field specifies the Server used to execute Kubernetes communication and kubectl commands using certificate-based authentication.

 

The selected server must:

 

          • Have kubectl installed

 

          • Have network access to the Kubernetes API Server Endpoint

 

          • Be located inside the same network or VPC as the Kubernetes cluster (if the endpoint is private)

 

          • Be allowed to communicate with the Kubernetes control plane

 

If you have not added your Servers in Namirasoft Infra, you can create one from Server entity. For more information, visit Server Configuration Guide.

 

 

    • OIDC SSO: This authentication method allows Namirasoft Infra to securely communicate with your Kubernetes cluster using your organization’s Identity Provider (IdP), such as enterprise authentication systems. Instead of using static credentials or certificates, this method verifies identity through a trusted login provider and grants access using secure authentication tokens.

 

      • Kubernetes API Server Endpoint (String): This is the network address used to access the Kubernetes control plane. It allows Namirasoft Infra to send operational commands to your cluster.

 

This value typically looks like: https://192.168.1.10:6443 or https://k8s.example.internal:6443

 

How to Find Kubernetes API Server Endpoint?

 

        • On the machine where Kubernetes CLI is configured, run:
          kubectl config view --raw

 

        • Locate the following section in the output:

          clusters:

 

        • Find the line that starts with:

          server:

 

        • Copy the full HTTPS address shown after server:.

 

        • Paste the copied value into the Kubernetes API Server Endpoint field.

 

      • OIDC Issuer URL (String): This is the URL of your organization’s Identity Provider that issues authentication tokens for Kubernetes access. It tells Kubernetes where to verify login tokens.

 

How to Find OIDC Issuer URL?

 

        • Sign in to your Identity Provider dashboard (such as Azure AD or another OIDC provider).

 

        • Navigate to the OpenID Connect or Application Registration section.

 

        • Locate the full Issuer URL or Provider URL.

 

        • Copy the full Issuer URL.

 

        • Paste the copied value into the OIDC Issuer URL field.

 

      • Client ID (String): This refers to the stored identifier used by Kubernetes to recognize the requesting application during authentication.

 

Because this field contains sensitive information, it will be encrypted and securely stored in Namirasoft Secret after configuration. For more information, visit Namirasoft Secret website.

 

How to Get OIDC SSO Client ID?

 

        • Sign in to your Identity Provider dashboard (such as Azure AD or another OIDC provider).

 

        • Navigate to the Kubernetes authentication application.

 

        • Locate the Client ID.

 

        • Copy the Client ID value.

 

        • Paste the copied value into the Client ID field.

 

      • Client Secret (String): This refers to the confidential key used alongside the Client ID during the authentication process.

 

Because this field contains sensitive information, it will be encrypted and securely stored in Namirasoft Secret after configuration. For more information, visit Namirasoft Secret website.

 

How to Get OIDC SSO Client Secret?

 

        • Sign in to your Identity Provider dashboard (such as Azure AD or another OIDC provider).

 

        • Navigate to the Kubernetes authentication application.

 

        • Locate or Generate the Client Secret.

 

        • Copy the Client Secret value.

 

        • Paste the copied value into the Client Secret field.

 

      • Username (String): This represents the authenticated user identity used when accessing the Kubernetes cluster.

 

Because this field contains sensitive information, it will be encrypted and securely stored in Namirasoft Secret after configuration. For more information, visit Namirasoft Secret website.

 

How to Find the Username?

 

        • Sign in to your Identity Provider dashboard (e.g., Azure AD, Keycloak, Okta, or other OIDC provider).

 

        • Navigate to the Application Registration or App Client section where your Kubernetes authentication app is configured.

 

        • Look for the field labeled Username, Service Account, or Client Login.

 

            • This is often the name assigned to the service account or application user in the OIDC provider.

 

            • In Azure AD, it is typically the Application (client) ID or the Managed Identity username.

 

            • In Azure AD, it is typically the Application (client) ID or the Managed Identity username.

 

        • Copy this username exactly as it appears and Paste it in the Username field.

 

Namirasoft Infra will automatically encrypt and store this value in Namirasoft Secret. For more information, visit Namirasoft Secret website.

 

      • Cluster CA Certificate (String): This refers to the certificate authority data used to verify that communication with the Kubernetes API server is secure and trusted.

 

Because this field contains sensitive information, it will be encrypted and securely stored in Namirasoft Secret after configuration. For more information, visit Namirasoft Secret website.

 

Hot to Find Cluster CA Certificate?

 

        • On the machine where Kubernetes CLI is configured, run:
          kubectl config view --raw

 

        • Locate one of the following sections:

          certificate-authority-data:

          OR

          certificate-authority: /path/to/ca.crt

 

        • If a file path is provided:

 

          • Open the referenced .crt file.

 

          • Copy the entire certificate content.

 

        • Paste the copied value into the Cluster CA Certificate field.

 

      • Kubectl Runs on Server (Enum): This field specifies the Server that Namirasoft Infra will use to execute Kubernetes communication and kubectl commands using OIDC SSO authentication.

 

The selected Server must meet the following requirements:

 

          • Have kubectl installed

 

          • Have network access to the Kubernetes API Server Endpoint

 

          • Be located inside the same network or VPC as the Kubernetes cluster (if the endpoint is private)

 

If you have not added your Servers in Namirasoft Infra, you can create one from Server entity. For more information, visit Server Configuration Guide.

 

 

    • Kubeconfig File: This authentication method allows Namirasoft Infra to securely communicate with your Kubernetes cluster using a pre-generated kubeconfig file. This method is often used when users already have a configured kubeconfig that contains all necessary credentials and cluster access details.

 

      • Kubernetes API Server Endpoint (String): This is the network address of your Kubernetes control plane. Namirasoft Infra uses this endpoint to send operational commands to your cluster. Its typical format is like the ones below:
        https://192.168.1.10:6443
OR

https://k8s.example.internal:6443

 

How to Find Kubernetes API Server Endpoint?

 

        • On the machine where Kubernetes CLI is configured, run:
          kubectl config view --raw

 

        • Locate the following section in the output:

          clusters:

 

        • Find the line that starts with:

          server:

 

        • Copy the full HTTPS address shown after server:.

 

        • Paste the copied value into the Kubernetes API Server Endpoint field.

 

      • File Content (String): This refers to the kubeconfig file content used to authenticate with the Kubernetes cluster.

 

Because this field contains sensitive information, it will be encrypted and securely stored in Namirasoft Secret after configuration. For more information, visit Namirasoft Secret website.

 

How to Get File Content?

 

        • Locate your kubeconfig file on your machine, usually at:
~/.kube/config

 

        • Open the kubeconfig file with a text editor.

 

        • Copy the content of the file and Paste it in this field.

 

 

      • Cluster CA Certificate (String): This refers to the certificate authority data used to verify that communication with the Kubernetes API server is secure and trusted.

 

Because this field contains sensitive information, it will be encrypted and securely stored in Namirasoft Secret after configuration. For more information, visit Namirasoft Secret website.

 

Hot to Find Cluster CA Certificate?

 

        • On the machine where Kubernetes CLI is configured, run:
          kubectl config view --raw

 

        • Locate one of the following sections:

          certificate-authority-data:

          OR

          certificate-authority: /path/to/ca.crt

 

        • If a file path is provided:

 

          • Open the referenced .crt file.

 

          • Copy the entire certificate content.

 

        • Paste the copied value into the Cluster CA Certificate field.

 

      • Kubectl Runs on Server (Enum): This field specifies the Server that Namirasoft Infra will use to execute Kubernetes communication and kubectl commands using Kubeconfig File authentication.

 

The selected Server must meet the following requirements:

 

          • Have kubectl installed

 

          • Have network access to the Kubernetes API Server Endpoint

 

          • Be located inside the same network or VPC as the Kubernetes cluster (if the endpoint is private)

 

If you have not added your Servers in Namirasoft Infra, you can create one from Server entity. For more information, visit Server Configuration Guide.

 

 

  • IP Public (String): This field displays the public IP address associated with the Kubernetes cluster, as discovered by Namirasoft Infra during the initial connection. For Kubernetes clusters, this is typically the IP address of the API server or load balancer that allows external access to the cluster.

 

  • Last Seen At (DateTime): This field shows the date and time when Namirasoft Infra last detected any activity or communication from the Kubernetes cluster. This indicates the most recent time the cluster was active and responsive to monitoring requests.

 

  • Last Online At (DateTime): This field shows the date and time when the Kubernetes cluster was last in an “online” or healthy state. This timestamp updates whenever the cluster transitions from an offline or unhealthy state back to a fully operational state.

 

  • Last Offline At (DateTime): This field shows the date and time when the Kubernetes cluster was last in an “offline” or unhealthy state. This timestamp updates whenever the cluster becomes unreachable or experiences significant health issues.

 

  • Meta Collective (JSON): This field contains a collection of metadata automatically gathered from the Kubernetes cluster. This metadata includes information such as cluster version, node details, installed add-ons, and configuration settings. Think of this as a comprehensive information packet about your cluster’s setup and configuration.

 

  • Meta Derivative (JSON): This field contains derived metrics and calculated values based on the raw data collected from the Kubernetes cluster. These might include performance trends, utilization patterns, or health scores that are computed by Namirasoft Infra to provide deeper insights into your cluster’s behavior.

 

  • Created At (DateTime): This shows the date and time when the Kubernetes configuration was created. This value is automatically generated and cannot be modified, providing an audit trail of when the cluster was added to monitoring.

 

  • Updated At (DateTime): This shows the date and time when the Kubernetes configuration was last updated. The value changes automatically whenever configuration details are modified or when significant changes to the cluster’s status occur, helping track configuration changes over time.

Keep Your Infrastructure Running Smoothly and Reliably

Get Started Now Explore Console Guide