-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
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
remove subnet from the output in kubectl get
#1609
Conversation
✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@mdbooth pleaes take a quick look :) |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jichenjc, mnaser The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test pull-cluster-api-provider-openstack-e2e-test |
1 similar comment
/test pull-cluster-api-provider-openstack-e2e-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I knew it would be something like that! Thanks.
Are users going to miss this information? Is there any way to specify all subnet ids from the new slice in the JSONPath?
subnet => subnets means this is array.., as in the commit msg, I searched kubernetes-sigs/controller-tools#652 but seems they don't want to support it or maybe I missed something ? |
It looks like yes: https://kubernetes.io/docs/reference/kubectl/jsonpath/ I can try to construct the correct incantation when I get back if you like (I'm on my phone right now). Or... we could report network id instead. Or just remove it like this. I don't understand how this information is used in practise, so it's hard for me to judge. That's the only reason I feel like the safest thing might be to retain it as a list of subnet ids. What do you think? |
no rush :) I think we already provide net id ? I believe if they need subnet ID they can always |
/lgtm Lets get rid of it because, as you say: it's definitely wrong right now. We can add subnets later if anybody asks for it, but as we're removing |
/hold cancel |
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 #1608
Special notes for your reviewer:
we made it subnets now , seems we can't get it if it's CRD
kubernetes-sigs/controller-tools#652
so remove seems better than show nothing ..
TODOs:
/hold