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

Tracking issue for Improving status in CAPI resources #11105

Open
46 of 96 tasks
fabriziopandini opened this issue Aug 27, 2024 · 1 comment
Open
46 of 96 tasks

Tracking issue for Improving status in CAPI resources #11105

fabriziopandini opened this issue Aug 27, 2024 · 1 comment
Assignees
@chrischdi @sbueringer @fabriziopandini
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 •
edited by sbueringer
Loading

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

Implementation Phase2

Initial notes for phase 2 of the implementation, where new field are added but not yet used by controllers

  • ...
  • API modeling
  • Change contracts
    • ...
  • Use new fields
    • MachineHealthCheck controller
      • Change test for ControlPlaneInitializedCondition in reconcile
      • Get MachineHealthCheckSucceededCondition in patchUnhealthyTargets
      • Drop failureReson/failureMessage test from needsRemediation
      • Change test for ControlPlaneInitializedCondition, InfrastructureReadyCondition in needsRemediation (few places)
    • KCP controller
      • Change test for MachineEtcdMemberHealthyCondition in canSafelyRemoveEtcdMember + add a test for ClusterHealthy if not already there
      • We should use the Initialized condition instead of the Available condition to calculate remoteConditionsGracePeriod
  • Condition utils
    • Rename packages for condition utils (conditions-->deprecated conditions, v1beta2conditions --> conditions)
  • Clusterctl
    • clusterctl describe (drop v1beta2 flag, introduce deprecated flag, switch default behaviour in the implementation)

Implementation Phase3

  • ...

Backlog / unprioritized

  • Scale testing with CAPD (check for condition flakiness)
@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 mentioned this issue Aug 27, 2024
Merged
@sbueringer
Copy link
Member

Feel free to assign me to "Improve Cluster Cache Tracker to allow tracking of connection problems"

@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 mentioned this issue Sep 9, 2024
Merged
This was referenced Sep 17, 2024
Merged
Merged
@fabriziopandini fabriziopandini mentioned this issue Sep 26, 2024
Merged
@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
@fabriziopandini fabriziopandini mentioned this issue Sep 27, 2024
Merged
This was referenced Oct 8, 2024
Merged
Open
@chrischdi chrischdi mentioned this issue Oct 9, 2024
Merged
@sbueringer sbueringer mentioned this issue Oct 14, 2024
Merged
@chrischdi chrischdi mentioned this issue Oct 14, 2024
Merged
@fabriziopandini fabriziopandini mentioned this issue Oct 15, 2024
Merged
@sbueringer sbueringer mentioned this issue Oct 15, 2024
Merged
@fabriziopandini fabriziopandini mentioned this issue Oct 16, 2024
Merged
@chrischdi chrischdi mentioned this issue Oct 17, 2024
Merged
@fabriziopandini fabriziopandini mentioned this issue Oct 17, 2024
Merged
@sbueringer sbueringer mentioned this issue Oct 18, 2024
Merged
@chrischdi chrischdi mentioned this issue Oct 22, 2024
Merged
@fabriziopandini fabriziopandini mentioned this issue Oct 22, 2024
Merged
@chrischdi chrischdi mentioned this issue Oct 25, 2024
Merged
@fabriziopandini fabriziopandini mentioned this issue Oct 25, 2024
Merged
@sbueringer sbueringer mentioned this issue Oct 25, 2024
Merged
This was referenced Oct 28, 2024
Merged
Merged
This was referenced Nov 5, 2024
Merged
Merged
@fabriziopandini fabriziopandini mentioned this issue Nov 5, 2024
Merged
@sbueringer sbueringer mentioned this issue Nov 6, 2024
Open
@fabriziopandini fabriziopandini mentioned this issue Nov 6, 2024
Merged
@sbueringer sbueringer mentioned this issue Nov 7, 2024
Merged
@fabriziopandini fabriziopandini mentioned this issue Nov 8, 2024
Merged
This was referenced Nov 8, 2024
Merged
Draft
Open
Merged
Open
Merged
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chrischdi chrischdi

@sbueringer sbueringer

@fabriziopandini fabriziopandini

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
Milestone
No milestone
Development

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