Construct working (not perfect yet) network for the cluster #44
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jakolehm
approved these changes
Jul 2, 2020
Signed-off-by: Jussi Nummelin <jnummelin@mirantis.com>
Signed-off-by: Jussi Nummelin <jnummelin@mirantis.com>
jnummelin
force-pushed
the
working-network
branch
from
4959402
to
a27d57d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Jussi Nummelin jnummelin@mirantis.com
This started as a PR to get just Calico in. Ended up building lots of things.
Running calico actually needs working kube-proxy as calico uses the clusters internal api address for eveything.
--> Had to build kube-proxy support
While building support for kube-proxy, sidetracked to build support for config file reading. This is 100% needed to be able to set API address etc. properly. Without those we cannot get kube-proxy up-and-running.
To be able to figure out why stuff does not work we need working
kubectl logs xyz, that requires we have properly set up auth between api and kubelet.--> Needed to fix that plus get the CA cert for kubelet
CoreDNS bundle to actually get DNS running, and to test the network even partially works. :D
Sorry for such a huge PR, would've been pretty impossible to break this into smaller pieces.