このコンテンツは選択した言語では利用できません。
Installing Red Hat Edge Manager on Red Hat OpenShift Container Platform
Installing Red Hat Edge Manager on OpenShift Container Platform
Abstract
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.
Prerequisites
- An active Red Hat Edge Manager subscription.
- An Red Hat OpenShift Container Platform cluster version 4.19 or later.
- Cluster administrator permissions.
-
The OpenShift CLI (
oc) installed and authenticated.
Procedure
- Log into the Red Hat OpenShift Container Platform web console.
In your terminal, run the following command to create a project for the Red Hat Edge Manager application services:
oc new-project <project_name>
$ oc new-project <project_name>Copy to Clipboard Copied! Toggle word wrap Toggle overflow - In the Red Hat OpenShift Container Platform web console, 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.
- In the Release name field, enter the name of your project.
- 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.crt$ oc get configmap default-ingress-cert \ -n openshift-config-managed \ -o jsonpath='{.data.ca-bundle\.crt}' > /tmp/ingress-ca.crt $ cat /tmp/ingress-ca.crtCopy to Clipboard Copied! Toggle word wrap Toggle overflow Under 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
Copy to Clipboard Copied! Toggle word wrap Toggle overflow WarningVerify 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.NoteIf Advanced Cluster Management (ACM) is present in your environment but you are using Red Hat Edge Manager as a standalone feature, set the
global.enableMulticlusterExtensionsparameter to"false".- Click Create to deploy Red Hat Edge Manager.
Verification: Retrieving the User Interface URL
Once 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}'$ oc get route flightctl-ui -n <project_name> -o jsonpath='{.spec.host}'Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Copy the returned URL and paste it into a web browser.
- Log in using your administrator credentials.
Chapter 2. Authenticating Red Hat Edge Manager on Red Hat OpenShift Container Platform リンクのコピーリンクがクリップボードにコピーされました!
Users can enable secure access to Red Hat Edge Manager by integrating their existing OpenShift identity provider. This guide walks you through labeling your environment and assigning the specific roles required for your team to manage devices, fleets, and organizations.
- Namespace-to-Organization Mapping: Red Hat Edge Manager uses a 1:1 mapping between OpenShift namespaces and Organizations.
-
Automatic Discovery: The act of labeling a namespace with
io.flightctl/instance=<helm_release-name>triggers the automatic discovery and initialization of that namespace as a Red Hat Edge Manager Organization. - Multi-Tenancy: You are not limited to a single organization. You can create and manage multiple isolated organizations within a single cluster by applying the same management label to different namespaces.
- Identity: Each labeled namespace is treated as a distinct organization, allowing you to segregate users, devices, and configurations across your environment.
Prerequisites
- Red Hat Edge Manager is deployed on Red Hat OpenShift Container Platform via the Software Catalog.
-
Red Hat OpenShift Container Platform users are created via an identity provider (e.g.
htpasswdor LDAP). -
You have
cluster-adminaccess to configureRoleBindings.
Procedure
- In the Red Hat OpenShift Container Platform web console, navigate to Helm → Releases and record the Helm release name. This value is required for labeling the namespace and configuring user access.
In your terminal, run the following command to label the namespace:
oc label namespace <namespace> io.flightctl/instance=<helm_release_name>
$ oc label namespace <namespace> io.flightctl/instance=<helm_release_name>Copy to Clipboard Copied! Toggle word wrap Toggle overflow ImportantThe label value must match the Helm release name, not the namespace name.
To verify which namespaces are associated with the Helm release name, run the following command:
oc get namespaces -l io.flightctl/instance=<helm_release_name>
$ oc get namespaces -l io.flightctl/instance=<helm_release_name>Copy to Clipboard Copied! Toggle word wrap Toggle overflow
2.1. Grant user access リンクのコピーリンクがクリップボードにコピーされました!
Accessing Red Hat Edge Manager resources requires a minimum of two roles: the mandatory view role for organization discovery, plus at least one functional role (e.g., flightctl-admin).
| Role | Purpose |
|---|---|
|
| Required for organization discovery. |
|
| Full access to Red Hat Edge Manager resources. |
|
| CRUD permissions for devices, fleets, resourcesyncs, and repositories. |
|
| Read-only access. |
Procedure
To grant the
viewrole for organization discovery:oc adm policy add-role-to-user view <user_name> -n <namespace>
$ oc adm policy add-role-to-user view <user_name> -n <namespace>Copy to Clipboard Copied! Toggle word wrap Toggle overflow To grant Red Hat Edge Manager administrative permissions:
oc adm policy add-role-to-user flightctl-admin-<helm_release_name> <user_name> -n <namespace>
$ oc adm policy add-role-to-user flightctl-admin-<helm_release_name> <user_name> -n <namespace>Copy to Clipboard Copied! Toggle word wrap Toggle overflow To grant permissions for CRUD operations on Red Hat Edge Manager resources:
oc adm policy add-role-to-user flightctl-operator-<helm_release_name> <user_name> -n <namespace>
$ oc adm policy add-role-to-user flightctl-operator-<helm_release_name> <user_name> -n <namespace>Copy to Clipboard Copied! Toggle word wrap Toggle overflow To grant Red Hat Edge Manager read-only access:
oc adm policy add-role-to-user flightctl-viewer-<helm_release_name> <user_name> -n <namespace>
$ oc adm policy add-role-to-user flightctl-viewer-<helm_release_name> <user_name> -n <namespace>Copy to Clipboard Copied! Toggle word wrap Toggle overflow
A User not found warning is expected if the user has not yet logged in. The role binding will activate automatically upon their first authentication.
2.2. User login リンクのコピーリンクがクリップボードにコピーされました!
You can authenticate with Red Hat Edge Manager using either the flightctl CLI or the UI.
2.2.1. Log in with the CLI リンクのコピーリンクがクリップボードにコピーされました!
Procedure
Log in to OpenShift:
oc login
$ oc loginCopy to Clipboard Copied! Toggle word wrap Toggle overflow Log in to Red Hat Edge Manager using the OpenShift token:
flightctl login https://api.flightctl.apps.example.com -k --token=$(oc whoami -t)
$ flightctl login https://api.flightctl.apps.example.com -k --token=$(oc whoami -t)Copy to Clipboard Copied! Toggle word wrap Toggle overflow Example output
Auto-selected organization: <uuid> flightctl Login successful.
Auto-selected organization: <uuid> flightctl Login successful.Copy to Clipboard Copied! Toggle word wrap Toggle overflow
2.2.2. Log in with the UI リンクのコピーリンクがクリップボードにコピーされました!
Procedure
- Navigate to the Red Hat Edge Manager UI.
- Click Login with OpenShift.
- Authenticate using your OpenShift credentials.
Upon successful authentication, the browser redirects to the Red Hat Edge Manager dashboard.
2.3. Verification リンクのコピーリンクがクリップボードにコピーされました!
Verify your access and configuration by running the following commands:
Procedure
Check the current organization:
flightctl config current-organization
$ flightctl config current-organizationCopy to Clipboard Copied! Toggle word wrap Toggle overflow List available organizations:
flightctl get organizations
$ flightctl get organizationsCopy to Clipboard Copied! Toggle word wrap Toggle overflow Test access to resources:
flightctl get devices flightctl get fleets
$ flightctl get devices $ flightctl get fleetsCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Chapter 3. Upgrading a Helm release chart リンクのコピーリンクがクリップボードにコピーされました!
Users on Red Hat OpenShift Container Platform can upgrade a Helm release by either selecting a new chart version (if available) or manually updating the YAML configuration values.
Prerequisites
- Ensure you are logged into the OpenShift console with a user account that has permission to modify resources in your specific project.
- Confirm you have the correct Project (namespace) selected in the console, as Helm releases are grouped by project.
- Ensure the application is in a stable state and that you have documented any critical configuration values currently in use.
Procedure
- In the OpenShift console, locate the navigation menu on the left side of the screen.
- Go to the Helm section and select Releases.
- Find your release in the list.
- Click the Kebab menu (three vertical dots) on the far right of the row and select Upgrade.
Configure your upgrade in the Upgrade Helm Release page:
- To change the version: Select a new version from the Chart Version dropdown menu if an update is available.
- To change settings: Manually edit the configuration in the YAML editor (Values) to update specific parameters.
- Click Upgrade to finalize and deploy your changes.
Once you click Upgrade, OpenShift will trigger a new revision. You can watch the Status column in the Helm Releases list change to "Pending" and then back to "Deployed" once the update is successful.