search

kubernetes / sample-controller

Repository for sample controller. Complements sample-apiserver
Apache License 2.0
3.17k stars 1.1k forks source link

无法执行生成 #91

Closed weiqiangxu closed 6 months ago

weiqiangxu commented 1 year ago

./hack/update-codegen.sh ./hack/update-codegen.sh: 行 24: ../code-generator/kube_codegen.sh: No such file or directory

godblesslancek commented 1 year ago

Hello, I personally solved it by git cloning the code-generator repository https://github.com/kubernetes/code-generator in the root directory of the repo. I also cd into hack before executing ./update-codegen.sh. If I don't do so, I encounter problems because the script doesn't expect that you execute it in the root directory.

googs1025 commented 1 year ago

Hey bro, you need to check if there is this file in the directory, or don't execute this script from the root directory, you need to execute it in the project directory

quartzeast commented 1 year ago

switch to a newer branch, like release-1.27, and run go mod vendor, and then in your project root run chmod +x ./vendor/k8s.io/code-generator/generate-groups.sh, Add executable permissions to the script, and finally run ./hack/update-codegen.sh in the project root

silentred commented 11 months ago

switch to a newer branch, like release-1.27, and run go mod vendor, and then in your project root run chmod +x ./vendor/k8s.io/code-generator/generate-groups.sh, Add executable permissions to the script, and finally run ./hack/update-codegen.sh in the project root

I followed the steps above. The ./hack/update-codegen.sh command generated codes out side of my project. My project is at /Users/jason/Desktop/projects/sample-controller, however the generated code is at /Users/jason/Desktop/

image

k8s-triage-robot commented 8 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 7 months ago

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:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 6 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 6 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/sample-controller/issues/91#issuecomment-2081326528): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.