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
On 2017-10-31 1:58 pm, 'Tim Hockin' via Kubernetes user discussion and
Q wrote:
Another option would be to use HostNetwork, and just use a random
port, and self-register your replicas in whatever registry (assuming
you don't care about port numbers being random). Some game servers do
exactly
I am trying to taint nodes in a gke node pool similar to this:
gcloud beta container node-pools create pool-node --cluster cgs
--machine-type n1-standard-16 --node-labels 'capability=impute' --tags impute
--num-nodes 1 --preemptible --enable-autoscaling
[Bcc'ed to kubernetes-dev@, kubernetes-users@; followups to
kubernetes-sig-gcp@]
The kick off meeting for SIG-GCP is scheduled for 9am Pacific Time,
Thursday Nov 9.
The agenda and meeting details are here : bit.ly/k8s-sig-gcp. Our first
topic will be an update from the Cloud Provider working
Now taints are supported in GKE and you don't need to run kubectl taint
nodes. Please follow
https://cloud.google.com/container-engine/docs/node-taints for more
information.
Thanks
Ajit
On Monday, August 21, 2017 at 1:37:56 AM UTC-7, je...@blendle.com wrote:
>
> For now, we solved this by
Hi Randal,
Yes, --node-taints flag should add taint to your nodes and you don't need
to run kubectl taint nodes. Node taint is a beta feature and you need to
set a flag before running gcloud create [1]. Please run following before
creating a node-pool/cluster
export
Greetings programs! This is a reminder that the Kubernetes Office Hours
will be in about 2 weeks, on 15 November. We run two sessions, one for the
EU and one for the Americas, you can find all the time information here:
http://bit.ly/kubernetes-office-hours
Volunteers, feel free to sign up here
