-
Notifications
You must be signed in to change notification settings - Fork 129
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
001cb2b
commit 329d39d
Showing
3 changed files
with
7 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
329d39d
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.
@kelseyhightower Why not using gcr.io/google_containers/hyperkube-amd64:1.5.2 ? It's surprising because GCE provide me kubernetes 1.5.2. (I'll search myself on why we need hyperkube to build new kubernetes cluster.).
I tested api-server using hyperkube {1.4.0,1.5.2} and associate pods won't launch with crashloop. Maybe we should use etcdv2 as your friend suggest ? kubernetes/enhancements#44 (comment)
As soon as possible I'll debug get collect debug info from etcd logs.
kubefed seems promising too. I've so much stuff to try :-)