Closed cjschaef closed 3 months ago
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 /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
Name | Link |
---|---|
Latest commit | 4012d7ccba8fb30b80b81f2417ee3e83b67ef3b8 |
Latest deploy log | https://app.netlify.com/sites/kubernetes-sigs-cluster-api-ibmcloud/deploys/66c60b58c96a7000085b9642 |
Deploy Preview | https://deploy-preview-1895--kubernetes-sigs-cluster-api-ibmcloud.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
/cc @Karthik-K-N
/ok-to-test
@dharaneeshvrd please take a look when you get some time.
/cc @dharaneeshvrd
Based on further investigation on requirements for Catalog Offerings, I have extended the ImageSpec to include a CatalogOffering resource now as well, to allow user to define whether an existing VPC Image is used, a Catalog Offering, or a new VPC Image gets created during Infrastructure reconciliation.
Rebased to resolve mock generation.
I dropped the Catalog Offering configuration for the Image definition, as I expect to handle it only within Machine API's and we may not have permission to validate a Catalog Offering, thus providing it in the Infrastructure is not useful.
It seems you need to regenerate the CRD def yamls, otherwise it LGTM!
@dharaneeshvrd Is there something specific I need to run to do that?
make generate
would do that.
@dharaneeshvrd I have run that prior, I don't think it passes CI tests unless the CRD files are updated. Is there something specific missing, or perhaps something I need to add into a list to generate what appears to be missing?
@cjschaef Apologies for the confusion, it is updated properly. LGTM, @mkumatag please review!
@mkumatag I added some enum validation to some of the type fields, but I cannot validate locally to confirm things work as expected (issues with CRD resource creation). Please let me know if you see further issues.
@mkumatag I added some enum validation to some of the type fields, but I cannot validate locally to confirm things work as expected (issues with CRD resource creation). Please let me know if you see further issues.
Getting a proper message now,
k apply -f test/vpc_cluster.yaml
The IBMVPCCluster "test-1" is invalid:
* spec.controlPlaneLoadBalancer.backendPools[0].algorithm: Unsupported value: "invalid-algo": supported values: "least_connections", "round_robin", "weighted_round_robin"
* spec.controlPlaneLoadBalancer.backendPools[0].healthMonitor.type: Unsupported value: "invalidtype": supported values: "http", "https", "tcp"
* spec.controlPlaneLoadBalancer.backendPools[0].protocol: Unsupported value: "": supported values: "http", "https", "tcp", "udp"
(base)
[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
Extending VPC related Cluster API's in order to provide additional VPC Infrastructure reconciliation support.
What this PR does / why we need it: introduces API's that will be used for extended VPC Cluster (Infrastructure) 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: