Skip to content
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

Cluster updates #58

Merged
merged 4 commits into from
Jul 7, 2022
Merged

Cluster updates #58

merged 4 commits into from
Jul 7, 2022

Conversation

danisla
Copy link
Member

@danisla danisla commented Jun 28, 2022

  • Update the Selkies CRD to use API v1.
  • Use CNRM GKE addon instead of manual install.
  • Improve custom domain and load balancer support.

@danisla danisla requested a review from reisbel June 28, 2022 15:12
@videlanicolas
Copy link
Contributor

I checked out this branch and re-deployed my infrastructure. It seems apiextensions.k8s.io/v1 is not getting picked up:

Step #1 - "deploy-manifests": Installing CRDs
Step #1 - "deploy-manifests": Applying deployment.
Step #1 - "deploy-manifests": Getting access to cluster "broker-us-west1" in "us-west1".
Step #1 - "deploy-manifests": Configuration files to be used: [{kind: CustomResourceDefinition, name: istiocontrolplanes.install.istio.io}]
Step #1 - "deploy-manifests": Applying configuration files to cluster.
Step #1 - "deploy-manifests": error: unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
Step #1 - "deploy-manifests": Error: failed to apply deployment: failed to apply CustomResourceDefinition configuration file with name "istiocontrolplanes.install.istio.io" to cluster: failed to apply config from string: command to apply kubernetes config from string to cluster failed: exit status 1
Finished Step #1 - "deploy-manifests"
ERROR
ERROR: build step 1 "gcr.io/REDACTED/broker-installer" failed: step exited with non-zero status: 1
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

BUILD FAILURE: Build step failure: build step 1 "gcr.io/REDACTED/broker-installer" failed: step exited with non-zero status: 1
ERROR: (gcloud.builds.submit) build 760aef79-1cd9-4ff7-a718-5ec795db05ad completed with status "FAILURE"

I tried to manually apply the .yaml file:

$ gke-deploy apply --project ${PROJECT_ID} --cluster broker-us-west1 --location us-west1 --filename base/pod-broker/crd.yaml
Applying deployment.
Getting access to cluster "broker-us-west1" in "us-west1".
Configuration files to be used: [{kind: CustomResourceDefinition, name: brokerappconfigs.gcp.solutions} {kind: CustomResourceDefinition, name: brokerappuserconfigs.gcp.solutions}]
Applying configuration files to cluster.
The CustomResourceDefinition "brokerappconfigs.gcp.solutions" is invalid:
* spec.validation.openAPIV3Schema.properties[spec].properties[nodeTiers].items.properties[resources].properties[limits].properties[cpu].type: Required value: must not be empty for specified object fields
* spec.validation.openAPIV3Schema.properties[spec].properties[nodeTiers].items.properties[resources].properties[requests].properties[cpu].type: Required value: must not be empty for specified object fields
Error: failed to apply deployment: failed to apply CustomResourceDefinition configuration file with name "brokerappconfigs.gcp.solutions" to cluster: failed to apply config from string: command to apply kubernetes config from string to cluster failed: exit status 1

It seems you need to specify type for openAPIV3Schema.properties[spec].properties[nodeTiers].items.properties[resources].properties[requests].properties[cpu]Probably type: object on both cases? I used that and it worked.

@videlanicolas
Copy link
Contributor

/opt/istio-operator/deploy/crds/istio_v1alpha2_istiocontrolplane_crd.yaml also depends on apiextensions.k8s.io/v1beta1, so we should update to the latest istio.

@danisla
Copy link
Member Author

danisla commented Jul 5, 2022

@videlanicolas thanks, I think the CRD schema should be now.

Working on updating istio now, it will be in the next PR.

Copy link
Contributor

@reisbel reisbel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@reisbel reisbel merged commit b083fe6 into master Jul 7, 2022
@reisbel reisbel deleted the cluster-updates branch July 7, 2022 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants