You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on #7290 I noticed that renaming a policy ID does not trigger a "restart" of the Agent Pods. The FLEET_ENROLLMENT_TOKEN is provided as an environment variable, and therefore requires a new Pod to be created to read the new value.
apiVersion: v1kind: Secretmetadata:
creationTimestamp: "2024-10-18T12:42:54Z"labels:
agent.k8s.elastic.co/name: elastic-agentcommon.k8s.elastic.co/type: agenteck.k8s.elastic.co/credentials: "true"name: elastic-agent-agent-envvarsnamespace: elasticstringData:
FLEET_ENROLLMENT_TOKEN: REDACTED // This is going to be updated correctly by the Agent controllertype: Opaque
While working on #7290 I noticed that renaming a policy ID does not trigger a "restart" of the Agent Pods. The
FLEET_ENROLLMENT_TOKEN
is provided as an environment variable, and therefore requires a new Pod to be created to read the new value.Note that one other problem is that the "old" policies are never deleted and the related tokens remain valid.
The text was updated successfully, but these errors were encountered: