Red Hat Summit Red Hat Summit지원콘솔개발자평가판 시작연락처

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 1. Red Hat Edge Manager architecture

Red Hat Edge Manager is designed for scalability and resilience, leveraging an autonomous Red Hat Edge Manager agent to manage the operating system and workloads on each device. By offloading management logic to the edge, this architecture ensures reliable deployment and monitoring across extensive fleets. The agent maintains operational integrity locally and reports status to the Red Hat Edge Manager service as connectivity allows, enabling consistent management even in limited or intermittent network environments.

Red Hat Edge Manager supports image-based operating systems. You can include the Red Hat Edge Manager agent and the agent configuration in the image that is distributed to the devices.

Image-based operating systems allow the agent to initiate a transactional update of the image and to roll back to the previous version in case of an update error.

Red Hat Edge Manager architecture has the following main features:

  • Agent: A lightweight process on the device that autonomously polls the service for updates, implements the desired state, and manages local workloads even during network outages.

  • Service: The central control plane responsible for managing device inventory and coordinating fleet-wide configurations. To support these operations, the service includes:

    • API server: The secure gateway that handles all communication between the service, administrative tools, and the distributed agents.
    • Database: The persistent storage layer that holds the current device registry, enrollment information, and the target state definitions for the fleet.
  • Image-based operating system: An immutable Linux distribution using bootc. This enables transactional, versioned updates that can be safely rolled back, ensuring maximum reliability for edge deployments.
  • Device: An individual hardware unit or virtual machine running the agent. It maintains local state awareness, independently applying configurations and reporting its unique health metrics back to the service.
  • Device fleet: A logical grouping of devices managed as a single entity. Fleets allow you to roll out updates and policies to thousands of devices simultaneously with granular visibility.

1.1. Red Hat Edge Manager agent and service
링크 복사

The Red Hat Edge Manager agent is a process running on each managed device that periodically communicates with the Red Hat Edge Manager service.

The Red Hat Edge Manager agent is responsible for the following tasks:

  • Enrolling its device into the service.
  • Periodically checking with the service for changes in the device specification, such as changes to the operating system, configuration, and applications.
  • Applying any updates independently from the service.
  • Reporting status of the device and the applications

The Red Hat Edge Manager service acts as the central hub for your edge operations, functioning as a reliable bridge between your core systems and your distributed devices. It manages the entire life of a device from the moment it’s securely connected to the network to the ongoing tracking of its health and activity across the fleet.

The service communicates with a database that stores the device inventory and the target device configuration. When communicating with the service, the agent polls the service for changes in the configuration. If the agent detects that the current configuration deviates from the target configuration, the agent attempts to apply the changes to the device.

When the agent receives a new target configuration from the service, the agent does the following tasks:

  1. Stage Resources: To ensure resilience against network failure during the update, the agent pre-downloads all required assets—including the operating system image and application container images—directly to local storage.
  2. Update Operating System: The agent delegates the operating system update to bootc, ensuring a transactional image-based transition.
  3. Apply Configuration: The agent updates the local file system by overlaying configuration files provided by the service.
  4. Finalize Environment: If required by the update, the agent triggers a system reboot. If no reboot is necessary, it signals the relevant system services and applications to reload their configurations.
  5. Update Workloads: The agent synchronizes and updates applications running on Podman or MicroShift.

If the update fails or the system does not return online after rebooting, the agent automatically rolls back to the previous operating system image and configuration.

Note

You can maintain fleet definitions in Git. Red Hat Edge Manager periodically syncs with the fleet definitions in the database.

1.2. Red Hat Edge Manager API server
링크 복사

The API server acts as the central communication hub, exposing secure endpoints that allow both users and agents to interact with the Red Hat Edge Manager service.

The API server exposes the following endpoints:

User-facing API endpoint
Users can connect to the user-facing API endpoint from the CLI or the web console. Users must authenticate with the configured external authentication service to obtain a JSON Web Token (JWT) to make HTTPS requests.
Agent-facing API endpoint
Agents connect to the agent-facing endpoint, which is mTLS-protected. The service authenticates devices using the X.509 client certificates.

The Red Hat Edge Manager service also communicates with various external systems to authenticate and authorize users, get mTLS certificates signed, or query configuration for managed devices.

Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2026 Red Hat맨 위로 이동