@justinsb @kubernetes/sig-cluster-lifecycle-feature-requests @kubernetes/sig-aws-misc any updates for 1.8? Is this feature still on track for the release?

@justinsb Any update on it? I am ready to lend a helping hand :)

Hi,

First of all I think that having automatic support for bare metal provisioning is an awesome goal.
I have some questions that might spark a discussion around what features are in scope and what not.

Are you targeting a full kubernetes cluster install on bare-metal?
Could kops support a use case of adding a bare-metal worker node to an existing kubernetes AWS cluster?
I believe that this might be good way to expand an existing cluster outside AWS as servers in classic providers as Hetzner can be cheaper. I don't know if the costs will be mitigated by the data transfer costs.

If this feature is out of scope for automatic provisioning by kops, maybe the procedure can be described so it can be done manually.

I have spent the last two to three weeks trying to get elasticsearch to run on a kubernetes cluster and have lots of R&D to offer with regards to LXD, conjure-up vs. kubeadm, namespace management, and the mish-mosh of intertwined commands between kubectl, docker and juju to get things almost running (everything says it's healthy, but can't actually get a response from ES). Let me know if you're interested.

@mtaylor769 : If your message was for me, I managed to deploy single cluster node with kubeadm and it worked very well. Thanks.

The cluster works ok but I have some issues with networking. I'm trying to secure the cluster by making services listen on localhost by default. Seems like I managed. Still I do have some unknowns in that area and more documentation would be helpful.

Regarding bare-metal, I believe kubeadm is muck more helpful at this moment.

@ieugen It was a general question, but your answer has shed some light on some of what I've been experiencing. I was trying kubeadm at first but wasn't able to get everything to play nice, so I will try that avenue again. Thanks.

@ieugen @mtaylor769 Just FYI, this repo is meant to be low-volume, and email notifications are expected to be feature status updates, not general discussion or support. That discussion should move to other forums, but no worries anyway.

Thanks for your interest in kubeadm and kops!

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@ieugen so I have got the same thing , I just believe kubeadm is appreaing to be the best solution for BareMetal considering it's single node control plane method and scalability by just adding a tokenized string , I tried to use kubespray as well but it seems there is a drift I felt when tried to apply for new nodes.

Not sure what's the opinion but I would love to see views or experience for the same.