Rename network prefix#424
Conversation
cloud provider and others might create this kind of resource as well, we might consider to make it clusterapi specific
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jichenjc The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@jichenjc Are they really creating additional networks? |
|
they use k8s a lot, my assumption is to either make it clear created by clusterapi, or we make it configurable for resources created by us to avoid consume people ...anyway, just my own thought |
|
It's fine for me. Just wanted to ask :). In the current state of the ClusterAPI provider I don't really care about changes like this. After a release this would be a breaking change :) /lgtm |
cloud provider and others might create this kind of resource as well, we might consider to make it clusterapi specific
cloud provider and others might create this kind of resource
as well, we might consider to make it clusterapi specific
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Release note: