CSPL-1044 Full MC configuration/reconfiguration (All deployments other than IDC)

[kashok-splunk]

Full MC configuration/reconfiguration (All deployments other than IDC)
Example to create Standalone with mcRef

apiVersion: enterprise.splunk.com/v1
kind: Standalone
metadata:
  name: s2
  finalizers:
  - enterprise.splunk.com/delete-pvc
spec:
  monitoringConsoleRef:
    name: test

[sgontla]

Do we need this for IDXC? What will be the net effect, if somebody configures this?

[sgontla]

Had a discussion with Kriti:

1. Good to have the MC ref as part of the MC CR, in case if we introduce the Global MC in the future.
2. SHC (even if we have a separate CR in the future) needs the MC reference, as the logic expects both for the Deployer and SHs.
3. IDXC case, each site-specific CR having MC reference can lead to confusion, as different sites can't go to different MCs. The best way is if we can pull this info from the CM CR, by reading it from the API server(?). If that is not feasible, an alternative can be using the configMap(CM writes it, and the site-specific CRs read and use it).

With the above understanding, we can continue using it in the current form(having the MC reference), but the implementation can ignore when dealing with the IDXC, and use it from the CM CR or through a configMap.