We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When the provider is trying to delete the cluster. It sometimes get stuck on SG deletion.
If two SG (a and b) are as follows:
The provider will not delete the cluster correctly because the rule in SG b is still existing when deleting SG a.
Instead of trying the same SG all the time, we would go to the next one before retrying the same one during 10 minutes.
Talos example
N/A
- Kubernetes version: (use `kubectl version`): - OS (e.g. from `/etc/os-release`): - Kernel (e.g. `uname -a`): - cluster-api-provider-outscale version: - cluster-api version: - Install tools: - Kubernetes Distribution: - Kubernetes Diestribution version:
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
What happened
When the provider is trying to delete the cluster. It sometimes get stuck on SG deletion.
If two SG (a and b) are as follows:
The provider will not delete the cluster correctly because the rule in SG b is still existing when deleting SG a.
Instead of trying the same SG all the time, we would go to the next one before retrying the same one during 10 minutes.
Step to reproduce
Talos example
Expected to happen
N/A
Add anything
N/A
cluster-api output
N/A
Environment
The text was updated successfully, but these errors were encountered: