-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Update pods with readinessGate as healthy for deleted TGB #2524
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
Conversation
Hi @oliviassss. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Codecov Report
@@ Coverage Diff @@
## main #2524 +/- ##
==========================================
- Coverage 53.97% 53.85% -0.12%
==========================================
Files 144 144
Lines 8147 8165 +18
==========================================
Hits 4397 4397
- Misses 3433 3451 +18
Partials 317 317
Continue to review full report at Codecov.
|
/ok-to-test |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kishorj, oliviassss The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
return err | ||
} | ||
if !exists { | ||
return errors.New("couldn't find podInfo for ready endpoint") |
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.
we should just continue
if pod not found.
we can fix it in future versions as it's rare to trigger and won't cause much defect.
|
||
allPodKeys := m.podInfoRepo.ListKeys(ctx) | ||
for _, podKey := range allPodKeys { | ||
pod, exists, err := m.podInfoRepo.Get(ctx, podKey) |
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.
we should check for pod's namespace here as well.
Since in theory you can have two targetGroupBinding in two namespace.
In practice, with our default Ingress/Service implementation, the TGB's name is same as TargetGroup's name and will be unique across namespaces.
but this will impact user created targetGroupBinding.
we can fix it in future versions as the impact is minimal
…-sigs#2524) * mark pod with readiness gate as healthy when deleting TGB * list pod keys Co-authored-by: Kishor Joshi <[email protected]>
Issue
#2393
#1764
Description
To avoid race condition between pods readiness gate, this PR adds a step to mark podCondition with associated TargetGroupBinding's readinessGate as healthy when delete a TargetGroupBinding.
Test
1/1
, and the new target group is registered to the TargetGroupBinding.Checklist
README.md
, or thedocs
directory)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯