are hence enabled by default. This will be fixed in a future release.
[#38593](https://github.com/kubernetes/kubernetes/issues/38593)
* Federation control plane can be upgraded by updating the image
fields in the `Deployment` specs of the control plane components.
However, federation control plane upgrades were not tested in this
release [38537](https://github.com/kubernetes/kubernetes/issues/38537)

## Notable Changes to Existing Behavior

## Changelog since v1.4.1

### Other notable changes

* Fix base image pinning during upgrades via cluster/gce/upgrade.sh ([#33147](https://github.com/kubernetes/kubernetes/pull/33147), [@vishh](https://github.com/vishh))
* Fix upgrade.sh image setup ([#34468](https://github.com/kubernetes/kubernetes/pull/34468), [@mtaufen](https://github.com/mtaufen))

    /** The key of the message: Unknown version for upgrade. */
    public static final String ERRORS_unknown_version_for_upgrade = "{errors.unknown_version_for_upgrade}";

    /** The key of the message: Failed to upgrade from {0}. */
    public static final String ERRORS_failed_to_upgrade_from = "{errors.failed_to_upgrade_from}";

    /** The key of the message: Home Directory */
    public static final String LABELS_HOME_DIRECTORY = "{labels.homeDirectory}";

    /** The key of the message: Upgrade */
    public static final String LABELS_upgrade_title_configuration = "{labels.upgrade_title_configuration}";

    /** The key of the message: Data Migration */