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.

Sign up for GitHub

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

Jump to bottom

Juju charms for k8s should use the latest LTS #30373

Closed
lazypower opened this issue Aug 10, 2016 · 1 comment · Fixed by #30374
Closed

Juju charms for k8s should use the latest LTS #30373

lazypower opened this issue Aug 10, 2016 · 1 comment · Fixed by #30374
Labels
area/controller-manager

Comments

@lazypower
Copy link
Contributor

Currently, the layers in the cluster/juju path only seem to support Trusty. This is the last revision of ubuntu to use upstart and doesn't have many of the recent bumps in packaging and SystemD init.

The juju charms should target systemd, as the layers already have support for deploying into this series.
@mbruzek mbruzek mentioned this issue Aug 10, 2016
Merged
@lazypower
Copy link
Contributor Author

Closed with #30374

@mbruzek mbruzek mentioned this issue Aug 30, 2016
Merged
k8s-github-robot pushed a commit that referenced this issue Oct 12, 2016
Merge pull request #30374 from mbruzek/juju-series-update
049a023 
Automatic merge from submit-queue

Update the series and the README to reflect the change.

This PR updates the juju charm code to support the latest series (xenial 16.04). We changed the README to reflect this change and how that changes the juju commands.

fixes #30373

`release-note-none`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/controller-manager
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update the series and the README to reflect the change. mbruzek/kubernetes
2 participants
@lazypower @k8s-github-robot