-
Notifications
You must be signed in to change notification settings - Fork 84
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
VPC: Extend VPC related API's for v2 VPC reconcile #1883
VPC: Extend VPC related API's for v2 VPC reconcile #1883
Conversation
Hi @cjschaef. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
✅ Deploy Preview for kubernetes-sigs-cluster-api-ibmcloud ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
/ok-to-test |
api/v1beta2/types.go
Outdated
@@ -400,3 +400,53 @@ type VPCEndpoint struct { | |||
// +optional | |||
LBID *string `json:"loadBalancerIPID,omitempty"` | |||
} | |||
|
|||
// GenericResourceReference represents a generic IBM Cloud resource. | |||
type GenericResourceReference struct { |
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 don't see this is used anywhere!
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.
Sorry, too early for that resource, I'll remove it for this PR.
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.
Removed
api/v1beta2/ibmvpccluster_types.go
Outdated
} | ||
|
||
// VPCResourceStatus identifies a VPC resource by id (and name) and whether it is ready. | ||
type VPCResourceStatus struct { |
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.
ResourceStatus
also look the same, can we reuse?
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 had designed the two status' initially, but can not recall why I had a unique one for VPC resources ATM.
I'll remove and use ResourceStatus
for all resources instead.
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.
Removed to use ResourceStatus
09a4350
to
0de029c
Compare
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 think its also ok to have one big PR with various small commits, so it gives overall good picture of intent of changes.
@@ -113,7 +113,11 @@ type VPCNetworkSpec struct { | |||
// +optional | |||
ResourceGroup *string `json:"resourceGroup,omitempty"` | |||
|
|||
// TODO(cjschaef): Complete spec definition (SecurityGroups, VPC) | |||
// vpc defines the IBM Cloud VPC. | |||
// +optional |
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.
We already have a field named VPC under IBMVPCClusterSpec, so may be lets add a comment whereever it looks appropriate on whats the difference or when to use which 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.
I added a little more detail to this field and some other fields/structs, as they related to the extended VPC Infra support.
0de029c
to
81951c8
Compare
Repushing to get CLA to pass. Done |
Extend the API's used in the v2 support of reconciling VPC for the VPCCluster support.
81951c8
to
4909b40
Compare
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cjschaef, mkumatag 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 |
Extend the API's used in the v2 support of reconciling VPC for the VPCCluster support.
What this PR does / why we need it: implements the v2 support of reconciling a VPC for VPCCluster support
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:
/area provider/ibmcloud
Release note: