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.

Sign up for GitHub

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

Jump to bottom

Improve status.Ready Fields in the contract #10707

Closed
Tracked by #10852
fabriziopandini opened this issue May 30, 2024 · 3 comments
Closed
Tracked by #10852

Improve status.Ready Fields in the contract #10707

fabriziopandini opened this issue May 30, 2024 · 3 comments
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@fabriziopandini
Copy link
Member

What would you like to be added (User Story)?

As a user I would like a clean and simple API

Detailed Description

As per 29th of May office hour discussion, status.Ready might be a little be confusing for at least two reasons:

  • status.Ready is relevant in the provisioning workflow, but not after
  • status.Ready is now confused with conditions.Ready

When designing the next API version we should consider if and how to remove the confusion about status.Ready

Anything else you would like to add?

see https://kubernetes.slack.com/archives/C8TSNPY4T/p1716892079243969

Label(s) to be applied

/kind api-change
@k8s-ci-robot k8s-ci-robot added kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API needs-priority Indicates an issue lacks a `priority/foo` label and requires one. labels May 30, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label May 30, 2024
@fabriziopandini fabriziopandini added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Jun 5, 2024
@k8s-ci-robot k8s-ci-robot removed the needs-priority Indicates an issue lacks a `priority/foo` label and requires one. label Jun 5, 2024
@sbueringer sbueringer mentioned this issue Jul 10, 2024
Open
53 tasks
@sbueringer
Copy link
Member

Will be addressed via #10897, pleaes take a look at the proposal for more details.
/close

@k8s-ci-robot
Copy link
Contributor

@sbueringer: Closing this issue.

In response to this:

Will be addressed via #10897, pleaes take a look at the proposal for more details.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sbueringer @fabriziopandini @k8s-ci-robot