Browse & Search Migration

To be able to start migrating the Browse & Search, you need to have migrated all Self-Service instances.

Make the Platform-UI to use the Topic-Browse instead of the Stream-Browse

Objective

Using Topic-Browse instead of Stream-Browse to browse and search messages

Execution

API Gateway

In the api-gateway section, change the gateway.endpoints configuration to forward to Topic-Browse and not to Stream-Browse as shown below:

values.yaml

axual-governance:
  api-gateway:

    config:

      gateway:
        endpoints:

          topicBrowse:
            enabled: true
            url: "http://[topic-browse-service-name]"

          streamBrowseLegacy:
            enabled: false
#            url: "https://[stream-browse-service-name]:[stream-browse-service-port]"

Platform UI

In the platform-ui section, change the FeatureFlags configuration to enable Topic-Browse and disable Stream-Browse as shown below:

values.yaml

axual-governance:
  platform-ui:
    # Window.ENV Configuration
    config:

      # Feature Flags

      # To enable Browse&Search with Stream-Browse
      streamBrowseEnabled: false
      streamBrowseUrl: 'https://[mgmt-ingress-host]/api/browse'

      # To enable Browse&Search with Topic-Browse
      topicBrowseEnabled: true
      topicBrowseUrl: 'https://[mgmt-ingress-host]/api/stream_configs'

Once the api-gateway and the platform-ui section have been updated, upgrade the Governance application.

Verification

In this step, we are going to verify that the new Management stack can perform the same operation as the old Management stack without interacting with the Stream-Browse.

Open a browse and access https:[mgmt-ingress-host]/login/[your-realm]

Verify that your user can still browse a topic it was able to browse before the migration.

If all checks are successful, you can proceed to the next steps.