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

Update upstream main branch #579

Merged
merged 5 commits into from
Jan 8, 2024
Merged

Update upstream main branch #579

merged 5 commits into from
Jan 8, 2024

Conversation

AndiDog
Copy link

@AndiDog AndiDog commented Jan 8, 2024

git merge upstream/main

tobiasgiese and others added 5 commits December 18, 2023 20:56
We have an issue that there is a gap between the CAPI Machine deletion and the AWSMachine deletion.
In this timeframe the kube-apiserver to the to be deleted control plane is no longer possible, but the deregistering of the LB member will be performed only for AWSMachine deletions.
This PR fixes the gap and also deregisteres the instance if the CAPI Machine is deleted.

Signed-off-by: Tobias Giese <tobias.giese@mercedes-benz.com>
…e/fix-deregister-scaledown

🐛 Fix deregistering of deleted CAPI Machines
…r was removed

Co-authored-by: Andreas Sommer <andreas@giantswarm.io>
✨ Use go 1.21.5, fix kubectl version detection after `--short` parameter was removed
@AndiDog AndiDog merged commit 9074fd4 into main Jan 8, 2024
3 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants