Skip to content

Enabling clients to tell if resource endpoints serve the same set of objects #2341

Closed
@ghost

Description

Enhancement Description

  • One-line enhancement description (can be used as a release note):

Enabling clients to tell if resource endpoints serve the same set of objects

  • Kubernetes Enhancement Proposal:

We propose to expand the discovery API to enable clients to tell if resource
endpoints (e.g., extensions/v1beta1/replicaset and apps/v1/replicaset) are
referring the same set of objects.

Motivation

Today, some workload objects (e.g., replicasets) are accessible from both the
extensions and the apps endpoints. This can happen to more of Kubernetes
APIs in the future. Enabling the clients to programmatically detect aliasing
endpoints can improve both the correctness and the efficiency.

    • Discussion Link:
    • Primary contact (assignee): @xuchao
    • Responsible SIGs: sig-api-machinery
    • Enhancement target (which target equals to which milestone):
      • Alpha release target (x.y):
      • Beta release target (x.y):
      • Stable release target (x.y):
    • Alpha
      • KEP (k/enhancements) update PR(s):
      • Code (k/k) update PR(s):
      • Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

Activity

added
needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.
on Jan 26, 2021
k8s-ci-robot

k8s-ci-robot commented on Jan 26, 2021

@k8s-ci-robot
Contributor

@shekhar-rajak: There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

  • /sig <group-name>
  • /wg <group-name>
  • /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

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.

ghost
fejta-bot

fejta-bot commented on Apr 26, 2021

@fejta-bot

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

added
lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
on Apr 26, 2021
fejta-bot

fejta-bot commented on May 26, 2021

@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

added
lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
and removed
lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
on May 26, 2021
fejta-bot

fejta-bot commented on Jun 25, 2021

@fejta-bot

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

k8s-ci-robot

k8s-ci-robot commented on Jun 25, 2021

@k8s-ci-robot
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @k8s-ci-robot@fejta-bot

        Issue actions

          Enabling clients to tell if resource endpoints serve the same set of objects · Issue #2341 · kubernetes/enhancements