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

Tracking issue for Improving status in CAPI resources - Phase 1 #11105

Open
54 of 59 tasks
fabriziopandini opened this issue Aug 27, 2024 · 0 comments · Fixed by #11422 or #11436
Open
54 of 59 tasks

Tracking issue for Improving status in CAPI resources - Phase 1 #11105

fabriziopandini opened this issue Aug 27, 2024 · 0 comments · Fixed by #11422 or #11436
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@fabriziopandini
Copy link
Member

fabriziopandini commented Aug 27, 2024

This is a tracking issue for activities related to #10897

Enablement

Activities that are required to unblock implementation

Documentation updates

Implementation Phase1

Focus on phase 1 of the implementation, where new field are added but not yet used by controllers

Follow up / before release

Activities that could be deferred to after we get a first version of this proposal implemented

  • P0: Check initializations of the status structs to catch cases like this
  • P0: Double check deprecations notices: fields that are marked as deprecated in the proposal, utils, etc (note: some of them should be deferred to phase 2)
  • P0: Prune fields not yet implemented before release

Phase 2 activities are tracked in #11474

@k8s-ci-robot k8s-ci-robot added needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 27, 2024
@fabriziopandini fabriziopandini added kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Aug 27, 2024
@k8s-ci-robot k8s-ci-robot removed needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Aug 27, 2024
@fabriziopandini fabriziopandini changed the title [WIP] Tracking issue for Improving status in CAPI resources Tracking issue for Improving status in CAPI resources Sep 26, 2024
@fabriziopandini fabriziopandini added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Sep 26, 2024
@k8s-ci-robot k8s-ci-robot removed the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Sep 26, 2024
@k8s-ci-robot k8s-ci-robot reopened this Nov 18, 2024
@sbueringer sbueringer reopened this Nov 19, 2024
@kubernetes-sigs kubernetes-sigs deleted a comment from k8s-ci-robot Nov 19, 2024
@kubernetes-sigs kubernetes-sigs deleted a comment from k8s-ci-robot Nov 19, 2024
@fabriziopandini fabriziopandini changed the title Tracking issue for Improving status in CAPI resources Tracking issue for Improving status in CAPI resources - Phase 1 Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
4 participants