7.3. Instalação do Migration Toolkit for Containers Operator herdado no OpenShift Container Platform 3

Procedimento

1. Faça login em register.redhat.io com suas credenciais do Portal do Cliente da Red Hat:

   $ sudo podman login registry.redhat.io

   Copy to Clipboard Toggle word wrap

2. Faça download do arquivo operator.yml:

   $ sudo podman cp $(sudo podman create \
     registry.redhat.io/rhmtc/openshift-migration-legacy-rhel8-operator:v1.5.3):/operator.yml ./

   Copy to Clipboard Toggle word wrap

3. Faça download do arquivo controller.yml:

   $ sudo podman cp $(sudo podman create \
     registry.redhat.io/rhmtc/openshift-migration-legacy-rhel8-operator:v1.5.3):/controller.yml ./

   Copy to Clipboard Toggle word wrap

4. Obtenha o mapeamento da imagem do Operador executando o seguinte comando:

   $ grep openshift-migration-legacy-rhel8-operator ./mapping.txt | grep rhmtc

   Copy to Clipboard Toggle word wrap

   O arquivo mapping.txt foi criado quando você espelhou o catálogo de Operadores. A saída mostra o mapeamento entre a imagem de registro.redhat.io e sua imagem de registro espelhada.

   Exemplo de saída

   registry.redhat.io/rhmtc/openshift-migration-legacy-rhel8-operator@sha256:468a6126f73b1ee12085ca53a312d1f96ef5a2ca03442bcb63724af5e2614e8a=<registry.apps.example.com>/rhmtc/openshift-migration-legacy-rhel8-operator

   Copy to Clipboard Toggle word wrap

5. Atualize os valores de image dos contêineres ansible e operator e o valor de REGISTRY no arquivo operator.yml:

   containers:
     - name: ansible
       image: <registry.apps.example.com>/rhmtc/openshift-migration-legacy-rhel8-operator@sha256:<468a6126f73b1ee12085ca53a312d1f96ef5a2ca03442bcb63724af5e2614e8a> 

   1

   
   ...
     - name: operator
       image: <registry.apps.example.com>/rhmtc/openshift-migration-legacy-rhel8-operator@sha256:<468a6126f73b1ee12085ca53a312d1f96ef5a2ca03442bcb63724af5e2614e8a> 

   2

   
   ...
       env:
       - name: REGISTRY
         value: <registry.apps.example.com> 

   3

   Copy to Clipboard Toggle word wrap

   1 2

   Especifique seu registro espelhado e o valor de sha256 da imagem do Operador.

   3

   Especifique seu registro espelhado.

6. Faça login no seu cluster do OpenShift Container Platform 3.

7. Crie o objeto do Migration Toolkit for Containers Operator:

   $ oc create -f operator.yml

   Copy to Clipboard Toggle word wrap

   Exemplo de saída

   namespace/openshift-migration created
   rolebinding.rbac.authorization.k8s.io/system:deployers created
   serviceaccount/migration-operator created
   customresourcedefinition.apiextensions.k8s.io/migrationcontrollers.migration.openshift.io created
   role.rbac.authorization.k8s.io/migration-operator created
   rolebinding.rbac.authorization.k8s.io/migration-operator created
   clusterrolebinding.rbac.authorization.k8s.io/migration-operator created
   deployment.apps/migration-operator created
   Error from server (AlreadyExists): error when creating "./operator.yml":
   rolebindings.rbac.authorization.k8s.io "system:image-builders" already exists 

   1

   
   Error from server (AlreadyExists): error when creating "./operator.yml":
   rolebindings.rbac.authorization.k8s.io "system:image-pullers" already exists

   Copy to Clipboard Toggle word wrap

   1

   Você pode ignorar as mensagens Error from server (AlreadyExists). Elas são geradas pelo Migration Toolkit for Containers Operator, que cria recursos para versões anteriores do OpenShift Container Platform 3, fornecidos em versões posteriores.

8. Crie o objeto MigrationController:

   $ oc create -f controller.yml

   Copy to Clipboard Toggle word wrap

9. Verifique se os pods do MTC estão em execução:

   $ oc get pods -n openshift-migration

   Copy to Clipboard Toggle word wrap