Replicate deployment labels to the pod spec template

[jfroy]

The labels on operator-managed Deployments are not replicated in the pod spec template, which means the pods do not have them. This makes it difficult to select those pods for e.g. monitoring, policy enforcement, etc.

Using a kustomize patch is a partial workaround. Most of the labels can be added that way, but some are more difficult because of their dynamic nature (e.g. version).

Also, the app.kubernetes.io/name label is missing on the Deployment, and the app.kubernetes.io/instance label (in my deployment) is set to "flux-system", when it should arguably be set to "flux" (the name of the FluxInstance resource).

[stefanprodan]

The way the operator sets up Flux is identical to the upstream procedure, the deployment spec and pod labels are the same as flux bootstrap so the operator can take over the management without triggering a rollout which could disrupt a production cluster.