The DevOps component in the compute cluster specifies the platform access address

Description

The platform supports external network access, which means that in some scenarios, the global cluster and the compute cluster cannot communicate using internal network addresses. In this case, the external network access address of the cluster can be configured to connect to the global cluster using a public network address.

For some DevOps components in the compute cluster, manual configuration is required to ensure that the DevOps components in the compute cluster and the global cluster can communicate with each other.

Procedure

The user configuration varies slightly depending on the usage scenario.

Scenario 1: Deploy Jenkins in the compute clusters

If you have previously used the feature to create Jenkins in the platform compute cluster and need to use the public network address to access the global cluster using the Jenkins component in the compute cluster, you can solve it by following these steps:

1. In the left navigation bar, click DevOps Toolchain > Integrations.

2. Click the Jenkins tool card.

3. Click the Instance Name on the right side of the Jenkins instance, and then click Actions > Update deploy instance on the deployment details page.

4. Update the Jenkins instance parameters to trigger the Jenkins instance to redeploy.

   Tip: You can slightly adjust the resource allocation request or limit value.

Scenario 2: Automatically triggering pipelines with code repositories or image repositories deployed in compute clusters

If you have deployed a code repository or image repository in the compute cluster and meet the following pipeline usage scenarios, you need to configure the Katanomi of the global cluster:

• Continuous build pipelines running in the global cluster and configured with code repository triggers.

• Continuous deployment pipelines running in any cluster and configured with image repository triggers.

• Jenkins pipelines running in any cluster and configured with code repository triggers.

1. Click Catalog > Operators in the left navigation bar and switch to the global cluster.

2. On the Deployed Operators tab, click katanomi-operator.

3. Switch to the Resource Instances tab.

4. On the right side of the katanomi-global instance, click > Update.

5. Modify the External URL parameter to the external access address of the global cluster.