search

kubernetes-sigs / work-api

Kubernetes Work API
Apache License 2.0
54 stars 21 forks source link

WEP 2: Sync applied workload resource status #18

Closed mikeshng closed 5 months ago

mikeshng commented 2 years ago

Enhancement proposal to update the Work API to solve https://github.com/kubernetes-sigs/work-api/issues/16

Signed-off-by: Mike Ng ming@redhat.com

mikeshng commented 2 years ago

/assign pmorie

/assign RainbowMango

mikeshng commented 2 years ago

CC @qiujian16 @yue9944882 @jnpacker @ryanzhang-oss

k8s-ci-robot commented 2 years ago

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mikeshng To complete the pull request process, please ask for approval from pmorie after the PR has been reviewed.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/kubernetes-sigs/work-api/blob/master/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
RainbowMango commented 2 years ago

Just summarize the conclusion made on today's community meeting. (Please @mikeshng correct me If anything I get wrong)

  1. We are going to work out a new configuration API to define the rules on how to collect status.
  2. We can go back to the discussion about how to reference the new API and how to show the status in the Work API after the new API.
  3. We got some wonderful comments from @pmorie that the new API should consider the QPS thing, such as the frequency the status should be synced, and how long the status should be kept.

Thank all of you folks who are contributing to this proposal, hope we can work out the final solution together!

mikeshng commented 2 years ago

Based on the community feedback, we have enhanced the proposal to introduce a new manifest configuration API that defines the rules and the frequency/threshold of the workload manifest resource status sync. Please take a look and provide feedback. Thanks. @RainbowMango @qiujian16 @yue9944882 @jnpacker @ryanzhang-oss

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

mikeshng commented 1 year ago

/remove-lifecycle stale

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

mikeshng commented 1 year ago

/remove-lifecycle stale

k8s-triage-robot commented 1 year ago

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

This bot triages PRs according to the following rules:

You can:

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

/lifecycle stale

mikeshng commented 1 year ago

/remove-lifecycle stale

k8s-triage-robot commented 7 months ago

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

This bot triages PRs according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 6 months ago

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

This bot triages PRs according to the following rules:

You can:

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

/lifecycle rotten

mikeshng commented 6 months ago

/remove-lifecycle stale

k8s-triage-robot commented 5 months ago

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

This bot triages PRs according to the following rules:

You can:

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

/close

k8s-ci-robot commented 5 months ago

@k8s-triage-robot: Closed this PR.

In response to [this](https://github.com/kubernetes-sigs/work-api/pull/18#issuecomment-2012267114): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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 PR is closed > >You can: >- Reopen this PR with `/reopen` >- Mark this PR 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 > >[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.