This guide provides instructions for updating the Kubernetes 2.0 OpsRamp Agent using Helm. It includes step-by-step instructions for both Helm version 3.10.0 or later and earlier versions. It also cover guidance on modifying configuration keys, updating to the specific versions, and handling custom settings for proxy servers and ports.
For Helm Version 3.10.0 or Above
- To upgrade the Kubernetes 2.0 Agent to the latest helm version, use the following command:
For example, if the release name ishelm upgrade <release-name> <helm-repo-url> --reset-then-reuse-values
opsramp
, the command will be:helm upgrade opsramp oci://us-docker.pkg.dev/opsramp-registry/agent-helm-charts/agent --reset-then-reuse-values
The above command will upgrade the Agent to the latest helm version available in the OpsRamp Agent Helm Repository.
To upgrade the Kubernetes 2.0 Agent to a specific helm version, use the
--version
flag in the command.
For example, to upgrade to helm version0.1.0
, use:helm upgrade opsramp oci://us-docker.pkg.dev/opsramp-registry/agent-helm-charts/agent --version 0.1.0 --reset-then-reuse-values
If the
opsramp-master
agent pod does not restart automatically after the upgrade, run:kubectl rollout restart deployment opsramp-master
Change Agent Configuration Keys
To modify any keys in the opsramp-agent-config
configMap, use the Helm upgrade command with the current agent version.
For example, if you want to change the proxy server and port, run:
helm upgrade opsramp-agent oci://us-docker.pkg.dev/opsramp-registry/agent-helm-charts/agent --version 0.1.0 --reset-then-reuse-values --set agent.config.proxy.server="172.24.5.7",agent.config.proxy.port="3128"
Note
Ensure that the--version
flag matches the currently installed Helm version.For Helm Versions Below 3.10.0
- To upgrade the Kubernetes 2.0 Agent to the latest helm version, use the following command:
For example, if the release name ishelm get values my-release -o yaml > /tmp/opsramp-current-values.yaml helm upgrade <release-name> <helm-repo-url> --reset-values -f /tmp/opsramp-current-values.yaml rm /tmp/opsramp-current-values.yaml
opsramp
, the command will be:helm get values my-release -o yaml > /tmp/opsramp-current-values.yaml helm upgrade opsramp oci://us-docker.pkg.dev/opsramp-registry/agent-helm-charts/agent --reset-values -f /tmp/opsramp-current-values.yaml rm /tmp/opsramp-current-values.yaml
The above command will upgrade the Agent to the latest helm version available in the OpsRamp Agent Helm Repository.
To upgrade the Kubernetes 2.0 Agent to a specific helm version, use the
--version
flag in the command.
For example, to upgrade to helm version0.1.0
, use:helm get values my-release -o yaml > /tmp/opsramp-current-values.yaml helm upgrade opsramp oci://us-docker.pkg.dev/opsramp-registry/agent-helm-charts/agent --version 0.1.0 --reset-values -f /tmp/opsramp-current-values.yaml rm /tmp/opsramp-current-values.yaml
If the
opsramp-master
agent pod does not restart automatically after the upgrade, run:kubectl rollout restart deployment opsramp-master
Change Agent Configuration Keys
To modify any keys in the opsramp-agent-config
configMap, use the Helm upgrade command with the current agent version.
For example, if you want to change the proxy server and port, run:
helm get values my-release -o yaml > /tmp/opsramp-current-values.yaml
helm upgrade opsramp-agent oci://us-docker.pkg.dev/opsramp-registry/agent-helm-charts/agent --version 0.1.0 --reset-values -f /tmp/opsramp-current-values.yaml --set agent.config.proxy.server="172.24.5.7",agent.config.proxy.port="3128"
rm /tmp/opsramp-current-values.yaml
Note
Ensure that the--version
flag matches the currently installed Helm version.