sigs.k8s.io/cluster-api@v1.7.1/docs/book/src/developer/providers/migrations/v1.6-to-v1.7.md (about)

     1  # Cluster API v1.6 compared to v1.7
     2  
     3  This document provides an overview over relevant changes between Cluster API v1.6 and v1.7 for
     4  maintainers of providers and consumers of our Go API.
     5  
     6  ## Go version
     7  
     8  - The Go version used by Cluster API is Go 1.21.x
     9  
    10  ## Dependencies
    11  
    12  **Note**: Only the most relevant dependencies are listed, `k8s.io/` and `ginkgo`/`gomega` dependencies in Cluster API are kept in sync with the versions used by `sigs.k8s.io/controller-runtime`.
    13  - sigs.k8s.io/kind: v0.20.x => v0.22.x
    14  
    15  
    16  ## Changes by Kind
    17  
    18  ### Deprecation
    19  
    20  ### Removals
    21  
    22  - API version `v1alpha4` is now completely removed.
    23  
    24  ### API Changes
    25  
    26  ### Other
    27  
    28  * Patch helper now return error with enough error context (https://github.com/kubernetes-sigs/cluster-api/pull/9946). It is recommended to remove redundant error context on call sites if applicable.
    29  
    30  ### Suggested changes for providers
    31  
    32  * [MachinePools are now enabled by default](https://github.com/kubernetes-sigs/cluster-api/pull/10141) and the feature flag is marked as `beta` instead of `alpha`. If you are re-defining feature flags in your codebase, these values will need to be updated accordingly. If not, the following error will result:
    33  
    34      ```
    35      panic: feature gate "MachinePool" with different spec already exists: {true false BETA}
    36      ```
    37  
    38      See [this change](https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/4897/files#diff-bd8758c39c0deb35ee6c5c387594f6575580918777fbf2926f5762c7c9fce755L104) for how to update the flag.