ERE: Will setting air gap registry affect existing K8s clusters?

[raymondyan]

Hello all. Just wanted to ask if anyone has already tested the following scenario within Ezmeral Runtime.

- At this point, it is not yet configured the private image registry on the Air gap page in the ERE web UI.
- Currently, one Kubernetes cluster has been created on ERE.

The above is the current status of the cluster.

Question:
Will setting the Airgap image registry to "marketplace.us1.greenlake-hpe.com/ezmeral/5.6.x"(or any other private registry) affect the existing Kubernetes cluster?

[mallik1 · Accepted solution]

HI raymondyan,

If you will be using an air-gap configuration for Kubernetes objects, then you must configure air-gap settings before adding any Kubernetes hosts.

Apply all air-gap settings with care. These settings do not propagate if updated after Kubernetes hosts have been installed unless one of the following occurs:

• The Kubernetes host is rebooted.
• The version of Kubernetes running on a host is upgraded.

Any Kubernetes hosts in a ready state that are not part of a Kubernetes cluster must be restarted for the changes to be applied.

Addionally , Changing an existing HPE Ezmeral Runtime Enterprise configuration from a non-airgapped environment to an air-gapped environment forces a reinstall of Kubernetes clusters.

If you are changing an existing HPE Ezmeral Runtime Enterprise configuration from a non-airgapped environment to an air-gapped environment, contact Hewlett Packard Enterprise support for assistance before you begin the transition. Several manual steps must be performed to transition to an air-gapped environment.

Thanks,

Sabyasachi Mallik