第 7 章 Configuring an RHDH instance with a TLS connection in Kubernetes

Procedure

1. Enable the Kubernetes plugins in the dynamic-plugins-rhdh.yaml file:

   kind: ConfigMap
   apiVersion: v1
   metadata:
     name: dynamic-plugins-rhdh
   data:
     dynamic-plugins.yaml: |
       includes:
         - dynamic-plugins.default.yaml
       plugins:
         - package: ./dynamic-plugins/dist/backstage-plugin-kubernetes-backend-dynamic
           disabled: false 

   1

   
         - package: ./dynamic-plugins/dist/backstage-plugin-kubernetes
           disabled: false 

   2

   
           # ...

   1

   Set the value to false to enable the backstage-plugin-kubernetes-backend-dynamic plugin.

   2

   Set the value to false to enable the backstage-plugin-kubernetes plugin.

   注意

   The backstage-plugin-kubernetes plugin is currently in Technology Preview. As an alternative, you can use the ./dynamic-plugins/dist/backstage-plugin-topology-dynamic plugin, which is Generally Available (GA).

2. Set the Kubernetes cluster details and configure the catalog sync options in the app-config.yaml configuration file.

   kind: ConfigMap
   apiVersion: v1
   metadata:
     name: my-rhdh-app-config
   data:
     "app-config.yaml": |
     # ...
     catalog:
       rules:
         - allow: [Component, System, API, Resource, Location]
       providers:
         kubernetes:
           openshift:
             cluster: openshift
             processor:
               namespaceOverride: default
               defaultOwner: guests
             schedule:
               frequency:
                 seconds: 30
               timeout:
                 seconds: 5
     kubernetes:
       serviceLocatorMethod:
         type: 'multiTenant'
       clusterLocatorMethods:
         - type: 'config'
           clusters:
             - url: <target-cluster-api-server-url> 

   1

   
               name: openshift
               authProvider: 'serviceAccount'
               skipTLSVerify: false 

   2

   
               skipMetricsLookup: true
               dashboardUrl: <target-cluster-console-url> 

   3

   
               dashboardApp: openshift
               serviceAccountToken: ${K8S_SERVICE_ACCOUNT_TOKEN} 

   4

   
               caData: ${K8S_CONFIG_CA_DATA} 

   5

   
               # ...

   1

   The base URL to the Kubernetes control plane. You can run the kubectl cluster-info command to get the base URL.

   2

   Set the value of this parameter to false to enable the verification of the TLS certificate.

   3

   Optional: The link to the Kubernetes dashboard managing the ARO cluster.

   4

   Optional: Pass the service account token using a K8S_SERVICE_ACCOUNT_TOKEN environment variable that you define in your <my_product_secrets> secret.

   5

   Pass the CA data using a K8S_CONFIG_CA_DATA environment variable that you define in your <my_product_secrets> secret.

3. Save the configuration changes.

Verification

1. Run the RHDH application to import your catalog:

   kubectl -n rhdh-operator get pods -w

2. Verify that the pod log shows no errors for your configuration.
3. Go to Catalog and check the component page in the Developer Hub instance to verify the cluster connection and the presence of your created resources.