CSPL-2353 - Bias lang update

[akondur]

Change master-uri to manager-uri.

Verified using the Splunk Operator for a c3 SVA deployment.

License Manager and Cluster Manager URI on an indexer pod:

[splunk@splunk-idxc-example-indexer-1 splunk]$ cat etc/system/local/server.conf | grep -i manager_uri -B2

[license]
manager_uri = https://splunk-lm-example-license-manager-service:8089
--

[clustering]
manager_uri = https://splunk-cm-example-cluster-manager-service:8089

Search head has the correct URI as well:

[splunk@splunk-shc-example-search-head-0 local]$ cat server.conf | grep -i manager_uri -B 2

[license]
manager_uri = https://splunk-lm-example-license-manager-service:8089
--

[clustering]
manager_uri = https://splunk-cm-example-cluster-manager-service:8089

[sgontla]

Just for my understanding from the Operator point of view, do we need to tie any Operator changes to this? What happens if the customer just updates the Splunk docker image with this changes? Also, If we have any Operator specific changes(?), what happens if the customer just updates the Operator alone?

[akondur]

Just for my understanding from the Operator point of view, do we need to tie any Operator changes to this? What happens if the customer just updates the Splunk docker image with this changes? Also, If we have any Operator specific changes(?), what happens if the customer just updates the Operator alone?

@sgontla Good point. We are changing only the cli and conf file changes syntax here from master to manager. As far as operator is concerned we should be able to continue using the same config and ansible underneath will use manager vs master to configure splunkd.

Just for my understanding from the Operator point of view, do we need to tie any Operator changes to this? What happens if the customer just updates the Splunk docker image with this changes? Also, If we have any Operator specific changes(?), what happens if the customer just updates the Operator alone?