Tracking issue for Improving status in CAPI resources - Follow up from phase 1

[fabriziopandini]

This is a tracking issue for activities related to #10897
Phase 1 activities are tracked into #11105

Follow up from phase 1 (1.10)

• Fine tuning of godocs for API types (make them kubectl explain compliant)
  - rif 📖 Proposal: Improving status in CAPI resources #10897 (comment)
  - it seems it is address in latest version of controller-tools (see comment below)
• Extending CC to allow the definition of AvailabilityGates & ReadinessGates (and Cluster topology) ✨ Add Availability and ReadinessGates to ClusterClass #11868
  • rif 📖 Proposal: Improving status in CAPI resources #10897 (comment)
  • rif ✨ Add v1beta2 structs to object status #11234 (comment)
• Consider if to allow users to add arbitrary ReadinessGates to KCP machines ✨ Add Availability and ReadinessGates to ClusterClass #11868
• Rename test types to align to API types (v1Beta2 in the middle) 🌱 Rename v1beta2 test types #11832
• ExtensionConfig 🌱 Add v1beta2 conditions to ExtensionConfig #11848
• DockerCluster and DockerMachine controllers
  • 🌱 Add v1beta2 conditions to DevMachines with InMemory backend #11901
  • 🌱 Add v1beta2 conditions to DevMachine and DevCluster with Docker backend #11923
• Add support for negative polarity conditions to ReadinessGates and AvailabilityGates 🌱 Allow readiness and availability gates with negative polarity #11918
• IPAddressClaim: 🌱 Add v1beta2 conditions to IPAddressClaim #11971

Dropped

• Check if NodeNetworkUnavailable must be added to MachineNodeHealthyCondition
  • Looks like NodeNetworkUnavailable is a left over of in tree gcp provider
• Allow customisation of remote-conditions-grace-period at cluster level
  • rif 📖 Proposal: Improving status in CAPI resources #10897 (comment)
• InMemoryCluster and InMemoryMachine controllers
  • It is being merged in CAPD(ev)

[sbueringer]

Assigned to v1.10 for now to keep an eye on it. I think it's not clear yet in which release this will land.

[fabriziopandini]

WRT to make new API fields kubectl explain compliant (rif #10897 (comment))

New fields introduced by the improve status proposal doesn't have fancy formatting anymore; never the less, it seems that this issue has been addressed in latest version of controller tools:

field with list using *

  template      <string>
    template defines the template to use for generating the name of the
    ControlPlane object.
    If not defined, it will fallback to `{{ .cluster.name }}-{{ .random }}`.
    If the templated string exceeds 63 characters, it will be trimmed to 58
    characters and will
    get concatenated with a random suffix of length 5.
    The templating mechanism provides the following arguments:
    * `.cluster.name`: The name of the cluster object.
    * `.random`: A random alphanumeric string, without vowels, of length 5.

field with list using -

  nodeStartupTimeout    <string>
    nodeStartupTimeout allows to set the maximum time for MachineHealthCheck
    to consider a Machine unhealthy if a corresponding Node isn't associated
    through a `Spec.ProviderID` field.

    The duration set in this field is compared to the greatest of:
    - Cluster's infrastructure ready condition timestamp (if and when available)
    - Control Plane's initialized condition timestamp (if and when available)
    - Machine's infrastructure ready condition timestamp (if and when available)
    - Machine's metadata creation timestamp

    Defaults to 10 minutes.
    If you wish to disable this feature, set the value explicitly to 0.