As a continuation of https://github.com/cloudfoundry-incubator/eirini/issues/83, it would be useful to have the cloudfoundry.org/application_name, space_name, and org_name annotations on the individual app pods, not just the statefulset. (For context, the Kubernetes filter we use in our Fluentd logging stack only pulls labels/annotations for the pod emitting the log.)
Steps to reproduce
Create an application using an Eirini, and compare the annotations on its statefulset and the resulting pods.
What was expected to happen
The following annotations to be present on the pods:
Description
As a continuation of https://github.com/cloudfoundry-incubator/eirini/issues/83, it would be useful to have the
cloudfoundry.org/application_name
,space_name
, andorg_name
annotations on the individual app pods, not just the statefulset. (For context, the Kubernetes filter we use in our Fluentd logging stack only pulls labels/annotations for the pod emitting the log.)Steps to reproduce
Create an application using an Eirini, and compare the annotations on its statefulset and the resulting pods.
What was expected to happen
The following annotations to be present on the pods:
cloudfoundry.org/application_name
cloudfoundry.org/space_name
cloudfoundry.org/org_name
What actually happened
None of the annotations are present on the pods.