Hi Anders,
This should be simple although, as always, I would strongly advise testing in a test system and having backups in case of unexpected issues.
If you update the values.yaml file so that DSC is enabled and then run a "helm upgrade" command for your release (pointing to the updated values.yaml file), this should create the new assets required by the DSC without modifying any existing assets. The new assets created will be the deployment(s) and service(s) related to DSC.
Once the DSC pods are available, you will need to modify your ISVA configuration to use it. This means modifying the cluster configuration and then, once this is done, modifying the Reverse Proxy configuration to enable use of DSC.
Jon.
P.S. Which version of ISVA are you currently running? I created an "incubator" chart for v10.0.2.0 which uses the new "lightweight" worker containers. It might be worth looking at this if you haven't already. Make sure to check out the release notes though because some changes will be required to your configuration to use this new version successfully (mainly because of port changes).
------------------------------
Jon Harry
Consulting IT Security Specialist
IBM
------------------------------
Original Message:
Sent: Mon October 25, 2021 04:28 AM
From: Anders Domeij
Subject: Adding the DSC "pod" to an existing installation.
Hi,
Is it possible to modify a running ISVA installed with Helm to a Kubernetes Cluster?
We have a running instance of ISVA that did not enable the DSC initially and would like to add it now.
Thanks in advance
Anders
------------------------------
Anders Domeij
CGI Sweden AB
------------------------------