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

feat: cleanup feature gates for KubeletPluginsWatcher #79310

Conversation

draveness
Copy link
Contributor

/kind cleanup

What this PR does / why we need it:

KubeletPluginsWatcher has already graduated to GA two releases ago, we could remove it in release 1.16

Which issue(s) this PR fixes:

ref: #79308

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Remove KubeletPluginsWatcher feature gates

/priority important-soon
/assign @vikaschoudhary16

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jun 23, 2019
@k8s-ci-robot k8s-ci-robot requested review from deads2k and liggitt June 23, 2019 09:02
@k8s-ci-robot k8s-ci-robot added area/kubelet sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/storage Categorizes an issue or PR as relevant to SIG Storage. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jun 23, 2019
Copy link
Contributor

@mattjmcnaughton mattjmcnaughton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

thanks for this clean up!

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 23, 2019
@mattjmcnaughton
Copy link
Contributor

/retest

@liggitt
Copy link
Member

liggitt commented Jun 24, 2019

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: draveness, liggitt

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

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 24, 2019
@k8s-ci-robot k8s-ci-robot merged commit 2109c1a into kubernetes:master Jun 24, 2019
@draveness draveness deleted the feature/cleanup-KubeletPluginsWatcher-feature-gates branch June 24, 2019 06:25
@liggitt liggitt added this to the v1.16 milestone Aug 6, 2019
rfranzke added a commit to rfranzke/gardener-extensions that referenced this pull request Sep 19, 2019
The feature gate was already beta in 1.13 (least supported version of
Alicloud/Packet which were using it) and enabled by default, it
graduated to GA in 1.14. We never needed to explicitly enable it, we
just have to make sure that it's not disabled.

See kubernetes/kubernetes#79310
rfranzke added a commit to gardener-attic/gardener-extensions that referenced this pull request Sep 19, 2019
The feature gate was already beta in 1.13 (least supported version of
Alicloud/Packet which were using it) and enabled by default, it
graduated to GA in 1.14. We never needed to explicitly enable it, we
just have to make sure that it's not disabled.

See kubernetes/kubernetes#79310
rfranzke added a commit to gardener-attic/gardener-extensions that referenced this pull request Sep 19, 2019
The feature gate was already beta in 1.13 (least supported version of
Alicloud/Packet which were using it) and enabled by default, it
graduated to GA in 1.14. We never needed to explicitly enable it, we
just have to make sure that it's not disabled.

See kubernetes/kubernetes#79310
rfranzke added a commit to gardener-attic/gardener-extensions that referenced this pull request Sep 20, 2019
The feature gate was already beta in 1.13 (least supported version of
Alicloud/Packet which were using it) and enabled by default, it
graduated to GA in 1.14. We never needed to explicitly enable it, we
just have to make sure that it's not disabled.

See kubernetes/kubernetes#79310
rfranzke added a commit to gardener-attic/gardener-extensions that referenced this pull request Sep 20, 2019
The feature gate was already beta in 1.13 (least supported version of
Alicloud/Packet which were using it) and enabled by default, it
graduated to GA in 1.14. We never needed to explicitly enable it, we
just have to make sure that it's not disabled.

See kubernetes/kubernetes#79310
@liggitt liggitt removed the sig/auth Categorizes an issue or PR as relevant to SIG Auth. label Feb 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/kubelet cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/storage Categorizes an issue or PR as relevant to SIG Storage. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants