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

🌱 api: deprecate FailureMessage and FailureReason #11317

Conversation

chrischdi
Copy link
Member

What this PR does / why we need it:

Deprecates .status.failureMessage and .status.failureReason as proposed in docs/proposals/20240916-improve-status-in-CAPI-resources.md.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Part of #11105

/area api

@k8s-ci-robot k8s-ci-robot added the area/api Issues or PRs related to the APIs label Oct 22, 2024
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Oct 22, 2024
@chrischdi chrischdi force-pushed the pr-deprecate-failure-message-reason branch from 9331dcc to 124f481 Compare October 22, 2024 07:40
@chrischdi chrischdi changed the title ⚠️ api: deprecate FailureMessage and FailureReason 🌱 api: deprecate FailureMessage and FailureReason Oct 22, 2024
Copy link
Member

@sbueringer sbueringer left a comment

Choose a reason for hiding this comment

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

One nit.

I've added an additional sub-task in the proposal for the other fields. But they are more complex and might require more discussion. So I think it makes sense to only deprecate failureReason & failureMessage in this PR and handle the other fields in follow-up PR(s)

api/v1beta1/cluster_types.go Outdated Show resolved Hide resolved
@chrischdi chrischdi force-pushed the pr-deprecate-failure-message-reason branch from 124f481 to 9a7d894 Compare October 22, 2024 18:09
@sbueringer
Copy link
Member

/lgtm
/assign @fabriziopandini

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 22, 2024
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 8147135ba36b206a859c9752f06702653e778c06

@sbueringer
Copy link
Member

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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 Oct 22, 2024
@k8s-ci-robot k8s-ci-robot merged commit 76328ed into kubernetes-sigs:main Oct 22, 2024
18 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.9 milestone Oct 22, 2024
@Sunnatillo Sunnatillo mentioned this pull request Nov 6, 2024
41 tasks
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/api Issues or PRs related to the APIs cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. 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.

4 participants