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

hostPort not available when using kube-flannel.yml #887

Closed
osoriano opened this issue Nov 25, 2017 · 0 comments
Closed

hostPort not available when using kube-flannel.yml #887

osoriano opened this issue Nov 25, 2017 · 0 comments

Comments

@osoriano
Copy link
Contributor

osoriano commented Nov 25, 2017

I deployed the registry cluster add-on which relies on hostPorts and couldn't connect to the hostPort.

Expected Behavior

The hostPort in the container spec should be available.

Current Behavior

The port is not available.

Possible Solution

Enable the portmap plugin in the CNI conf. This is how bootkube solved it: kubernetes-retired/bootkube#697

Also, the flannel-cni repo was updated to include the portmap plugin in the CNI config:
coreos/flannel-cni#5

The CNI portmap capability was added in k8s 1.7

Steps to Reproduce (for bugs)

  1. Deploy flannel using kube-flannel.yaml
  2. Create a pod that uses a hostPort

Context

Others have reported the issue, but the kube-flannel.yml was not updated

Your Environment

  • Flannel version: v0.9.1-amd64
  • Backend used (e.g. vxlan or udp): vxlan
  • Etcd version: v3.2.9
  • Kubernetes version (if used): 1.8.3
  • Operating System and version: CentOS7
osoriano added a commit to osoriano/flannel that referenced this issue Nov 25, 2017
The portmap plugin is needed in order for hostPorts to work

Closes flannel-io#887
osoriano added a commit to osoriano/flannel that referenced this issue Nov 25, 2017
The portmap plugin is needed for hostPorts to work

Closes: flannel-io#887
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