Re: [kubernetes-users] is kubernetes aware of the performance difference between say a nehalem and a broadwell core?

No. Kubernetes is not aware of perf differences between CPU or RAM hardware. Can you describe why you are looking for such a solution? What's your specific use case? On Sep 20, 2017 4:04 PM, "z3ro" wrote: > is kubernetes aware of the performance difference between say

[kubernetes-users] is kubernetes aware of the performance difference between say a nehalem and a broadwell core?

is kubernetes aware of the performance difference between say a nehalem and a broadwell core? and ram performance? -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q" group. To unsubscribe from this group and stop receiving emails

[kubernetes-users] kubeadm init hangs

Hello, I know I have seen some discussion on this topic both in this group and on the Kubernetes github issues, but I haven't found a good solution, so I thought I would add my experience to the mix. Earlier this week, Oraclelinux added Kubernetes support through its yum repositories.

Re: [kubernetes-users] steps to migrate Docker image to use kubernetes

On Wed, Sep 20, 2017 at 5:25 AM, Shashank Dutt Jha wrote: > > $ kubectl apply -f kuber-agent.yml > The Deployment "agent-kuber" is invalid: > * spec.template.spec.volumes[0].hostPath: Forbidden: may not specify more > than 1 volume type You have more than one source listed

Re: [kubernetes-users] Re: using image from local directory

And if you are on different machines, you need to push that image somewhere so it can be pulled by kubelet On Wed, Sep 20, 2017 at 9:49 AM, Warren Strange wrote: > > > ImagePullBackOff means that Kubernetes can not find the image. > > You have: > image: agentc > > You

[kubernetes-users] Re: using image from local directory

ImagePullBackOff means that Kubernetes can not find the image. You have: image: agentc You need: image: library/agentc:latest This also assumes you have done a "docker build" direct to the docker daemon that your Kubernetes cluster is using. If you are using minikube, you must make sure

Re: [kubernetes-users] Resolv.conf override for a pod

There's no supported way to do that, in part because it would give up all of the Service names that kubernetes provides. I don't know what would happen if you tried to volumeMount a file over /etc/resolv.conf - might be worth a shot. On Wed, Sep 20, 2017 at 3:15 AM, Simone D'Andreta

Re: [kubernetes-users] Cluster command history

It seems like it. The documentation seems pretty straightforward: https://kubernetes.io/docs/tasks/debug-application-cluster/audit/ Thank you! Best, George -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q" group. To unsubscribe

[kubernetes-users] Re: Kubernetes on Bar Metal servers!

Thank you for your post. I too am trying different methods/stacks as well to pxe boot a 42u bare metal rack into a cluster. os running in ram of course. what was your experience with Rancher and core os together? Do you recommend Bootkube+matchbox over coreosmatchbox/ rancher? I like

[kubernetes-users] Whitelist an IP to access deployment with Kubernetes ingress Istio

Hello everyone! I'm trying to whitelist an IP to access a deployment inside my Kubernetes cluster. (Restrict all traffic but the whitlisted IP's) I looked for some documentation online about this, but I only found the ingress.kubernetes.io/whitelist-source-range for ingress to grant access to

Re: [kubernetes-users] steps to migrate Docker image to use kubernetes

$ kubectl apply -f kuber-agent.yml The Deployment "agent-kuber" is invalid: * spec.template.spec.volumes[0].hostPath: Forbidden: may not specify more than 1 volume type * spec.template.spec.volumes[0].persistentVolumeClaim: Forbidden: may not specify more than 1 volume type *

[kubernetes-users] Resolv.conf override for a pod

Hello, I wanted to know if there is a way to override DNS settings for pods (not per cluster). I tried to use HostAliases but it only creates an A record for that entry. I basically need a NS record cause I need to point to different Consul clusters and then Consul must be able to do service

Re: [kubernetes-users] steps to migrate Docker image to use kubernetes

I get this error now: $ kubectl apply -f kuber-agent.yml error: error validating "kuber-agent.yml": error validating data: found invalid field path for v1.Volume; if you choose to ignore these errors, turn validation off with --validate=false apiVersion: apps/v1beta1 kind: Deployment metadata:

Re: [kubernetes-users] steps to migrate Docker image to use kubernetes

Now I get following error: following your suggestion $ kubectl apply -f kuber-agent.yml error: error validating "kuber-agent.yml": error validating data: found invalid field volumes for v1beta1.DeploymentSpec; if you choose to ignore these errors, turn validation off with --validate=false

[kubernetes-users] using image from local directory

I have created an image using Docker command docker build -t library/app-agentk . Then I have config file piVersion: apps/v1beta1 kind: Deployment metadata: name: agent-deployment spec: replicas: 1 # tells deployment to run 2 pods matching the template template: # create pods using pod

Re: [kubernetes-users] steps to migrate Docker image to use kubernetes

currently I run the same image using docker-compose with following configuration. Which works. Same volume information needs to be passed to when I run uring kubernetes version: '2' services: app-agentc: image: app-agentc env_file: - a.env volumes: -