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

Make kube2sky and skydns docker images cross-platform #19376

Merged
merged 1 commit into from
Apr 11, 2016

Conversation

luxas
Copy link
Member

@luxas luxas commented Jan 7, 2016

ARM tracking issue: #17981
Continues on: #19216

Make it possible to create kube2sky and skydns docker images for ARM and other architectures too
Build in a container, so golang isn't a dependency
I've preserved the original default behaviour:

  • skydns: It just compiles with go on host
  • kube2sky: Build an image

@brendandburns @dchen1107 @ArtfulCoder @thockin @fgrzadkowski

@k8s-bot
Copy link

k8s-bot commented Jan 7, 2016

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")

If this message is too spammy, please complain to ixdy.

@k8s-bot
Copy link

k8s-bot commented Jan 7, 2016

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")

If this message is too spammy, please complain to ixdy.

@k8s-github-robot
Copy link

Labelling this PR as size/L

@k8s-github-robot k8s-github-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 7, 2016
@luxas
Copy link
Member Author

luxas commented Jan 11, 2016

Friendly ping @thockin @brendandburns. Trigger the tests at least :)

docker build -t $(PREFIX)/kube2sky:$(TAG) .
ifeq ($(ARCH),amd64)
# Backward compatability. TODO: deprecate this image tag
docker tag -f ${REGISTRY}/kube2sky-${ARCH}:${TAG} ${REGISTRY}/kube2sky:${TAG}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems that make supports ${} but $() is more common - minor point, but I even had to go look to make sure ${} was right.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, ${} works, at least locally :)
One example of ${} usage is the hyperkube Makefile now.
It heavily uses ${} and I think we should choose one of them

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I much prefer $() for make variables.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, I'll update this one if you prefer

@thockin
Copy link
Member

thockin commented Jan 12, 2016

I think this is OK, but it doesn't include the usage of the new -ARCH container. Is that coming later?

@luxas
Copy link
Member Author

luxas commented Jan 12, 2016

Yes, that for the next PR.
It's better to do that when you guys have pushed the images, when all the -ARCH containers is pullable
It it OK to merge then?

@luxas luxas force-pushed the dns_cross_platform branch from a6de1ed to bf49f96 Compare January 17, 2016 14:51
@luxas
Copy link
Member Author

luxas commented Jan 17, 2016

@thockin @brendandburns Replaced ${} with $().
Is it OK to merge?

@luxas
Copy link
Member Author

luxas commented Jan 19, 2016

@thockin @brendandburns PTAL

@luxas
Copy link
Member Author

luxas commented Jan 25, 2016

Ping @thockin

@k8s-bot
Copy link

k8s-bot commented Jan 28, 2016

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")

If this message is too spammy, please complain to ixdy.

2 similar comments
@k8s-bot
Copy link

k8s-bot commented Jan 28, 2016

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")

If this message is too spammy, please complain to ixdy.

@k8s-bot
Copy link

k8s-bot commented Feb 3, 2016

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")

If this message is too spammy, please complain to ixdy.

@k8s-github-robot
Copy link

PR needs rebase

@k8s-github-robot k8s-github-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 4, 2016
@k8s-bot
Copy link

k8s-bot commented Feb 4, 2016

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")

If this message is too spammy, please complain to ixdy.

@luxas luxas force-pushed the dns_cross_platform branch from bf49f96 to 194fdc6 Compare February 7, 2016 19:56
@luxas
Copy link
Member Author

luxas commented Feb 7, 2016

@thockin I really understand if you have much to do, but could you a) LGTM or b) reassign this

Then, in another PR, we should cut new kube2sky and skydns releases, and update the .yaml files to the new -ARCH name.

@k8s-github-robot k8s-github-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 7, 2016
@k8s-bot
Copy link

k8s-bot commented Feb 7, 2016

GCE e2e test build/test passed for commit 194fdc672e6680dfc3b3f123d17602fb33eff85d.

@k8s-github-robot
Copy link

The author of this PR is not in the whitelist for merge, can one of the admins add the 'ok-to-merge' label?

@luxas
Copy link
Member Author

luxas commented Feb 21, 2016

@fgrzadkowski Can you kindly take a look at this, and maybe push the images?
It should be OK, as @thockin said above.
I really understand if you have much to do now when you're preparing for v1.2...

@k8s-bot
Copy link

k8s-bot commented Feb 23, 2016

GCE e2e build/test failed for commit 194fdc672e6680dfc3b3f123d17602fb33eff85d.

@k8s-github-robot
Copy link

@luxas PR needs rebase

@david-mcmahon david-mcmahon added lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-merge and removed needs-ok-to-merge labels Apr 7, 2016
@k8s-github-robot
Copy link

@k8s-bot test this

Tests are more than 48 hours old. Re-running tests.

@k8s-bot
Copy link

k8s-bot commented Apr 9, 2016

GCE e2e build/test passed for commit b3015e1a4e4113d0b0d07031ab64abf825db4932.

@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Apr 10, 2016

GCE e2e build/test passed for commit b3015e1a4e4113d0b0d07031ab64abf825db4932.

@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Apr 10, 2016

GCE e2e build/test passed for commit b3015e1a4e4113d0b0d07031ab64abf825db4932.

@@ -1,3 +1,9 @@
## Version 1.15 (Apr 7 2016 Lucas Käldström <lucas.kaldstrom@hotmail.co.uk>)
- No code changes since 1.14
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what version was 1.14 built with? probably want to include that this is using go 1.6

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know which version 1.14 was built with (as it was using go on host), but adding a note about go1.6

@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Apr 11, 2016

GCE e2e build/test passed for commit b3015e1a4e4113d0b0d07031ab64abf825db4932.

@david-mcmahon david-mcmahon removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 11, 2016
@luxas luxas force-pushed the dns_cross_platform branch from b3015e1 to 1c8140c Compare April 11, 2016 04:32
@luxas
Copy link
Member Author

luxas commented Apr 11, 2016

@david-mcmahon Updated. PTAL

@k8s-bot
Copy link

k8s-bot commented Apr 11, 2016

GCE e2e build/test passed for commit 1c8140c.

@david-mcmahon david-mcmahon added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 11, 2016
@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Apr 11, 2016

GCE e2e build/test passed for commit 1c8140c.

@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Apr 11, 2016

GCE e2e build/test passed for commit 1c8140c.

@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Apr 11, 2016

GCE e2e build/test passed for commit 1c8140c.

@k8s-github-robot
Copy link

Automatic merge from submit-queue

@k8s-github-robot k8s-github-robot merged commit 78dc9c7 into kubernetes:master Apr 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants