1.13.2. Resolving the problem: Git server connection
Important: Upgrade if you are on a previous version.
- Save apps.open-cluster-management.io_channels_crd.yaml as the same file name.
On the Red Hat Advanced Cluster Management cluster, run the following command to apply the file:
oc apply -f apps.open-cluster-management.io_channels_crd.yaml
In the
open-cluster-management
namespace, edit theadvanced-cluster-management.v2.2.0
CSV, run the following command and edit:oc edit csv advanced-cluster-management.v2.2.0 -n open-cluster-management
Find the following containers:
-
multicluster-operators-standalone-subscription
multicluster-operators-hub-subscription
Replace the container images with the following:
quay.io/open-cluster-management/multicluster-operators-subscription:2.2-PR337-91af6cb37d427d22160b2c055589a4418dada4eb
The update recreates the following pods in the
open-cluster-management
namespace:-
multicluster-operators-standalone-subscription-<random-characters>
-
multicluster-operators-hub-subscription-<random-characters>
-
- Check that the new pods are running with the new docker image. Run the following command, then find the new docker image:
oc get pod multicluster-operators-standalone-subscription-<random-characters> -n open-cluster-management -o yaml oc get pod multicluster-operators-hub-subscription-<random-characters> -n open-cluster-management -o yaml
Update the images on managed clusters.
On the hub cluster, run the following command by replacing
CLUSTER_NAME
with the actual managed cluster name:oc annotate klusterletaddonconfig -n CLUSTER_NAME CLUSTER_NAME klusterletaddonconfig-pause=true --overwrite=true
Run the following command, replacing
CLUSTER_NAME
with the actual managed cluster name:oc edit manifestwork -n CLUSTER_NAME CLUSTER_NAME-klusterlet-addon-appmgr
Find
spec.global.imageOverrides.multicluster_operators_subscription
and set the value to:quay.io/open-cluster-management/multicluster-operators-subscription:2.2-PR337-91af6cb37d427d22160b2c055589a4418dada4eb
This recreates the
klusterlet-addon-appmgr-<random-characters>
pod inopen-cluster-management-agent-addon
namespace on the managed cluster.- Check that the new pod is running with the new docker image.
When you create an application through the console or the CLI, add `insecureSkipVerify: true' in the channel spec manually. See the following example:
apiVersion: apps.open-cluster-management.io/v1 kind: Channel metadata: labels: name: sample-channel namespace: sample spec: type: GitHub pathname: <Git URL> insecureSkipVerify: true