[bug] Flagd doesn't start when using k8s manifests

[julianocosta89]

Bug Report

Which version of the demo you are using?
84304d3

Symptom

When using the k8s manifests: https://github.com/open-telemetry/opentelemetry-demo/blob/main/kubernetes/opentelemetry-demo.yaml the flagd service doesn't start, and the pod hangs on Init:0/1.

Events:
  Type     Reason       Age                  From               Message
  ----     ------       ----                 ----               -------
  Normal   Scheduled    34m                  default-scheduler  Successfully assigned default/opentelemetry-demo-flagd-5d67ccf97-rmfrn to otel-demo-worker2
  Warning  FailedMount  118s (x24 over 34m)  kubelet            MountVolume.SetUp failed for volume "config-ro" : configmap "opentelemetry-demo-flagd-config" not found

What is the expected behavior?

All services should start and demo should be usable.

What is the actual behavior?

Flagd doesn't start.

Reproduce

kubectl apply -f kubernetes/opentelemetry-demo.yaml

Additional details

I've installed the demo via Helm and all services started fine.
When checking if there was missing changes from Helm in the k8s manifests files I only got this update: #1982

[puckpuck]

When writing the Helm Chart PR to remove the release name prefix, I noticed the same with the install. The solution I used was to add command line arguments to flagd so it would force bind to port 8013 (it was binding to a random port otherwise). I think if we do a make generate-kubernetes-manifest it will resolve this.