Updating configuration of .yaml deployment Files

You may want to update the configuration of your cluster. For example, you could change log levels or replicas. To change the configuration or your cluster, take these steps.

Important: If you're using fix pack 2 or earlier, follow the instructions in Updating configuration of .yaml deployment Files

  • (Recommended) If using Helm deployment

    When a new version of a chart is released, or when you want to change the configuration of your release, you can use the helm upgrade command. An upgrade takes an existing release and upgrades it according to the information you provide. Because Kubernetes charts can be large and complex, Helm tries to perform the least invasive upgrade. It will only update things that have changed since the last release. For more information, see 'helm upgrade' and 'helm rollback': Upgrading a Release, and Recovering on Failure on the Helm Docs site.

    Procedure

    Navigate to the directory where the Helm chart is located (./production/helm-deployment). To upgrade the Z APM Connect DG or modify your configuration, run the helm upgrade command, including the release name and chart path as arguments.

    helm upgrade --namespace <desired project> -f <config yaml> <name> <chart location>

    For example,

    helm upgrade --namespace ibm-zapm -f values.yaml zapm ./zapm-helm-chart-6.1.1-6.tgz
  • If using manifests deployment

    Procedure

    1. Update the YAML files with the changes. For detailed information on how to update the YAML files, see Populating deployment files.

    2. After making the updates, navigate to the deployments folder (./production/manifests-deployment).

    3. Run the command kubectl apply -f ./ to apply the updated configuration.

    Note: Using apply is the recommended method to update the configuration. However, if you encounter any errors during the process, you may need to clean up the existing deployments. To do this, run kubectl delete -f ./ to stop and remove the current deployment. Once the cleanup is complete, you can reapply the configuration by running kubectl apply -f ./ again.