-
Notifications
You must be signed in to change notification settings - Fork 261
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
⚠️ Move InstanceID from Spec to Status #1988
⚠️ Move InstanceID from Spec to Status #1988
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mdbooth 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 |
✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
75e2bb0
to
a6b46de
Compare
a6b46de
to
5c1ad44
Compare
/test pull-cluster-api-provider-openstack-e2e-full-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.
It lgtm, I just have one question:
@@ -119,6 +118,10 @@ type OpenStackMachineStatus struct { | |||
// +optional | |||
Ready bool `json:"ready"` | |||
|
|||
// InstanceID is the OpenStack instance ID for this machine. | |||
// +optional | |||
InstanceID optional.String `json:"instanceID,omitempty"` |
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.
Have we considered adding it under the Resolved
field?
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.
My first PR put it in Resources
. This made sense, but I've decided against that for now. The reason is I think InstanceID is fundamental
to the OpenStackMachine object and something an end user might be interested in (e.g. in printcolumns
), but the other properties are not.
I have an idea that I might move actual machine creation into a separate controller with its own CRD, in which case Resources
would move to the new controller. In that case I think we'd still want InstanceID to be on this object, so I decided to put it here instead.
None of which precludes adding it to Resources in the future too if it turns out that still makes sense.
/lgtm looks good |
/hold cancel |
This is a status field and should not be included in the spec. ProviderID is the same, but cannot be removed as it is required by Cluster API.
This PR replaces #1961 with a smaller scope.
TODO:
restorev1alpha6MachineTemplateMachineSpec
into 🐛 Fix multiple panics in restore functions #1989/hold