search

kubernetes / sample-controller

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

Documentation error: example CRD already exists while trying to apply manually #87

Closed pravarag closed 1 year ago

pravarag commented 2 years ago

Following the documentation I've tried to apply the steps mentioned here: https://github.com/pravarag/sample-controller#running

For the step:

# create a CustomResourceDefinition
kubectl create -f artifacts/examples/crd-status-subresource.yaml

It throws below error upon applying as the crd already exists in the cluster (possibly due to the previous step):

Error from server (AlreadyExists): error when creating "artifacts/examples/crd-status-subresource.yaml": customresourcedefinitions.apiextensions.k8s.io "foos.samplecontroller.k8s.io" already exists

If this is the expected output, the document can be updated with the removal of the extra step mentioned. I'll be happy to submit a PR on same.

pravarag commented 2 years ago

Got a similar erro while trying to apply the below step as well:

# create a custom resource of type Foo
kubectl create -f artifacts/examples/example-foo.yaml

Error:

Error from server (AlreadyExists): error when creating "artifacts/examples/crd-status-subresource.yaml": customresourcedefinitions.apiextensions.k8s.io "foos.samplecontroller.k8s.io" already exists
k8s-triage-robot commented 1 year ago

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:

You can:

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

/lifecycle stale

k8s-triage-robot commented 1 year ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 1 year 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 1 year ago

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

In response to [this](https://github.com/kubernetes/sample-controller/issues/87#issuecomment-1416378928): >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.