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

issue with vagrant and ubuntu 16.04 (xenia64) #29

Open
upolymorph opened this issue May 29, 2018 · 0 comments
Open

issue with vagrant and ubuntu 16.04 (xenia64) #29

upolymorph opened this issue May 29, 2018 · 0 comments

Comments

@upolymorph
Copy link

I am using the playbook to deploy three nodes using vagrant and ubuntu/xenia64 (I have the same issue using bento/ubuntu16.04).
the playbook stop while trying to install helm has shown in the gist https://gist.github.com/upolymorph/abbf9a1465ae9987e998e19adc4caf84

accessing to the master nodes i have the folowing output:

kubectl -n kube-system get nodes
NAME STATUS ROLES AGE VERSION
k8sceph-01 Ready master 53m v1.9.8

kubectl -n kube-system get pods
NAME READY STATUS RESTARTS AGE
etcd-k8sceph-01 1/1 Running 0 1h
kube-apiserver-k8sceph-01 1/1 Running 0 1h
kube-controller-manager-k8sceph-01 1/1 Running 0 1h
kube-dns-6f4fd4bdf-xlxmz 3/3 Running 0 1h
kube-flannel-ds-p5qw6 1/1 Running 0 54m
kube-proxy-gtl7q 1/1 Running 0 1h
kube-scheduler-k8sceph-01 1/1 Running 0 1h
tiller-deploy-7ccf99cd64-tm9cp 0/1 Pending 0 54m

kubectl -n kube-system describe pod tiller-deploy-7ccf99cd64-tm9cp
Name: tiller-deploy-7ccf99cd64-tm9cp
Namespace: kube-system
Node:
Labels: app=helm
name=tiller
pod-template-hash=3779557820
Annotations:
Status: Pending
IP:
Controlled By: ReplicaSet/tiller-deploy-7ccf99cd64
Containers:
tiller:
Image: gcr.io/kubernetes-helm/tiller:v2.9.1
Ports: 44134/TCP, 44135/TCP
Liveness: http-get http://:44135/liveness delay=1s timeout=1s period=10s #success=1 #failure=3
Readiness: http-get http://:44135/readiness delay=1s timeout=1s period=10s #success=1 #failure=3
Environment:
TILLER_NAMESPACE: kube-system
TILLER_HISTORY_MAX: 0
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-947p2 (ro)
Conditions:
Type Status
PodScheduled False
Volumes:
default-token-947p2:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-947p2
Optional: false
QoS Class: BestEffort
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message


Warning FailedScheduling 20s (x191 over 55m) default-scheduler 0/1 nodes are available: 1 PodToleratesNodeTaints.

Can you please provide me with some guidances?
Thanks in advance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant