add info to routeUpdate msg in Felix for node updates #10
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
After this patch, single IPs are no longer announced as global routes. The patch also fixes a bug related to config change, causing one or more route to be withdrawn if changing from for example /32 to /29 in BGPConfiguration. Now setRoutesForKey() assures that routes it thinks are advertised actually do exist.
…olicy Cluster. Do not advertise these as /32 routes when part of a larger subnet definition.
hedibouattour
force-pushed
the
Feature/add-info-to-routeUpdate-msg
branch
from
5ae4903
to
6285f74
Compare
Move the staggering to the connectivity check. Looks like the handshake is only done on first packet so our synchronised connectivity check is worst case.
hedibouattour
force-pushed
the
Feature/add-info-to-routeUpdate-msg
branch
2 times, most recently
from
ff4bdd3
to
ab347b1
Compare
Issues described in projectcalico#4509 are only UDP related. We need to turn off CTLB for UDP. TCP would resolve broken connections as the original pod would not exist anymore and would make a new connection. Therefore it does not need to take the performance hit associated with disabling CTLB.
Update the ipsec.yaml file's location
Use kubectl replace instead of apply when upgrading. If you don't, you hit: ``` The CustomResourceDefinition "installations.operator.tigera.io" is invalid: metadata.annotations: Too long: must have at most 262144 bytes ```
Avoid running APT from Golang.
Adjust wireguard deflake fix.
fixing typo in front matter
Move hping into the felix test image.
…tlb-udp felix/bpf: allow using CTLB workaround just for UDP
In some cases, the delay between CRDs being successfully created and the API resources that represent them being available was long enough for the IPAM metrics FV setup to fail (resource not found).
Fix IPAM metrics test flake
Update kubernetes-upgrade.md
DOCS-602: Fixes syntax for a note
…-master Update multiple dependencies
…ouncements Fix announcement of /32 and /128 entries for serviceLoadBalancerIPs.
Finesse health reports, actually print the table not its string.
Use kubectl replace instead of applying when upgrading. This avoids the possibility of a 2-way merge leaving behind unwanted fields as described in projectcalico#6848
DOCS-854: Removes extra toc
Add CSI node-driver-registrar to image list for private registry use
…counters may not be present (projectcalico#6835) Continue on errors while reading or flushing XDP counters map Failing in dumping or flushing a counter map should not prevent the operation for the rest of maps. So instead of returning an error, we just need to log and continue with the rest of maps. Co-authored-by: Tomas Hruby <[email protected]>
Update kubernetes-upgrade.md
hedibouattour
force-pushed
the
Feature/add-info-to-routeUpdate-msg
branch
from
ab347b1
to
3f3d6b3
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.
Description
Related issues/PRs
Todos
Release Note
Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one
docs-*label.docs-pr-required: This change requires a change to the documentation that has not been completed yet.docs-completed: This change has all necessary documentation completed.docs-not-required: This change has no user-facing impact and requires no docs.Every PR needs one
release-note-*label.release-note-required: This PR has user-facing changes. Most PRs should have this label.release-note-not-required: This PR has no user-facing changes.Other optional labels:
cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.