Chapter 1. Installing Red Hat Edge Manager on Red Hat OpenShift Container Platform
Red Hat OpenShift Container Platform users can install Red Hat Edge Manager from the Software Catalog in the Hybrid Cloud Console. This procedure guides you through project creation, certificate configuration, and application deployment.
After deployment, you can open the Red Hat Edge Manager web UI from a dedicated route for a standalone deployment, or from the Red Hat Advanced Cluster Management console when you integrate Red Hat Edge Manager with Red Hat Advanced Cluster Management. The console integration path requires enabling the flightctl-plugin dynamic plugin in the Red Hat OpenShift Container Platform web console.
- An active Red Hat Edge Manager subscription.
- A Red Hat OpenShift Container Platform cluster version 4.19 or later.
- Cluster administrator permissions.
-
The OpenShift CLI (
oc) installed and authenticated. - For access through the Red Hat Advanced Cluster Management console, Red Hat Advanced Cluster Management is installed on the cluster and you can enable dynamic plugins in the Red Hat OpenShift Container Platform web console.
- Log into the Red Hat OpenShift Container Platform web console.
-
Navigate to Home
Projects. Click Create Project.
- Enter a name for your project in the Name field.
- Optional: Enter a display name for your project in the Display name field.
- Optional: Enter a description for your project in the Description field.
- Click Create to create your project.
-
Navigate to Ecosystem
Software Catalog. Select your project from the Project dropdown menu.
NoteIf the project does not appear in the dropdown, refresh your browser.
- Search for "Red Hat Edge Manager" and select the Red Hat Edge Manager tile.
- In the Red Hat Edge Manager side panel, click Create.
- Enter a name for your Helm release in the Release Name field.
- Select the desired version from the Chart version dropdown menu.
Before finishing the installation, you must configure the ingress certificates. In your terminal, run the following commands to extract the cluster’s Certificate Authority (CA) bundle:
$ oc get configmap default-ingress-cert \ -n openshift-config-managed \ -o jsonpath='{.data.ca-bundle\.crt}' > /tmp/ingress-ca.crt $ cat /tmp/ingress-ca.crtUnder the Configure via section, select the YAML view radio button, locate the
global.auth.caCertfield and paste the contents of/tmp/ingress-ca.crtas shown below:Example YAML configuration
global: auth: caCert: | -----BEGIN CERTIFICATE----- MIIDWzCCAkOgAwIBAgIIUUg1fwtYuLYwDQYJKoZIhvcNAQELBQAwJjEkMCIGA1UE ... [Full certificate content] ... -----END CERTIFICATE----- insecureSkipTlsVerify: falseWarningVerify the
global.auth.caCertfield is included. If it is missing, you must add it manually to allow edge devices to verify the API. Ensureglobal.auth.caCertis correctly indented. If this field is missing or malformed, managed edge devices will be unable to verify the API identity and will fail to connect.ImportantSet
global.enableMulticlusterExtensionsaccording to how you use Red Hat Edge Manager on this cluster:-
Standalone Red Hat Edge Manager: Use the Red Hat Edge Manager UI through a dedicated OpenShift route. If Red Hat Advanced Cluster Management is also installed but you do not want Edge management inside the Red Hat Advanced Cluster Management console, set
global.enableMulticlusterExtensionsto"false". -
Red Hat Advanced Cluster Management-integrated Red Hat Edge Manager: Use Edge capabilities from Fleet Management. Set
global.enableMulticlusterExtensionstotrueorauto(as supported by your chart version). After the Helm release is deployed, enable theflightctl-plugindynamic plugin in the Red Hat OpenShift Container Platform console. For the steps, see Accessing Red Hat Edge Manager from the Red Hat Advanced Cluster Management console.
NoteThe OpenShift Software Catalog used here is where you install the Red Hat Edge Manager service. It is not the same as the in-product Software Catalog in the Red Hat Edge Manager web console, which is used to distribute operating system images and applications to edge devices.
NoteTo control Kubernetes Secret Provider access to cluster secrets:
-
Grant access per namespace (Recommended): Use a
RoleandRoleBindingto grant theflightctl-workerservice account access to specific namespaces. This is the recommended method to ensure limited permission access for the worker. For details, see the Managing devices topic on Secrets from a Kubernetes cluster. -
Allow cluster-wide access: Set
global.worker.clusterLevelSecretAccesstotruein the YAML configuration. Use this option only if the worker requires access to secrets across the entire cluster.
-
Standalone Red Hat Edge Manager: Use the Red Hat Edge Manager UI through a dedicated OpenShift route. If Red Hat Advanced Cluster Management is also installed but you do not want Edge management inside the Red Hat Advanced Cluster Management console, set
Click Create to deploy Red Hat Edge Manager.
NoteIf you upgrade the Red Hat Edge Manager Helm chart through the Red Hat OpenShift Container Platform web console and change the chart version, the upgrade form shows the new chart version’s default values only; it does not include custom values from your installed release. To preserve configuration when upgrading, see Additional resources.
1.1. Accessing the Red Hat Edge Manager web UI through a route (standalone) Copy linkLink copied to clipboard!
Complete the following steps when you set global.enableMulticlusterExtensions to "false" or otherwise use the dedicated Red Hat Edge Manager route as your primary UI.
After the pods are running, obtain the external URL to access the Red Hat Edge Manager dashboard. In your terminal, run the following command to retrieve the host address:
$ oc get route flightctl-ui -n <project_name> -o jsonpath='{.spec.host}'- Copy the returned URL and paste it into a web browser.
- Log in using your administrator credentials.
1.2. Accessing Red Hat Edge Manager from the Red Hat Advanced Cluster Management console Copy linkLink copied to clipboard!
Complete the following steps when you set global.enableMulticlusterExtensions to true or auto so that Edge management appears in Fleet Management. The Red Hat OpenShift Container Platform web console loads the Red Hat Edge Manager web UI through the flightctl-plugin dynamic plugin. Enabling that plugin after installation is required even when the Helm chart is configured for multicluster extensions.
- The Red Hat Edge Manager Helm release is deployed and pods are running.
You can log in to the Red Hat OpenShift Container Platform web console with a user who is allowed to manage dynamic plugins (typically
cluster-admin).- Switch to the Administrator perspective. On recent Red Hat OpenShift Container Platform versions, the console might label this perspective Core Platform instead.
-
Navigate to Administration
Dynamic plugins. -
Locate
flightctl-pluginin the list. The same entry might show a different display name (for example, Flight Control). - Click Enable (or use the equivalent control) to turn the plugin on.
- Wait until the console reports that the plugin is loaded. Loading can take a short time.
- If the console prompts you to refresh, reload the page. Otherwise, refresh the browser window so the updated navigation appears.
- Switch to Fleet Management.
- Open the Edge Management entry to use the Red Hat Edge Manager web UI.
If Edge does not appear in Fleet Management, confirm that global.enableMulticlusterExtensions is set to true or auto in your Helm values, that the Helm upgrade has finished successfully, that flightctl-plugin is enabled on Administration