admission-controller: Allow to configure clusterName

[ChristianCiach]

We are trying to run the admission-controller inside our Rancher K3s clusters, but it logs this:

clusterinfo: Failed to find cluster name" "providers"=["ec2v2MetadataProvider","ec2MetadataProvider","eksctlProvider","ecsFargateMetadataProvider","azureMonitorAgentProvider","azureMetadataProvider │
│ ","azureLabelProvider","gcpMetadataProvider","ocpProvider"]

The Helm Chart allows to configure the clusterName: CrowdStrike/falcon-helm@811891e

[evanstoner]

Tracked internally - but we'll see if engineering can verify that you can create the falcon-kac-meta ConfigMap manually to work around this.

[ChristianCiach]

but we'll see if engineering can verify that you can create the falcon-kac-meta ConfigMap manually to work around this.

Thanks! I've already figured out that this workaround does work indeed. But this doesn't integrate well into our deployment pipelines, for similar reasons as #567 (Namespace must exist at the time of the initial deployment)

We've reverted back to use the Helm charts (with post-processing using Kustomize), but I will keep an eye on the operator, as I try to move away from Helm as much as possible.