Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Instance Host Labelling #998

Closed
misterikkit opened this issue Apr 24, 2019 · 12 comments
Closed

Instance Host Labelling #998

misterikkit opened this issue Apr 24, 2019 · 12 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@misterikkit
Copy link

Enhancement Description

  • One-line enhancement description (can be used as a release note):
    Instance Host Labelling
  • Kubernetes Enhancement Proposal: Create KEP for instance host labelling #997
  • Primary contact (assignee): @misterikkit
  • Responsible SIGs: @kubernetes/sig-cloud-provider, @kubernetes/sig-scheduling-feature-requests
  • Enhancement target (which target equals to which milestone):
    • Alpha release target (1.15)
    • Beta release target (x.y)
    • Stable release target (x.y)

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

original feature request is in kubernetes/kubernetes#75274

@k8s-ci-robot k8s-ci-robot added sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. kind/feature Categorizes issue or PR as related to a new feature. labels Apr 24, 2019
@misterikkit
Copy link
Author

/sig cloud-provider

@k8s-ci-robot k8s-ci-robot added the sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. label Apr 24, 2019
@mrbobbytables
Copy link
Member

/milestone v1.15
/stage alpha

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Apr 25, 2019
@k8s-ci-robot k8s-ci-robot added this to the v1.15 milestone Apr 25, 2019
@mrbobbytables mrbobbytables added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Apr 25, 2019
@justaugustus
Copy link
Member

/assign @misterikkit

@craiglpeters
Copy link
Contributor

@misterikkit, Enhancement Freeze for Kubernetes 1.15 has passed and this did not meet the deadline. This is now being removed from the 1.15 milestone and the tracking sheet. If there is a need for this to be in 1.15, please file an Enhancement Exception. Thank you.

@craiglpeters craiglpeters added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels May 1, 2019
@craiglpeters
Copy link
Contributor

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.15 milestone May 1, 2019
@alculquicondor
Copy link
Member

Hi @misterikkit, I just submitted #1127 focusing only in the label name. Could you please update the issue? Unless it's preferred that I create a new one.

@kacole2
Copy link

kacole2 commented Jul 9, 2019

Hi @alculquicondor @misterikkit , I'm the 1.16 Enhancement Lead. Is this feature going to be graduating alpha/beta/stable stages in 1.16? Please let me know so it can be added to the 1.16 Tracking Spreadsheet. If not's graduating, I will remove it from the milestone and change the tracked label.

Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly.

Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.

Thank you.

@ahg-g
Copy link
Member

ahg-g commented Jul 9, 2019

/milestone v1.16
/alpha

@k8s-ci-robot
Copy link
Contributor

@ahg-g: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone v1.16
/alpha

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.

@alculquicondor
Copy link
Member

@kacole2 yes, this should be in the 1.16 milestone. Thanks

@kacole2 kacole2 added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Jul 9, 2019
@kacole2 kacole2 added this to the v1.16 milestone Jul 9, 2019
@kacole2
Copy link

kacole2 commented Jul 26, 2019

Closing because of #1127 (comment)

/close
/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.16 milestone Jul 26, 2019
@k8s-ci-robot
Copy link
Contributor

@kacole2: Closing this issue.

In response to this:

Closing because of #1127 (comment)

/close
/milestone clear

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.

@kacole2 kacole2 added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Jul 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
None yet
Development

No branches or pull requests

8 participants