Thanks Tim. I'll give it a shot. On Thursday, 5 October 2017 08:59:42 UTC+4, Tim Hockin wrote: > pkg/kubelet/envvars/envvars.go > > Simplest change would probably be a new field, default true, saying > "publish env vars for services". we might want to special case > KUBERNETES_SERVICE_HOST and _PORT because that has deeper roots. > > A short design proposal would be appropriate. > > On Wed, Oct 4, 2017 at 9:50 PM, <kongsl...@gmail.com> wrote: > > Tim, > > > > That would be great if such an optional feature is included. Could you > > point me in the right direction code wise? Maybe I would be able to do a PR. > > > > My request for this feature is purely based on functionality but I see that > > scalability is also a concern according to this Github issue (which you > > have also been involved in): > > > > Pods need to pre-declare service links iff they want the environment > > variables created #1768 > > https://github.com/kubernetes/kubernetes/issues/1768 > > > > > > Regarding environment variables, I also see FOOBAR_PORT: > > > > SCHEMA_REGISTRY_PORT=tcp://10.106.89.94:8081 > > SCHEMA_REGISTRY_PORT_8081_TCP=tcp://10.106.89.94:8081 > > SCHEMA_REGISTRY_PORT_8081_TCP_ADDR=10.106.89.94 > > SCHEMA_REGISTRY_PORT_8081_TCP_PORT=8081 > > SCHEMA_REGISTRY_PORT_8081_TCP_PROTO=tcp > > SCHEMA_REGISTRY_SERVICE_HOST=10.106.89.94 > > SCHEMA_REGISTRY_SERVICE_PORT=8081 > > SCHEMA_REGISTRY_SERVICE_PORT_8081=8081 > > > > On Wednesday, 4 October 2017 20:46:57 UTC+4, Tim Hockin wrote: > >> AFAIK there isn't a way to disable these automatic variables. We've > >> discussed this for a very long time, and maybe it's finally time to > >> add an optional disable for this? Proposals and patches welcome. > >> This should be a pretty easy one, honestly. > >> > >> FWIW, the variables are named `FOOBAR_SERVICE_HOST and > >> FOOBAR_SERVICE_PORT, so the variable you list should not be a problem. > >> > >> > >> > >> On Wed, Oct 4, 2017 at 7:15 AM, <shivani.chan...@gmail.com> wrote: > >> > Can you try to see if unsetting environment variables using the > >> > pod.beta.kubernetes.io/init-containers works (using busybox). > >> > > >> > -- > >> > 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. > > > > -- > > 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.
-- 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.
