Skip to content
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

#18325 v1.10 backport #18461

Merged
merged 1 commit into from
Jan 17, 2022
Merged

#18325 v1.10 backport #18461

merged 1 commit into from
Jan 17, 2022

Conversation

jibi
Copy link
Member

@jibi jibi commented Jan 12, 2022

Once this PR is merged, you can update the PR labels via:

$ for pr in 18325; do contrib/backporting/set-labels.py $pr done 1.10; done

@jibi jibi added kind/backports This PR provides functionality previously merged into master. backport/1.10 labels Jan 12, 2022
@jibi jibi requested a review from a team as a code owner January 12, 2022 19:51
@aditighag aditighag added the dont-merge/needs-rebase This PR needs to be rebased because it has merge conflicts. label Jan 14, 2022
@jibi jibi added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Jan 17, 2022
[ upstream commit ab9bfd7 ]

When a new egress gateway manager is created, it will wait for the k8s
cache to be fully synced before running the first reconciliation.

Currently the logic is based on the WaitUntilK8sCacheIsSynced method
of the Daemon object, which waits on the k8sCachesSynced channel to be
closed (which indicates that the cache has been indeed synced).

The issue with this approach is that Daemon object is passed to
the NewEgressGatewayManager method _before_ its k8sCachesSynced
channel is properly initialized. This in turn causes the
WaitUntilK8sCacheIsSynced method to never return.

Since NewEgressGatewayManager must be called before that channel is
initialized, we need to switch to a polling approach, where the
k8sCachesSynced is checked periodically.

Signed-off-by: Gilberto Bertin <gilberto@isovalent.com>
@jibi jibi force-pushed the pr/jibi/18325-v1.10-backport branch from 8009910 to 646aa7e Compare January 17, 2022 09:05
@jibi jibi removed ready-to-merge This PR has passed all tests and received consensus from code owners to merge. dont-merge/needs-rebase This PR needs to be rebased because it has merge conflicts. labels Jan 17, 2022
@jibi
Copy link
Member Author

jibi commented Jan 17, 2022

/test-backport-1.10

Job 'Cilium-PR-K8s-1.19-kernel-4.9' failed and has not been observed before, so may be related to your PR:

Click to show.

Test Name

K8sServicesTest Checks service across nodes with L7 policy Tests NodePort with L7 Policy

Failure Output

FAIL: Request from k8s1 to service http://[fd04::11]:31421 failed

If it is a flake, comment /mlh new-flake Cilium-PR-K8s-1.19-kernel-4.9 so I can create a new GitHub issue to track it.

@jibi
Copy link
Member Author

jibi commented Jan 17, 2022

4.9 failed because of a known flake #13011
ci-l4lb-1.10 is failing because #18370 has not been backported yet to v1.10

@jibi jibi added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Jan 17, 2022
@aditighag aditighag merged commit 6d1bc27 into v1.10 Jan 17, 2022
@aditighag aditighag deleted the pr/jibi/18325-v1.10-backport branch January 17, 2022 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/backports This PR provides functionality previously merged into master. ready-to-merge This PR has passed all tests and received consensus from code owners to merge.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants