-
Notifications
You must be signed in to change notification settings - Fork 15k
mark node phase as deprecated #549
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
Conversation
I'm not sure on what the best wording for this should be, but `Node Phase` is no longer populated, and so the docs should say so. @Random-Liu on slack/#sig-node told me that they believed node phase was unused. cc @dawnchen
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed, please reply here (e.g.
|
signed CLA |
CLAs look good, thanks! |
I'm sure the @dchen1107 and @bgrant0607 should have more ideas. |
@dchen1107 Did we change how/whether node phase is set? That would be a breaking behavioral change for the v1 API. If we do plan to deprecate it, it would need to be documented in the API first: |
@dchen1107 @Random-Liu Any update on this? |
@pwittrock I'm not sure whether we really want to deprecate |
@dchen1107 Is |
We stopped populate / set node phase a while back. This won't be breaking change for v1 API since no one couldn't depend on it at all. But we still should change v1API code first to make such announcement. Let me send a pr changing v1API shortly. |
@mwhooker This field will be deprecated in kubernetes/kubernetes#30005 for 1.4. Lets merge it when that change is live. |
neato! thanks |
Automatic merge from submit-queue Marked NodePhase deprecated. cc/ @lavalamp Even Kubernetes stops set NodePhase for a while, the user might patch NodeStatus with NodePhase. Marked the field deprecated and documented first. xref: kubernetes/website#549 <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30005) <!-- Reviewable:end -->
This docs change is slated for the 1.4 release. We're trying to have all 1.4 docs PRs target the release-1.4 branch. Can you have this PR target release-1.4? A rebase would probably also be a good idea. |
Bumps [actions/checkout](https://github.com/actions/checkout) from 2 to 3. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v2...v3) --- updated-dependencies: - dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
I'm not sure on what the best wording for this should be, but
Node Phase
is no longer populated, and so the docs should say so.@Random-Liu on slack/#sig-node told me that they believed node phase was unused.
cc @dawnchen
This change is