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

[fix] When the Nat-gw pod container restarts unexpectedly, trigger nat-gw statefulset restart to restore the nat-gw pod configuration #5070

Merged
merged 1 commit into from
Mar 14, 2025

Conversation

kldancer
Copy link
Contributor

When the Nat-gw pod container restarts unexpectedly, trigger nat-gw statefulset restart to restore the nat-gw pod configuration

Pull Request

What type of this PR

Examples of user facing changes:

  • Bug fixes

Which issue(s) this PR fixes

Fixes #(4987)
#4987

@dosubot dosubot bot added size:M This PR changes 30-99 lines, ignoring generated files. bug Something isn't working labels Mar 11, 2025
…t-gw statefulset restart to restore the nat-gw pod configuration

Signed-off-by: ykl <[email protected]>
@kldancer kldancer force-pushed the v1.12.22-nat-gw-restart branch from 0440562 to f74b90a Compare March 11, 2025 05:34
@oilbeater
Copy link
Collaborator

@kldancer can you also make a pr to the master branch?

@kldancer
Copy link
Contributor Author

@kldancer can you also make a pr to the master branch?

ok

@oilbeater
Copy link
Collaborator

@kldancer Thanks!

A better solution might be to make the script that configures the VPC NAT gateway idempotent and rerun it whenever there is a change to any Pod. However, implementing this would require significant effort. So I think it's ok that we only resolve this first.

@oilbeater oilbeater merged commit d9e1d9e into kubeovn:release-1.12 Mar 14, 2025
53 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working size:M This PR changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants