I have an old issue open for this.
https://github.com/kubernetes/kubernetes/issues/36601
On Thursday, January 19, 2017 at 2:37:02 PM UTC-8, Mayank wrote:
>
> Hi All
> Is there a way to create a kubernetes job that runs on all nodes in the
> cluster and then finishes without creating one job per
>
> If sig-aws has a reason to exist, then so does sig-metal. People who use
> the cloud have (justifiably) no interest in mechanics that will be
> mandatory in bare metal - like choice of load balancers, networking across
> data centers, etc
>
With that being said, I don't think this should
Everyone interested in the bare metal sig should also join cluster
lifecycle. No questions IMO. But I think the sigs have different goals.
Cluster lifecycle from my experience (I've only joined a few calls) is more
abstracted towards best practices and maintaining a cluster. There are
occasiona
I'm surprised you only found 3 ways. I don't think there is a comparison
page but here is a really quick breakdown from my limited knowledge of each
tool. *disclaimer* I've only ever used kube-up
kubeadm: currently alpha tool to initiate clusters on any platform (AWS
included). Mostly trying to
Yes please! Only concern is this would spin off to start including SIGs for
each cloud environment. I think it would be very hard to justify why this
is needed over intricacies when running in AWS/GCE/Azure/etc. or even
on-prem with VMware/OpenStack
With that being said, we'd also need to make
