-
Notifications
You must be signed in to change notification settings - Fork 39.3k
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
Refactor cluster/juju #22726
Refactor cluster/juju #22726
Conversation
Can one of the admins verify that this patch is reasonable to test in $JOB_NAME? (reply "ok to test", or if you trust the user, reply "add to whitelist") If this message is too spammy, please complain to ixdy. |
2 similar comments
Can one of the admins verify that this patch is reasonable to test in $JOB_NAME? (reply "ok to test", or if you trust the user, reply "add to whitelist") If this message is too spammy, please complain to ixdy. |
Can one of the admins verify that this patch is reasonable to test in $JOB_NAME? (reply "ok to test", or if you trust the user, reply "add to whitelist") If this message is too spammy, please complain to ixdy. |
Labelling this PR as size/XXL |
3bd5f21
to
50e055f
Compare
args: | ||
# command = "/kube2sky" | ||
{% if dns_domain -%}- -domain={{ dns_domain }} {% else %} - -domain=cluster.local {% endif %} | ||
- -kube_master_url=http://{{private_address}}:8080 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This could be your issue. I believe you need it to be {{ private_address }} and not {{private_address}}
f9f4bb6
to
52427af
Compare
Ok, I think i have this building cleanly now, and have updated the necessary Meta. Let me know if you'd like me to squash this before the review happens. |
@zmerlynn - any update on getting a review? the travis and cla bot seem fine. submit-queue still however states its pending failing tests? is that the mesos smoke test bot that i need to satisfy before I get a review? |
Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist") This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
This commit imports the latest development focus from the Charmer team working to deliver Kubernetes charms with Juju. Notable Changes: - The charm is now assembled from layers in $JUJU_ROOT/layers - Prior, the juju provider would compile and fat-pack the charms, this new approach delivers the entirety of Kubernetes via hyperkube. - Adds Kubedns as part of `cluster/kube-up.sh` and verification - Removes the hard-coded port 8080 for the Kubernetes Master - Includes TLS validation - Validates kubernetes config from leader charm - Targets Juju 2.0 commands
52427af
to
b8b54ac
Compare
@k8s-bot ok to test |
@chuckbutler: I'm sorry for the long delay, this went to the bottom due to size. Is there any other maintainer that can help review this as well? This is mammoth and I have little Juju context. |
GCE e2e build/test passed for commit b8b54ac. |
The author of this PR is not in the whitelist for merge, can one of the admins add the 'ok-to-merge' label? |
@zmerlynn - you bet, theres a couple If you're OK with canonical being the reviewers, @marcoceppi or @mbruzek is on our ticket. In terms of googlers that have looked at our code in the past: @eparis and @erictune both lent a hand in bringin us on board and looking over our initial PR's that landed in cluster. I apologize again for the size, it wasn't intended to be this large, but it is a big deletion of footprint and re-scoping of what needs to be here, vs supporting infra code that revs independently of our work here. If there's anything else I can do to help expedite the request, such as test run logs or an environment stood up with the charms to poke at and validate I'm happy to lend a hand. |
expose: true | ||
num_units: 2 | ||
etcd: | ||
charm: cs:~lazypower/trusty/etcd |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NIT: Would it be better to put etcd in ~containers?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah good point!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll bring this in on the next update w/ the docs. @zmerlynn - is that still going to be pointed here or have the docs migrated to their new home already?
LGTM |
I independently verified running ./kube-up.sh from the cluster directory. Everything came up OK. I will take a further look at the code.
|
I know this looks like an XXL pull request, but looking at the lines changed: +915 −2,513 that is a net loss of 1598 lines of code in the cluster/juju/ directory that makes the Juju specific files much smaller. The heart of this change is in the cluster/juju/util.sh and that also was reduced in size. I deployed this via kube-up.sh on amazon with KUBERNETES_REPOSITORY=juju and it worked for me. +1 on the code and the change from my end (for what it is worth). |
@zmerlynn I'll pick this up. |
|
||
- [Kubernetes github project](https://github.com/kubernetes/kubernetes) | ||
- [Kubernetes issue tracker](https://github.com/kubernetes/kubernetes/issues) | ||
- [Kubernetes Documenation](https://github.com/kubernetes/kubernetes/tree/master/docs) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We prefer that you link to http://kubernetes.io/docs/
two comments. |
…bled and handled completely differently
GCE e2e build/test passed for commit 326a51f. |
GCE e2e build/test passed for commit cc1fb15. |
LGTM. Thanks! |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit cc1fb15. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit cc1fb15. |
Automatic merge from submit-queue |
Apologies in advance for the XL PR
The Juju team has been hard at work refactoring the Kubernetes charms. A new charming pattern has emerged where charms are now assembled from layers to build a deployable artifact. Allowing our footprint in the Kubernetes upstream repository to remain light and only pertain to the concerns of Kubernetes itself.
A few things to note about this PR:
cluster/kube-up.sh
- this is not intended to stand up a long running kubernetes cluster, but instead to validate the charm deployment for devel purposes. (building and packing a custom hyperkube image is planned but unscheduled at the moment)hyperkube
Prereq work to address #9107