On Mon, Mar 27, 2017 at 05:08:12PM -0700, Jeff Haynie wrote:
> OK i think i understand... So I would need to place the generated
> Deployment ID in the POD template (somehow?) at deployment time? Then I
This isn't so weird, nor difficult I think.
You may want to pick the number of replicas, for
OK i think i understand... So I would need to place the generated
Deployment ID in the POD template (somehow?) at deployment time? Then I
could read the metadata and use the normal Kube API to query for all the
objects with same id?
On Mon, Mar 27, 2017 at 5:02 PM, 'Tim Hockin' via Kubernetes
I have a _very_ n00b question as I'm just getting into Kubernetes (from docker
swarm land).
As part of our deployment we have a script that will generate a unique ID
(Deployment ID) when deploying a new swarm deployment and as part of this
deployment all services and containers in the swarm
Hi, I've been trying to enabled token auth for HTTP rest api access from a
remote client.
I installed my CoreOS/K8S cluster controller using this script:
https://github.com/coreos/coreos-kubernetes/blob/master/multi-node/generic/controller-install.sh
My cluster works fine. This is a TLS
I'm running Kubernetes v1.4.0+776c994 on an EC2 instance in AWS GovCloud.
I can list EC2 volumes with 'aws ec2 describe-volumes', but when I try to
create a persistent volume, 'kubectl create -f aws-pv.yaml', I get this error:
If the service is not reachable by the cluster IP, your cluster
probably isn't really functional. For example, DNS works by cluster
IP.
On Mon, Mar 27, 2017 at 3:45 AM, govindaraj wrote:
> I am trying to set up locust master / agent. All the agents need to know
>
Can it just use a DNS name? This is more stable and would likely provide
what you need. If so, I'd create a service endpoint for the master, and
that will take care of what you need.
On Mon, Mar 27, 2017 at 12:45 PM, govindaraj
wrote:
> I am trying to set up locust
I am trying to set up locust master / agent. All the agents need to know
locust master IP. When I use the name locust-master, it gets th cluster IP
of master. The cluster ip seems not rout able and the agents are not able
to connect to locust master.
On Mar 27, 2017 1:38 AM, "'David Aronchick'
On Monday, March 27, 2017 at 4:56:25 PM UTC+8, ede...@unity3d.com wrote:
> On Monday, March 27, 2017 at 1:14:31 PM UTC+8, Tim Hockin wrote:
> > This should be part of docs - if you used kubeadm, please file a bug
> > against it.
> >
> > On Sun, Mar 26, 2017 at 10:03 PM,
On Monday, March 27, 2017 at 1:14:31 PM UTC+8, Tim Hockin wrote:
> This should be part of docs - if you used kubeadm, please file a bug against
> it.
>
> On Sun, Mar 26, 2017 at 10:03 PM, wrote:
> > On Sunday, March 26, 2017 at 7:09:26 PM UTC+8, ede...@unity3d.com wrote:
>
10 matches
Mail list logo