Skip to content

Handle Baremetal registrymirror upgrade validation #7710

@panktishah26

Description

@panktishah26

What happened:
We do not upgrade registry mirror configuration for BareMetal provider.

What you expected to happen:
Pre-flight validation stating registry mirror fields are not mutable or with the in-place upgrade functionality for tinkerbell, these fields should be mutable.

How to reproduce it (as minimally and precisely as possible):

  1. Create a Bare metal cluster with registry mirror configuration.
  2. Upgrade with the changed registry mirror fields.
  3. Upgrade succeeds without changing registry mirror config values.

Anything else we need to know?:

Environment:

  • EKS Anywhere Release:
  • EKS Distro Release:

Metadata

Metadata

Assignees

No one assigned

    Labels

    ackIssue has been acknowledged

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions