[kubernetes-users] Docker platform adding Kubernetes

Hi, I've seen this announced https://www.docker.com/kubernetes Interested to know what this means in terms of roadmap. Does this just mean Kubernetes will work with the latest Docker? Or are there other integrations with Swarm, Docker-compose, Stack deploy? -- You received this message

[kubernetes-users] Let default service account view configmaps?

GET at: https://kubernetes.default.svc/api/v1/namespaces/default/configmaps/my-config. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. configmaps "my-config" is forbidden: User "system:serviceaccount:default:default" cannot get

[kubernetes-users] nginx-ingress-controller Deployment on vmware & baremetal

Hi, I have the following nginx-ingress-controller Deployment (replicas: 2) running on kubeadmin cluster: https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.9.0-beta.15/examples/deployment/nginx/kubeadm/nginx-ingress-controller.yaml But how can do I expose this outside the

[kubernetes-users] unknown host between nodes in a Stateful Set

Hi, I'm running a Stateful Set with Headless Service (db-0, db-1, db2) similar to the Cassandra example here However, when the pods start up they cannot ping each: > kubectl exec -it db-0 -- ping db-1 ping: unknown host

[kubernetes-users] minikube - Error from server (BadRequest): container "hello-minikube" in pod "hello-minikube-180744149-z87pb" is waiting to start: ContainerCreating

Hi, Trying to setup minikube on Windows 10 with Hyper-V. *kubectl run hello-minikube --image=gcr.io/google_containers/echoserver:1.4 --port=8080* But hello-minikube pod is stuck in ContainerCreating *kubectl get pod* NAME READY STATUS RESTARTS

[kubernetes-users] minikube (with hyperv) won't start on Windows 10

Hi, In Hyper-V Manager > Virtual Switch Manager I created a Virtual Switch called minikube and rebooted my machine I then ran minikube start: minikube

[kubernetes-users] Re: minikube - Error from server (BadRequest): container "hello-minikube" in pod "hello-minikube-180744149-z87pb" is waiting to start: ContainerCreating

> > *Also there doesn't seem to be a way to delete the pod in this state* > kubectl delete pods *hello-minikube-180744149-z87pb* pod "*hello-minikube-180744149-z87pb*" deleted But it never gets removed -- You received this message because you are subscribed to the Google Groups "Kubernetes

Re: [kubernetes-users] minikube - Error from server (BadRequest): container "hello-minikube" in pod "hello-minikube-180744149-z87pb" is waiting to start: ContainerCreating

The problem was my *imagePullSecret* I used: *--docker-server=nexus.mycompany.com:5* But I needed: *--docker-server=https://nexus.mycompany.com:5/v2/* kubectl create secret docker-registry regsecret --docker-server=https:// nexus.mycompany.com:5/v2/ --docker-username=foo

[kubernetes-users] Kubernetes Volume storage questions

Hi, My Kubernetes cluster will be running on VmWare and in future on Amazon's AKS also. What should I be looking for regards Volume drivers? - Cepth, GlusterFS seem to be popular options. - RexRay seems to be popular in Docker with a FlexRay K8s option Or should I be looking at

Re: [kubernetes-users] Kubernetes Volume storage questions

Thanks, what are the benefits (if any) to choosing GlusterFS/Ceph over VsphereVolume/AWSElasticBlockStore? For a database like Postgres. -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q" group. To unsubscribe from this group and