Once you’re able to connect to the API then I would say you can call the cluster operational. Keep in mind that the deployment process downloads ~400 MB of containers so the timing will vary there. Make sure you have a robust backoff loop for that check.
- Rob > On Jun 8, 2016, at 1:28 PM, Gary Denner <[email protected]> wrote: > > Thanks Kyle, is there any easy way to "verify" a kubernetes cluster is > operational after bringing it up and before pushing containers to it?? > > On Wednesday, June 8, 2016 at 9:21:23 PM UTC+1, Kyle Brown wrote: > Gary, > > You could create a Jenkins job that uses our kubernetes AWS deployment tool: > kube-aws > <https://github.com/coreos/coreos-kubernetes/tree/master/multi-node/aws>. > This tool uses CloudFormation to bring up a cluster using the latest release > of coreos-kubernetes. <https://github.com/coreos/coreos-kubernetes> You can > find more documentation on kube-aws here. > <https://coreos.com/kubernetes/docs/latest/kubernetes-on-aws.html> > > Cheers, > Kyle Brown > > > > On Wed, Jun 8, 2016 at 12:40 PM, Gary Denner <[email protected] > <javascript:>> wrote: > Folks > > What is the best way to do the following > > 1. Build a Jenkins job that goes off to AWS and provisions CoreOS machines > 2. Then push Kubernetes to these configs. > 3. The ability to be able to blow away these images and bring them back up > simply using the latests versions. > > I looked at CloudFormation files but can't see an easy way to do this without > having to manually login to AWS etc > > Thanks for any insights > >
