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

AWS + CoreOS + k8s 1.0.1 Documentation #11975

Closed
mcadam opened this issue Jul 29, 2015 · 12 comments
Closed

AWS + CoreOS + k8s 1.0.1 Documentation #11975

mcadam opened this issue Jul 29, 2015 · 12 comments
Labels
area/os/coreos kind/documentation Categorizes issue or PR as related to documentation. kind/support Categorizes issue or PR as a support question. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.

Comments

@mcadam
Copy link

mcadam commented Jul 29, 2015

Hello,

Is there more documentation on how to run a Kubernetes cluster using CoreOS on AWS ??

I tried the script for AWS specifying KUBE_OS_DISTRIBUTION=coreos, it started a master on ubuntu, and then tried to launch my minions but they all crashed.

I first had to modify the cluster/aws/coreos/util.sh script and delete those lines to make the script go this far:

  i=$1
  # TODO(bakins): Is this actually used?
  MINION_PRIVATE_IP=$INTERNAL_IP_BASE.1${i}

  MINION_IP=$(yaml-quote ${MINION_PRIVATE_IP})

That crashed because you dont use a loop anymore to create the minions.

Do you have a solution to use the script to start a cluster automatically, like create credentials and give me access to the cluster directly. I dont want to use the other guide in the multi-node coreos page, because it is basically useless as is. What do i do once the masters and minions are running ? SSH to get the credentials ?

I would love to be able to use the autoscaling group approach from the other script :)

I am on kubernetes version 1.0.1.
@mikedanese
Copy link
Member

@kelseyhightower

@mikedanese mikedanese added kind/support Categorizes issue or PR as a support question. area/os/coreos labels Jul 31, 2015
@joshm1
Copy link

joshm1 commented Aug 3, 2015

I ran into the same issue. It's been a bit of a blocker for me in getting kubernetes up and running on AWS with coreos. Even after I modified those lines you referenced, I had issues with kube-ui not working and service-dns resolution only working on one of my 2 minions (not sure if either of those are related though).

@mcadam
Copy link
Author

mcadam commented Aug 5, 2015

I ha ve at the same stage as you @joshm1, when trying to access the UI I get this error:

Error: 'dial tcp 172.17.0.2:8080: no route to host'
Trying to reach: 'http://172.17.0.2:8080/'

It seems the network stack is missing something ?

@mikedanese
Copy link
Member

You should be accessing it through the apiserver proxy. Run:

kubectl proxy

Then go to http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/kube-ui

https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/user-guide/connecting-to-applications-proxy.md

@mcadam
Copy link
Author

mcadam commented Aug 7, 2015

I tried to access it using address like https://xx.xx.xx.xx/api/v1/proxy/namespaces/kube-system/services/kube-ui on the IP of the master, which used to work when not using coreos as kube distribution.

Also I cant ping from one container to another.

@joshm1 joshm1 mentioned this issue Aug 9, 2015
Closed
@mbforbes mbforbes added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. area/platform/aws sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. kind/documentation Categorizes issue or PR as related to documentation. labels Aug 16, 2015
@pires
Copy link
Contributor

pires commented Aug 25, 2015

Have you guys tried https://github.com/kubernetes/kubernetes/blob/master/docs/getting-started-guides/coreos/coreos_multinode_cluster.md?

pires added a commit to pires/kubernetes that referenced this issue Aug 25, 2015
@pires
Removed deprecated and unmaintained AWS + CoreOS docs in favor of cor…
8549c0b 
…eos/coreos_multinode_cluster.md. Refs kubernetes#11975

Removed deprecated and unmaintained fork of pires/kubernetes-vagrant-coreos-cluster linked in the docs.
Removed deprecated and unmaintained VMware + CoreOS section of coreos/coreos_multinode_cluster.md. Refs kubernetes#13143
Refs kubernetes#9178
@pires pires mentioned this issue Aug 25, 2015
Merged
@mcadam
Copy link
Author

mcadam commented Aug 26, 2015

yes I tried I am using that currently but it is not a hand key version, like authentication you need a ssh tunnel, you dont have all the addons, the UI doesnt work.

@ngbinh
Copy link

ngbinh commented Aug 26, 2015

I had the same problem with @mcadam on 1.0.3.

xsamurai added a commit to xsamurai/kubernetes that referenced this issue Aug 26, 2015
@xsamurai
Changed SSH_USER to core instead ubuntu, also applied fixes from kube…
5f5d97b 
…rnetes#11975
@pires
Copy link
Contributor

pires commented Aug 26, 2015

@mcadam there is no UI nor secure API access, indeed. But it's better than not having a cluster, am I right? Joke aside, it would be great if the alternative CoreOS documentation would include this. I will be adding it to #9178

@mikedanese mikedanese removed the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Aug 26, 2015
@mikedanese
Copy link
Member

I suggest checking out https://github.com/kubernetes/kubernetes/blob/master/docs/user-guide/debugging-services.md

@bgrant0607-nocc bgrant0607-nocc added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Sep 4, 2015
brendandburns added a commit that referenced this issue Sep 30, 2015
@brendandburns
Merge pull request #13185 from xsamurai/master
5545630 
Changed SSH_USER to core instead ubuntu, also applied fixes from #11975
ananth-at-camphor-networks pushed a commit to Juniper/kubernetes that referenced this issue Oct 3, 2015
@xsamurai @ananth-at-camphor-networks
Changed SSH_USER to core instead ubuntu, also applied fixes from kube…
e7cdf9c 
…rnetes#11975
mkulke pushed a commit to mkulke/kubernetes that referenced this issue Oct 7, 2015
@xsamurai
Changed SSH_USER to core instead ubuntu, also applied fixes from kube…
2e4eaf3 
…rnetes#11975
@bcwaldon
Copy link

CoreOS is now maintaining official "Kubernetes on CoreOS" documentation. See the AWS guide here: https://coreos.com/kubernetes/docs/latest/kubernetes-on-aws.html

RichieEscarez pushed a commit to RichieEscarez/kubernetes that referenced this issue Dec 4, 2015
@xsamurai @RichieEscarez
Changed SSH_USER to core instead ubuntu, also applied fixes from kube…
7abca24 
…rnetes#11975
@rastut rastut mentioned this issue Dec 15, 2015
Merged
@aronchick
Copy link
Contributor

I would suspect this is hideously out of date. Please reopen if it's still an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/os/coreos kind/documentation Categorizes issue or PR as related to documentation. kind/support Categorizes issue or PR as a support question. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@aronchick @joshm1 @ngbinh @bcwaldon @mbforbes @pires @mikedanese @mcadam @bgrant0607 @bgrant0607-nocc