Skip to content
This repository has been archived by the owner on Apr 22, 2020. It is now read-only.

Port kubernetes-anywhere to provision on Packet #368

Closed
vielmetti opened this issue Apr 1, 2017 · 11 comments
Closed

Port kubernetes-anywhere to provision on Packet #368

vielmetti opened this issue Apr 1, 2017 · 11 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@vielmetti
Copy link

With encouragement from @luxas , this item will track the project to get Kubernetes Anywhere to provision and run services on Packet.

For reference

@luxas
Copy link
Contributor

luxas commented Apr 1, 2017

This will allow us to set up a CI test for kubeadm on arm64 by adding a similar job as https://k8s-testgrid.appspot.com/misc#kubeadm-gce but on Packet.

@packethost and @jacobsmith928 are very kind to provide infra for this 👍

@vielmetti
Copy link
Author

The docs mention

"There will be an implementation of GCE/AWS/Azure provisioning that utilizes Terraform."

Does such a thing exist now?

@vielmetti
Copy link
Author

Work in progress, edit the README file.

https://github.com/vielmetti/kubernetes-anywhere/tree/master/phase1/packet

@luxas
Copy link
Contributor

luxas commented Apr 5, 2017

cc @mikedanese @pipejakob @roberthbailey

They should be able to (and will) help you @vielmetti
I'm not an expert in these GCE scripts in particular

@vielmetti
Copy link
Author

Thanks @luxas !

@mikedanese @pipejakob @roberthbailey - if there's a walk-through of the provisioning process, and some guidelines for what files to change first for a new provider, I'm interested in getting that overview. Packet has an API, but I don't quite understand how this process works end to end, and where the data is pulled from at each stage.

@pipejakob
Copy link
Contributor

@vielmetti and I chatted on Slack, and I gave him an overview and pointers about how the current GCE + kubeadm works. It sounds like he has enough to get started now.

@fejta-bot
Copy link

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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 23, 2017
@roberthbailey
Copy link
Contributor

@vielmetti - is this something you have worked on? As we discussed during a recent cluster lifecycle meeting we hope to deprecate kubernetes-anywhere and move it to the kubernetes graveyard once we are able to port e2e tests for kubeadm over to run on top of the cluster api. And I know you've been looking at making a packet machine controller for the cluster api, which hopefully supersedes this work.

@luxas
Copy link
Contributor

luxas commented Dec 23, 2017

IIUC, no more serious work was ever conducted in this area, but the possibility to do this was investigated.
Good news on the Packet Machine controller though!
I'll close this as we'll move from kube-anywhere anyway

@luxas luxas closed this as completed Dec 23, 2017
@vielmetti
Copy link
Author

Thanks @roberthbailey @luxas we will be pursuing the Packet machine controller for the cluster API.

@vielmetti
Copy link
Author

@hh this is the issue I originally raised re kubernetes-anywhere.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

6 participants