Open koala7659 opened 1 year ago
Quote from Slack thread where we analysed the code:
Basically there is nothing wrong with the code, it’s just for many runtimes the VNet CIDR was expanded during the HA migration and this was not reflected back in provisioner DB. This resulted in an undefined behaviour when executing that specific part of the code using stale input from DB vs changed infra config on shoot. Since the particular code was developed for NAT gateway enablement of existing SKRs which was never used and won’t be needed in the future, it is safe to remove this code to avoid future problems
More information can be found at control-plane issue 4387 in some internal Github
This issue or PR has been automatically marked as stale due to the lack of recent activity. Thank you for your contributions.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
If you think that I work incorrectly, kindly raise an issue with the problem.
/lifecycle stale
This issue or PR has been automatically closed due to the lack of activity. Thank you for your contributions.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle stale
If you think that I work incorrectly, kindly raise an issue with the problem.
/close
@kyma-bot: Closing this issue.
Description
The code for Azure NAT infra change to enable NAT gateway for existing runtimes is invalid and not used, but in some circonstances may cause problems to some migrated clusters:
https://github.com/kyma-project/control-plane/blob/main/components/provisioner/internal/model/gardener_config.go#L452-L489
Expected result
Remove obsolete code.