WIP: fix(openstack): determine ports to delete based on tags #16961
+34
−11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This will determine the ports to delete when deleting an InstanceGroup in OpenStack based on the tags, rather than comparing the prefix of the name of the port to a pattern.
The current approach for deleting ports associated with an InstanceGroup in OpenStack can be problematic.
For example, when creating an InstanceGroup called
worker
and another one calledworker-2
. Some of the ports kOps creates for those groups will look like this:port-worker-2-1-<clusterName>
port-worker-2-2-<clusterName>
port-worker-1-<clusterName>
port-worker-2-<clusterName>
port-worker-20-<clusterName>
Deleting the
worker-2
IG will ultimately delete all the ports prefixed withport-worker-2
, which means that kOps will also delete ports of theworker
IG.TODO: