We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I deployed the registry cluster add-on which relies on hostPorts and couldn't connect to the hostPort.
The hostPort in the container spec should be available.
The port is not available.
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
Others have reported the issue, but the kube-flannel.yml was not updated
The text was updated successfully, but these errors were encountered:
Add portmap plugin to CNI conf
56b6e45
The portmap plugin is needed in order for hostPorts to work Closes flannel-io#887
014b2d5
The portmap plugin is needed for hostPorts to work Closes: flannel-io#887
No branches or pull requests
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)
Context
Others have reported the issue, but the kube-flannel.yml was not updated
Your Environment
The text was updated successfully, but these errors were encountered: