-
Notifications
You must be signed in to change notification settings - Fork 13
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
kubeadm/calico: use public IP #486
Merged
Merged
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
pothos
approved these changes
Nov 27, 2023
Noticed while debugging Calico on DO: ``` Warning Failed 7m25s (x4 over 8m47s) kubelet Failed to pull image "ghcr.io/flatcar/calico/apiserver:v3.26.4": rpc error: code = Unknown desc = failed to pull and unpack image "ghcr.io/flatcar/calico/apiserver:v3.26.4": failed to resolve reference "ghcr.io/flatcar/calico/apiserver:v3.26.4": failed to authorize: failed to fetch anonymous token: unexpected status: 403 Forbidden ``` Signed-off-by: Mathieu Tortuyaux <[email protected]>
Signed-off-by: Mathieu Tortuyaux <[email protected]>
tormath1
force-pushed
the
tormath1/calico-do
branch
from
November 28, 2023 17:32
3ee5647
to
d7be6f8
Compare
tormath1
changed the title
kubeadm/calico: switch to VXLAN (always)
kubeadm/calico: use public IP
Nov 28, 2023
pothos
reviewed
Nov 28, 2023
kola/tests/kubeadm/templates.go
Outdated
@@ -379,6 +384,10 @@ kind: InitConfiguration | |||
nodeRegistration: | |||
kubeletExtraArgs: | |||
volume-plugin-dir: "/opt/libexec/kubernetes/kubelet-plugins/volume/exec/" | |||
{{ if eq .Platform "do" }} | |||
# On digital ocean, the node IP is often not reachable - let's use the public one. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What means "often"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. I wanted to say something else I guess.
pothos
approved these changes
Nov 28, 2023
Signed-off-by: Mathieu Tortuyaux <[email protected]>
tormath1
force-pushed
the
tormath1/calico-do
branch
from
November 29, 2023 09:19
d7be6f8
to
05ae425
Compare
Tested again:
all pods and running / ready and NFS tests are passing. |
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.
On Digital Ocean, there are two network interfaces (one public and one private) - by default, Calico / Kubernetes was autodetecting the private one but doing this, the
calico-node
daemon set was not ready because of bgp issue.this was not an issue until we started to have pod-to-elsewhere connections (like with NFS)
Locally tested with current stable: