Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci/cd: add software to CI to run cluster api with a minikube bootstrap cluster #51

Closed
sflxn opened this issue Sep 18, 2018 · 2 comments
Closed

Comments

@sflxn
Copy link

sflxn commented Sep 18, 2018

To test clusterctl with a bootstrap cluster using minikube, we need some software installed on some machines in CI. Specifically,

  1. Vmware workstation
  2. minikube with the Vmware support built in (Add new VMware unified driver to supported list kubernetes/minikube#2606)
  3. the docker-machine driver for vmware (https://github.com/machine-drivers/docker-machine-driver-vmware/releases)

It doesn't matter if these components are installed on some static VMs or on the CI/CD kubernetes cluster nodes as long as we can run clusterctl on the machine that these components are installed on.

Note, this requirement is contingent on the minikube bootstrap workflow remaining in clusterctl, for which there are currently no discussions on removing.

@sflxn
Copy link
Author

sflxn commented Nov 27, 2018

We are lowering this in priority as using minikube with Fusion in CI was very problematic. It introduces another software stack that we would have to debug if bootstrapping failed.

@sflxn sflxn closed this as completed Feb 1, 2019
@sflxn
Copy link
Author

sflxn commented Feb 1, 2019

Adding this would make CI really unreliable. We'd be adding multiple software stacks that would end up making debugging failing builds very difficult.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant