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

Adding new Kubernertes units when running with CNI not working #102

Open
simonklb opened this issue Sep 4, 2017 · 2 comments
Open

Adding new Kubernertes units when running with CNI not working #102

simonklb opened this issue Sep 4, 2017 · 2 comments
Assignees

Comments

@simonklb
Copy link
Contributor

simonklb commented Sep 4, 2017

Something needs to be done to enable CNI for new units added after initial deployment as well. It's problematic because you won't have cluster-wide CNI support which obviously will lead to inconsistencies but even worse, new units cannot even join the cluster.

Workaround I'm using atm is to manually attach the IAM role to the instance and set the cloud-provider snap option.

@adam-stokes
Copy link

We're working with the Juju team to try and get this functionality included.

@adam-stokes
Copy link

Opened a bug with Juju here: https://bugs.launchpad.net/juju/+bug/1715200

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

No branches or pull requests

3 participants