make sure gw pod exist before eip creation

[zbb88888]

Pull Request

• Make sure you have followed Kube-OVN Code Style.

What type of this PR

Examples of user facing changes:

• Bug fixes

#4922

Which issue(s) this PR fixes

Fixes #(issue-number)

[coveralls]

Pull Request Test Coverage Report for Build 12800143555

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 4 (0.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.002%) to 22.331%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
pkg/controller/vpc_nat_gw_eip.go	0	4	0.0%

Totals
Change from base Build 12799483227:	-0.002%
Covered Lines:	10376
Relevant Lines:	46464

---

💛 - Coveralls

[cruickshankpg]

thanks for this. I think this will prevent the leak when the EIP is misconfigured. There's still the risk that the nat gateway is broken in some way and the exec in pod fails which may cause the IP to leak but that's more of an edge case

[zbb88888]

thanks for this. I think this will prevent the leak when the EIP is misconfigured. There's still the risk that the nat gateway is broken in some way and the exec in pod fails which may cause the IP to leak but that's more of an edge case

yeah, if the pod crashes, and can not run up later, the EIP is leaked. how about talking about theses cases in detail later, we will try to help fix them too.

[zbb88888]

@oilbeater 这个ut降低跟这个pr应该也没关系