kubebuilder icon indicating copy to clipboard operation
kubebuilder copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

We should have an FAQ / common issues book section

Open DirectXMan12 opened this issue 4 years ago • 12 comments

There's all sorts of weird k8s API server issues (and a few KB-specific ones :wink:) that folks can run into, and we should document them somewhere.

Off the top of my head:

  • Weird issues when a v1beta1 CRD is already installed in the cluster (invisibly set preserveUnknownFields, refusal to chance certain fields, etc)

/kind docs

DirectXMan12 avatar Oct 13 '20 23:10 DirectXMan12

@DirectXMan12: The label(s) kind/docs cannot be applied, because the repository doesn't have them

In response to this:

There's all sorts of weird k8s API server issues (and a few KB-specific ones :wink:) that folks can run into, and we should document them somewhere.

Off the top of my head:

  • Weird issues when a v1beta1 CRD is already installed in the cluster (invisibly set preserveUnknownFields, refusal to chance certain fields, etc)

/kind docs

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot avatar Oct 13 '20 23:10 k8s-ci-robot

/help

DirectXMan12 avatar Oct 13 '20 23:10 DirectXMan12

@DirectXMan12: This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot avatar Oct 13 '20 23:10 k8s-ci-robot

Following a few examples to help who will work on in this task:

  • controller-runtime; https://github.com/kubernetes-sigs/controller-runtime/blob/master/FAQ.md
  • sdk: https://sdk.operatorframework.io/docs/faqs/faqs/

camilamacedo86 avatar Oct 20 '20 12:10 camilamacedo86

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

fejta-bot avatar Jan 18 '21 19:01 fejta-bot

/remove-lifecycle stale

camilamacedo86 avatar Jan 18 '21 20:01 camilamacedo86

We can explain that and link https://book.kubebuilder.io/cronjob-tutorial/gvks.html.

camilamacedo86 avatar Mar 29 '21 16:03 camilamacedo86

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

fejta-bot avatar Jun 27 '21 16:06 fejta-bot

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten

k8s-triage-robot avatar Jul 27 '21 17:07 k8s-triage-robot

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:

  • 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 or PR with /reopen
  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

/close

k8s-triage-robot avatar Aug 26 '21 17:08 k8s-triage-robot

@k8s-triage-robot: Closing this issue.

In response to this:

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:

  • 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 or PR with /reopen
  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot avatar Aug 26 '21 17:08 k8s-ci-robot

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:

  • 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:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Apr 06 '22 13:04 k8s-triage-robot

We can close this one because we have a FAQ section now, see: https://github.com/kubernetes-sigs/kubebuilder/pull/3044

Regards the need:

Weird issues when a v1beta1 CRD is already installed in the cluster (invisibly set preserveUnknownFields, refusal to chance certain fields, etc)

It seems outdated since v1beta1 CRD is no longer supported.

So, it seems fine we close this one.

camilamacedo86 avatar Oct 31 '22 21:10 camilamacedo86