Pod restart

Kubernetes pods are designed to maintain a desired state defined in YAML configurations. When changes occur to configurations that affect a pod's runtime environment, Kubernetes initiates pod restarts to ensure the actual state aligns with the desired state. This reconciliation process is fundamental to Kubernetes' operation.

Specifically, modifications to resources such as AgentConfiguration, AgentConnection, and AgentInjector trigger these restarts. These resources define critical aspects of the pod's behavior, including connectivity, settings, and injection rules. When these configurations are updated, Kubernetes detects the discrepancy between the current pod state and the new desired state.

The impact extends to ClusterAgentConnection and ClusterAgentConfiguration too. These cluster-level resources generate AgentConnections and AgentConfigurations within specified namespaces. Therefore, changes to these cluster-level resources cascade down, leading to corresponding updates and restarts of pods in the affected namespaces.

Any change to the pod's configuration, whether direct or indirect through related resources, necessitates a restart to guarantee that the pod reflects the latest defined state within the cluster. This ensures consistency and reliability across the application. It is essential to understand that only the pods affected explicitly by the configuration change will be restarted. For instance, if an AgentInjector targets deployments using a specific label selector, only the pods within those targeted deployments will be restarted, not all pods in the cluster.