add some more deprecation warnings to cluster #49148
Conversation
k8s-ci-robot
added
sig/cluster-lifecycle
mikedanese
force-pushed
the
deprecate-cluster
branch
from
bc407a4 to
428de6b
Compare
|
|
||
| !!! DEPRECATION NOTICE !!! | ||
|
|
||
| The '${provider}' kube-up provider is deprecated and will be removed in a future |
There was a problem hiding this comment.
Is there an issue or announcement we can link to here to provide more context about the deprecation? Also, if someone sees this message and immediately panics and wants to convince us not to remove this support, how should they proceed? A little clarity up front will help us organize any support pings we get in the future.
There was a problem hiding this comment.
What @pipejakob said
Also we could state the timeline up front here (removal in v1.9?)
There was a problem hiding this comment.
@luxas @pipejakob Done. GCE is going to be a PITA to remove and it's currently unstaffed so I'm leaving it out of the list.
There was a problem hiding this comment.
@mikedanese sounds reasonable to defer that.
k8s-github-robot
added
size/S
luxas
added
release-note-action-required
mikedanese
force-pushed
the
deprecate-cluster
branch
from
428de6b to
89bf771
Compare
k8s-github-robot
added
the
approved
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: luxas, mikedanese Associated issue: 49213 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
|
Automatic merge from submit-queue (batch tested with PRs 48377, 48940, 49144, 49062, 49148) |
Part of #49213
@kubernetes/sig-cluster-lifecycle-misc