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

Sync <1.6 yaml with the 1.6 yaml #48

Closed
kfox1111 opened this issue Mar 27, 2017 · 5 comments
Closed

Sync <1.6 yaml with the 1.6 yaml #48

kfox1111 opened this issue Mar 27, 2017 · 5 comments

Comments

@kfox1111
Copy link

The patch "Sync <1.6 yaml with the 1.6 yaml " broke the kolla-kubernetes gate. Reverting it fixed the issue. I think there may be an incompatibility with the canal containers and k8s 1.5?

@ozdanborne
Copy link
Member

@kfox1111 The images it was updated to use should be compatible with k8s 1.5. What behavior / logs are you seeing?

@tomdee
Copy link
Contributor

tomdee commented Mar 28, 2017

@kfox1111 Could you describe what's actually going wrong. There are a lot of logs at those links but I have no idea what I'm looking for.

@ozdanborne
Copy link
Member

A quick look and I noticed kubedns pod wasn't coming up, which is a symptom of this issue: https://github.com/projectcalico/calicoctl/issues/1575

I've opened #49 to resolve it

@ozdanborne
Copy link
Member

@kfox1111 I've just merged 49, which adds the following environment variable to calico/node:

# Set Felix endpoint to host default action to ACCEPT.
name: FELIX_DEFAULTENDPOINTTOHOSTACTION
value: "ACCEPT"

This should allow connections from the container to the host, e.g. Kube-DNS on Master speaking to the Api-server. I believe this is the issue you were hitting.

Please retry with the latest manifests and reopen if you are still having some issues.

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

3 participants