Este contenido no está disponible en el idioma seleccionado.

Chapter 21. Configuring and integrating the RHACS plugin with Red Hat Developer Hub


By configuring and integrating the Red Hat Advanced Cluster Security for Kubernetes (RHACS) plugin with Red Hat Developer Hub (RHDH), you can view the security information for your deployments in RHDH.

Important

Integration of vulnerability findings into the RHDH is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.

21.1. Viewing security information in Red Hat Developer Hub

By configuring and integrating the Red Hat Advanced Cluster Security for Kubernetes (RHACS) plugin with Red Hat Developer Hub (RHDH), you can access vulnerability data, assess risks, and take proactive security actions without leaving the RHDH environment.

Review the upstream plugin progress and details by visiting Community plugins for Backstage.

Prerequisites

Procedure

  1. In the app-config.yaml file, add the proxy and acs stanzas by using the following content:

    # ...
    proxy:
      endpoints:
        /acs:
          target: ${ACS_API_URL}
          headers:
            authorization: Bearer ${ACS_API_KEY}
    acs:
      acsUrl: ${ACS_API_URL}
    # ...
    Copy to Clipboard Toggle word wrap
  2. To enable the RHACS plugin, perform the following steps:

    1. Navigate to the dynamic plugins configuration file in your RHDH setup.
    2. To include the RHACS plugin, add the following content to the configuration file, for example:

      # ...
      - package: "oci://ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-acs:pr_986__0.0.4!backstage-community-plugin-acs"
        disabled: false
        pluginConfig:
          dynamicPlugins:
            frontend:
              backstage-community.plugin-acs:
                entityTabs:
                  - path: /acs
                    title: Security
                    mountPoint: entity.page.acs
                mountPoints:
                  - mountPoint: entity.page.acs/cards
                    importName: EntityACSContent
                    config:
                      layout:
                        gridColumnEnd:
                          lg: span 12
                          md: span 12
                          xs: span 12
      # ...
      Copy to Clipboard Toggle word wrap
  3. To add annotations for entities in the RHDH catalog, perform the following steps:

    Note

    To display the vulnerability data, each component entity in the RHDH catalog must reference the RHACS deployments.

    The following values are associated with the entities in the RHDH catalog:

    • API
    • Component
    • Domain
    • Group
    • Location
    • Resource
    • System
    • Template
    • User
    1. Navigate to the entity configuration file for your service in your RHDH setup.
    2. Add the following annotation to the configuration file, for example:

      apiVersion: backstage.io/v1alpha1
      kind: Component
      metadata:
        name: test-service
        annotations:
          acs/deployment-name: test-deployment-1,test-deployment-2,test-deployment-3
      # ...
      Copy to Clipboard Toggle word wrap

Verification

  1. In the RHDH portal, click Catalog.
  2. Click an entity and verify that the RHACS tab appears.
  3. To view the violations and vulnerability data, click the RHACS tab.

After you configure and integrate the RHACS plugin with RHDH, you need to rebuild the Open Container Initiative (OCI) artifact. See "Rebuilding the OCI artifact" for instructions.

21.2. Rebuilding the OCI artifact

To rebuild the Open Container Initiative (OCI) artifact, update the repo-ref field in the source.json file to reference the new commit ID of the plugin repository.

Procedure

  • To rebuild the OCI artifact, update the repo-ref field in the source.json file, for example:

    Important

    You can find the source.json file in the workspaces/acs directory of the rhdh-plugin-export-overlays repository.

    {"repo":"https://github.com/backstage/community-plugins","repo-ref":"19ddb7837c6823a253c87af9524f8aef26a90b35","repo-flat":false}
    Copy to Clipboard Toggle word wrap
Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat