As the subject says, I would like to avoid that Kubernetes populates a pod with the environment variables for known services. They interfere with some external container images that I am trying to get up and running on Kubernetes.
As an example, confluentinc/cp-schema-registry:3.3.0-1, exits with an error if SCHEMA_REGISTRY_PORT is defined. See https://github.com/confluentinc/cp-docker-images/blob/3.3.x/debian/schema-registry/include/etc/confluent/docker/configure Is it somehow possible to deactivate this populate feature? I'd prefer that over e.g. replacing the image's entry script or rolling my own image. I haven't been able to find anything in the official documentation but maybe I've overlooked it? Best regards, Jonas Kongslund -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
