Open xvzf opened 2 years ago
Hello @xvzf,
We currently do not use the CRDs as YAML and do not have them in the repo to reduce our maintenance. However if you would like, you can get the YAML form by querying a cluster:
kubectl get crds backendconfigs.cloud.google.com -o yaml > backendconfig.yaml
kubectl get crds frontendconfigs.networking.gke.io -o yaml > frontendconfig.yaml
Hi @swetharepakula this is fine but we'd need a static exposure of them to automatically generate them. It's not a manual task for now. Would you consider adding them to this repo or is it a no-go?
Hi @xvzf, Do our API definitions work? Those are what we generate our CRDs.
@swetharepakula Unfortunately no, we'd need a YAML file, containing the rendered CRDs that are applied to the cluster then
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/lifecycle frozen
We built a library around GKE CRDs using cdk8s import. It seems running kubectl get crds ..
is the only option. This has some drawbacks like
kubectl get crd ..
cannot be guaranteed to return the same result on different clusters.. So it's not straightforward to track CRD changes and update generated cdk8s code.It would've been lot more helpful, if GKE CRDs were available as a yaml format and if it was possible to track which GKE versions comes with which Ingress Controller versions. So our internal toolings are consistent with GKE versions..
Hello
I'd like to generate jsonnet libraries for Grafana Tanka based on the CRDs but unfortunately they are not in any of the releases. Would you be open to address this?