Deploy PulseAXN Agent on Kubernetes

Deploy Pulseaxn (Actions Agent) into a Kubernetes cluster in the same namespace as Pulse using the Manager Server deploy addons API, then configure hostname settings via deployment environment variables.

---

Prerequisites

• Pulse is already deployed in the target Kubernetes cluster.
• You have:
  • Manager Server Ingress API endpoint
  • <clustername> as registered in the Manager Server
  • Credentials for the API (-u user:token)
• kubectl access to the cluster.
• Target namespace (referred to below as <pulse_namespace>).

---

Step 1: Deploy Pulseaxn agent using the Deploy Addons API

Run the deploy addons API call:

curl --request PUT \
 --url http://<Ingress API for the Manager Server>/api/v1/mserver/deploy/addons/<clustername> \
 -u "pulse:6Q6+2JxJ6QXORvvHjQakqyEUSM5/KhAFXYBAZsUnJQqCOSUl5VkWeHwfUGekw1z4" \
 --header 'Content-Type: application/json' \
 --data '{
 "addons": [
 "ACTIONS AGENT",
 ],
 "extra_hosts": {
 "ip1": "hostname1",
 "ip2": "hostname2",
 .
 .
 }

Notes:

• addons must be a valid list entry for the Manager Server. Use the exact string expected by your build (example shown: "ACTIONS AGENT").
• extra_hosts is optional; use it when you need static hostname-to-IP mapping (for environments without stable DNS resolution).

---

Step 2: Confirm the Pulseaxn agent pod is deployed

List resources in the Pulse namespace:

kubectl edit deployment ad-axnagent -n <pulse_namespace>

Expected:

• A deployment named similar to ad-axnagent
• A running pod created from that deployment

---

Step 3: Update deployment environment variables (hostname settings)

Edit the deployment:

kubectl edit deployment ad-axnagent -n <pulse_namespace>

Add PULSE_HOSTNAME

Under the container env: section, add:

- name: PULSE_HOSTNAME
- value: adaxn.agent

Set PULSE_HOSTNAME to a unique value to identify this agent instance.

Change AXN_HOSTNAME_METHOD from CMD to ENV

Find and update:

- name: AXN_HOSTNAME_METHOD
- value: ENV

Save and exit. Kubernetes will roll out an updated ReplicaSet and start a new pod automatically.