Mark, Are you looking at the /etc/kubernetes/manifests directory on the master or on the nodes?
On Fri, Jul 1, 2016 at 5:29 AM, Mark <[email protected]> wrote: > Hi Vishnu, thanks! I was able to limit fluentd logger and the proxy pods > in the /etc/kubernetes/manifests directory successfully. I didn't see a > config file in there for the DNS pod for example, are you able to change > those as well? > > > On Thursday, 30 June 2016 19:09:27 UTC-4, Vishnu Kannan wrote: >> >> Hi Mark, >> >> The configs used for kube-system pods are stored inside >> `/etc/kubernetes/` directory on the master node. There is a process running >> on the master that ensures that these system pods match those configs. If >> you have access to master, you can update those config files directly. >> >> >> On Wednesday, June 29, 2016 at 7:21:34 PM UTC-7, Mark wrote: >>> >>> Hi, Upon creating a cluster it creates a bunch of default pods under the >>> "kube-system" namespace, (fluentd-cloud-logging-gke, kube-dns, etc) which >>> seem to automatically re-spawn when deleted. Is there a way to limit the >>> CPU / Memory resources for these? >>> >> -- > You received this message because you are subscribed to the Google Groups > "Containers at Google" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/google-containers. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Containers at Google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-containers. For more options, visit https://groups.google.com/d/optout.
