Backstage RHDH Plugin Configuration Guide

This comprehensive guide outlines the steps to configure, deploy, and troubleshoot the MTA plugin for Red Hat Developer Hub (RHDH).

Table of Contents

1. Cluster Access
2. MTA/Tackle Setup
3. RHDH Operator Deployment
4. Configmaps and Secrets
5. Keycloak Client Setup
6. Plugin Deployment
7. Troubleshooting

1. Get Access to Your Cluster

The first step is to log in to your cluster.

• Run the following command:

oc login --token=<your-token> --server=<your-server-url>

2. MTA / Tackle Setup Process

You need an MTA instance running in your cluster. For upstream MTA (Tackle), follow these instructions:

• Create a Tackle instance in the cluster:

kubectl apply -f https://raw.githubusercontent.com/konveyor/tackle2-operator/main/tackle-k8s.yaml

• Note: This may take a moment for the operator to spin up.
• Once the Tackle instance is running, create a Tackle Custom Resource (CR) to configure it:

cat << EOF | kubectl apply -f -
kind: Tackle
apiVersion: tackle.konveyor.io/v1alpha1
metadata:
  name: tackle
  namespace: konveyor-tackle
spec:
  feature_auth_required: true
EOF

• Alternatively, you can use the downstream MTA, with versions up to 7.2.2 supported. Version 7.3 requires an update for RHBK.

MTA Plugin Configuration

• Configure the MTA plugin URL: You will need the URL for the Tackle instance. This URL must be added to the app-config configmap (e.g., app-config-rhdh.example.yaml) under the mta key. Be sure to include the http:// or https:// prefix.
• The app-config configmap also contains the mta key, which holds configurations for MTA resources, including:
  • url: The URL of the MTA instance
  • backendPluginRoot: Root URL for the MTA backend plugin
  • version: Version of the backend plugin

View the full documentation on GitHub