There is a note at the top of the page containing a link with instructions for
enabling the v1beta1 API surface:
Note: This feature uses gcloud beta commands. To use gcloud beta commands, you
must configure gcloud to use the v1beta1 API
On Thursday, November 2, 2017 at 1:56:28 PM UTC-7, randal.
Hi All,
I am considering using Kubernetes for an application that would require
worker pods to spawn additional (custom) docker containers that have
runtime parameters set by the worker. Ideally, these additional containers
would be added to the existing container's pod. At the very least, t
I have several Kubernetes cluster on GKE, and recently created a cluster on
AWS. When working against a GKE cluster, I run this command:
gcloud container clusters get-credentials my-cluser --zone us-central1-a --my
project
I'd like to know how I should be authenticating with a kubernetes cluste
Cool. Take into account that daemon set it is created to guarantee having
exactly one pod per node. For example, if you had more nodes, more pods for
a daemonset will be added. And the same if some crash or you reduce.
If that fits better what you want (sorry I didn't understood before), then
don'
I thought so, but the error message is not very clear so I was guessing
that perhaps the parameters' names have changed between 1.3 and 1.5 but I
couldn't find any proof of that in the docs.
The reason why I was going to upgrade my client is that with v 1.3. I hit a
configmap limit, Too long: mu
Hi Simone,
Ah yes it's probably a client/server version issue; quoting the versioning
design docs – "a client should be skewed no more than one minor version
from the master, but may lead the master by up to one minor version. For
example, a v1.3 master should work with v1.1, v1.2, and v1.3 nodes,
Hi Peter,
the user is present in my local kubeconfig file, I use it also to connect
to other clusters.
I am pretty sure the user is properly set in the API server, as it is
working fine with older versions of kubectl client.
Also note that the application is not using any kubeconfig file, but
re
Hello Simone,
the --user flag refers to the name of the kubeconfig user you want to use,
i.e the user needs to be set in your kubeconfig file.
Take a look at your local kubeconfig file (by default it should be here
~/.kube/config) and see if you can find the user `user` or run this command
to lis
Hello,
I have a weird issue happening with Kubectl client version 1.5 and above. I
have a docker app which runs a script that execute the following line:
kubectl --server=https://internal-elb-aws...(hidden..)
--certificate-authority=ca.pem --user=user --token=hidden get namespaces
and the outpu
As I said before, using multiple times the command "kubectl apply -f
my-deployment.yaml" (changing from time to time the image version inside the
yaml) I noticed that Kubernetes never deploys 2 pod in a same node.
I tested this behavior many times so yes it's working as I need :)
If I had proble
10 matches
Mail list logo
