conformance: Added bpf-hostlegacyrouting option #174
Merged
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.
Added a configurable bpf-hostlegacyrouting option to the conformance tests as Cilium 1.16.5+ introduced a breaking change for Talos 'forwardKubeDNSToHost'. See cilium/cilium#35098 for more details.
I've explicitly set
bpf-hostlegacyrouting: true
for all test cases. For the KPR ones to fix the issue mentioned above, and for the others as it's disabled anyway in their case (because of enabled IPsec and KPR being disabled). Please look at the relevant code here.