-
Notifications
You must be signed in to change notification settings - Fork 40k
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
[1.16] Stop serving deprecated beta workload APIs #70672
Merged
k8s-ci-robot
merged 2 commits into
kubernetes:master
from
liggitt:stop-serving-beta-apps
Jun 22, 2019
Merged
[1.16] Stop serving deprecated beta workload APIs #70672
k8s-ci-robot
merged 2 commits into
kubernetes:master
from
liggitt:stop-serving-beta-apps
Jun 22, 2019
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
size/XXL
Denotes a PR that changes 1000+ lines, ignoring generated files.
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.
needs-priority
Indicates a PR lacks a `priority/foo` label and requires one.
area/apiserver
area/kubectl
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
sig/apps
Categorizes an issue or PR as relevant to SIG Apps.
sig/autoscaling
Categorizes an issue or PR as relevant to SIG Autoscaling.
and removed
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
labels
Nov 5, 2018
k8s-ci-robot
added
sig/cluster-lifecycle
Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
sig/gcp
sig/testing
Categorizes an issue or PR as relevant to SIG Testing.
labels
Nov 5, 2018
liggitt
added
sig/network
Categorizes an issue or PR as relevant to SIG Network.
sig/auth
Categorizes an issue or PR as relevant to SIG Auth.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
and removed
area/apiserver
area/kubectl
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
sig/autoscaling
Categorizes an issue or PR as relevant to SIG Autoscaling.
labels
Nov 5, 2018
adelina-t
added a commit
to e2e-win/flannel-kubernetes
that referenced
this pull request
Jun 24, 2019
Update flannel manifest endpoints for DaemonSet & PodSecurityPolicy. kubernetes/kubernetes#70672
adelina-t
added a commit
to e2e-win/flannel-kubernetes
that referenced
this pull request
Jun 24, 2019
Update flannel manifest API endpoints for PodSecurityPolicy and DaemonSet. Note: kubernetes/kubernetes#70672
This was referenced Jun 24, 2019
4 tasks
This was referenced Jun 30, 2019
3 tasks
bpietraga
added a commit
to bpietraga/mattermost-helm
that referenced
this pull request
Nov 27, 2019
Based on official PR: kubernetes/kubernetes#70672 `Ingress resources will no longer be served from extensions/v1beta1 in v1.20. Migrate use to the networking.k8s.io/v1beta1 API, available since v1.14. Existing persisted data can be retrieved via the networking.k8s.io/v1beta1 API.`
Merged
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/apiserver
area/test
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
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-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
release-note-action-required
Denotes a PR that introduces potentially breaking changes that require user action.
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
sig/apps
Categorizes an issue or PR as relevant to SIG Apps.
sig/network
Categorizes an issue or PR as relevant to SIG Network.
sig/testing
Categorizes an issue or PR as relevant to SIG Testing.
size/XL
Denotes a PR that changes 500-999 lines, ignoring generated files.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):xref #43214
Does this PR introduce a user-facing change?: