feat(operator): fetch cluster name from providers

[rootxrishabh]

Purpose of PR?:

This PR adds fetching cluster name from cluster providers.

Does this PR introduce a breaking change?
No
If the changes in this PR are manually verified, list down the scenarios covered::

Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs

Checklist:

• Bug fix. Fixes #
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• PR Title follows the convention of <type>(<scope>): <subject>
• Commit has unit tests
• Commit has integration tests

[Prateeknandle]

what happens in case there is no operator, should we have a fallback logic in kubearmor?
cc: @daemon1024

[rootxrishabh]

Yes, cluster name goes to "default".

[Prateeknandle]

Yes, cluster name goes to "default".

@rootxrishabh i meant shouldn't we fetch cluster name from providers in case operator is not there?

[rksharma95]

@rootxrishabh can you please add args handling in operator helm chart? It should support any args list values.

[Prateeknandle]

Tested on both GKE and AWS, working as expected.

[rksharma95]

@Prateeknandle @rootxrishabh does kubearmor uses clusterName value from cofigmap?

[Prateeknandle]

@Prateeknandle @rootxrishabh does kubearmor uses clusterName value from cofigmap?

No, sry totally forgot this point, @rootxrishabh we should update cluster name in kubearmor, it should get updated based on conifgmap value.
https://github.com/Prateeknandle/KubeArmor/blob/main/KubeArmor/core/kubeUpdate.go#L2749

check whether correct cluster name is reflected in alerts/logs or not.

[rksharma95]

LGTM