Re: [kubernetes-users] Get current user name in pod yaml file

Yes, I meant dynamically, like I would $USER in linux. Is it possible? On Friday, 10 November 2017 10:55:58 UTC+8, Rodrigo Campos wrote: > > On Thursday, November 9, 2017, lppier > wrote: > >> In my pod yaml file, I need to mount the user's current directory for use >>

[kubernetes-users] Re: Can't stop hundreds of CronJob pods. CronJob no longer exists

The CronJob was not visible because it was under a namespace and it seems you have to provide the namespace. If anyone comes across this in the future, kubectl get cronjobs -n payment kubectl delete cronjob -n payment After running those commands the pods were stopped. -- You received this

[kubernetes-users] Can't stop hundreds of CronJob pods. CronJob no longer exists

I'm running Kubernetes 1.8.1-gke.1 on GCP. I created a cronjob using kubectl apply -f cronjob.yaml. There was an issue with required ENV vars missing, and the container failed to startup. I tried a few more times with different yaml configurations to no avail. I deleted the cronjob using

Re: [kubernetes-users] Getting informations from my Kubernetes

Hello Matheus- I would suggest you run kube-state-metrics and the Prometheus Node Exporter . For example, we run these as Daemon Sets on CoreOS Tectonic and then scrape

Re: [kubernetes-users] Share the IPC namespace between pods

Rodrigo you are correct, that results in a co-location hell. Also that requires careful calculations ahead of time to ensure that you can co-locate the corresponding data partitions (in case of a 1:N, where we have a high-demand database) at all times. Even in case of node failures. Moreover if

[kubernetes-users] Getting informations from my Kubernetes

Hello. I would like to know how I could get my server informations as like CPU, Memory, etc as a JSON using a R script to plot these informations with graphic and etc. If it's not possible, would be possible to get these informations with another language and convert to R after this? The goal

Re: [kubernetes-users] Pod Presets and init containers

Hi Warren, PodPreset doesn't support init containers yet, so behavior you are observing is expected. There is a proposal to add support for init containers in Beta version of PodPreset, but thats not coming out soon. As a workaround, I would recommend exploring Initializers

Re: [kubernetes-users] Container is unable to write to mounted volume

We don't auto-apply ownership changes to hostPath volumes because that would allow, for example, a user to take over /etc. We've considered heuristics like "apply ownership if we make the directory" or "apply ownership if the path is under a flag-defined root", but none of them have been totally

Re: [kubernetes-users] Share the IPC namespace between pods

On Thu, Nov 9, 2017 at 2:27 AM, wrote: > We measured that we lose at least one order of magnitude in terms of latency, > which is our key KPI in this setup. If you are moving from a model where your apps were guaranteed to be colocated into Kubernetes, you are going to

Re: [kubernetes-users] Pod Presets and init containers

I don't find any reason mentioned in the proposal: https://github.com/kubernetes/community/blob/master/contributors/design-proposals/service-catalog/pod-preset.md It seems like an useful question to ask on service catalog sig? Probably with a concrete use case :) On Thursday, November 9, 2017,

[kubernetes-users] Container is unable to write to mounted volume

I created a volume in linux as a certain user and mounted it using the hostPath method. My container is the tensorflow gpu default container, and I am able to see the linux command prompt when I do : kubectl exec -it tf-gpu /bin/bash It logs into the container as root. My issue now is that

Re: [kubernetes-users] Share the IPC namespace between pods

We measured that we lose at least one order of magnitude in terms of latency, which is our key KPI in this setup. Pods are not always on the same host, but we play with co-location a lot. 1:1 mainly. Matthias, Tim, I will get back to you with a decent benchmark on our metals. Thanks so far for

[kubernetes-users] Re: GCP Internal Load Balancer through VPN

On Wednesday, August 2, 2017 at 10:51:44 PM UTC+2, Paul Mazzuca wrote: > Are there any plans to allow access to the IP address of the internal load > balancer for k8s through the Google cloud VPN?   I am able to access the IP > from another computer instance, however not from my VPN connected