Skip to content

Commit

Permalink
Don't put flanneld binary in /opt/bin
Browse files Browse the repository at this point in the history
As several people already pointed out on pull request flannel-io#1563, the
instructions added in there are not necessary. In fact, blindly following
these instructions actually caused some trouble for me since I ran into
issue flannel-io#1418 and started debugging that problem before realizing that I
don't actually need the binary in `/opt/bin`.

The pull request also does not provide any reasoning for why this could
be necessary. Given that, and given that many people install Flannel
without doing this, it's probably fair to remove this again to prevent
more people running into the issue I had.

This reverts commit a93a407.
  • Loading branch information
lkiesow committed Sep 2, 2022
1 parent f30ebbb commit 9dcc0ef
Showing 1 changed file with 1 addition and 3 deletions.
4 changes: 1 addition & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,9 +32,7 @@ Though not required, it's recommended that flannel uses the Kubernetes API as it
Flannel can be added to any existing Kubernetes cluster though it's simplest to add `flannel` before any pods using the pod network have been started.

For Kubernetes v1.17+

1. Make sure a `flanneld` binary exists at `/opt/bin/flanneld` on each node
2. `kubectl apply -f https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/kube-flannel.yml`
`kubectl apply -f https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/kube-flannel.yml`

If you use custom `podCIDR` (not `10.244.0.0/16`) you first need to download the above manifest and modify the network to match your one.

Expand Down

0 comments on commit 9dcc0ef

Please sign in to comment.