Data Protection Software

Hallo Kevin,

thanks for your quick reaction.  I'm an instructor for TSM and SPP and would like to

show the K8s provider to my students.

My K8S installation is a small Test-Installation  (no minikube or so…) 

Just for completeness I tell you the steps what I have done. I try to install "online"  and not air-gapped.

My aim was just to install ONLY the absolute necessary components, so that I can register the provider in SPP and show  the install process and 
"a PVC" .

So e.g.  currently  no velero, no metrics server  and no  application to volume claim relationship.

Install steps

• Certificate manager  - installed successfully
• Bass-options.sh created:

export DOCKER_REGISTRY_ADDRESS='cp.icr.io/cp'

export DOCKER_REGISTRY_USERNAME='cp'

export DOCKER_REGISTRY_PASSWORD='  the key I copied '

export DOCKER_REGISTRY_NAMESPACE='sppc'

export SPP_ADMIN_USERNAME='mm_admin'

export SPP_ADMIN_PASSWORD='xxxxxxx'

export DATAMOVER_USERNAME='mm_admin'

export DATAMOVER_PASSWORD='xxxxxxx'

export MINIO_USERNAME='mm_admin'

export MINIO_PASSWORD='xxxxxxx'

export REDHAT_REGISTRY_ADDRESS='registry.redhat.io'

export REDHAT_REGISTRY_USERNAME='my userid'

export REDHAT_REGISTRY_PASSWORD='my_pw'

• Access to redhat and ibm registries is OK  and I logged in successfully to both registries
• Operator Life-cycle Manager  - installed successfully
• Namespace baas ceated
• Secrets as on page 140 UG -  created successfully
• baas-k8s-catalogsource.yaml -  applied successfully
• baas-k8s-operatorgroup.yaml and baas-k8s-subscription.yaml   - applied successfully

outputs of  steps  1  and 2  mentioned on page 142  UG 10.1.10:

kubectl apply -f baas-k8s-catalogsource.yaml

 kubectl get catalogsource –A

kubectl describe catalogsource -n olm ibm-sppc-operator | grep Image

• my baas-values-cr.yaml file: (indention in "real" file is correct)

apiVersion: sppc.ibm.com/v1

#apiVersion: IBMSPPC.V1.sppc.ibm.com

kind: IBMSPPC

metadata:

  namespace: baas

# Malitz 04-2022

  name: ibmsppc-entitled-registry

spec:

  state: present

  version: 10.1.10

  license:

    accept: true

  # use_nodeport: false

  product_loglevel: INFO

  cluster_name: MM_K8s_Cluster

  image_registry_namespace: sppc

  image_registry: 'cp.icr.io/cp'

  #

  image_registry_secret: baas-registry-secret

  spp_port: 443

  spp_ips: 192.168.1.50

  spp_fqdn: spp.enablement.lab

  networkPolicy:

    cluster_api_serverips:

      - 192.168.1.210

      #- kubernetes_host_ip2

      #- kubernetes_host_ip3

    cluster_api_serverport: 6443

    cluster_cidr: 10.244.0.0/16

    is_server_installed_on_another_cluster: false

    other_cluster_cidr_block: None

    #other_cluster_cidr_block: '24'

  minio_storage_class: None

  #minio_storage_class: name_of_storageclass_to_use_with_minio

  velero_namespace: None

  cluster_nodes_fqdn:

    - mm-k8s-master.enablement.lab

    - mm-k8s-worker-1.enablement.lab

kubectl apply -f ./baas-values-cr.yaml

Result:

[root@mm-k8s-master mikels_yaml_files]# kubectl apply -f ./baas-values-cr.yaml

error: unable to recognize "./baas-values-cr.yaml": no matches for kind "IBMSPPC" in version "sppc.ibm.com/v1"

"./baas-values-cr.yaml": no matches for kind "IBMSPPC" in version "sppc.ibm.com/v1"

kubectl get catalogsource –A

Hallo Kevin,

thanks for your quick reaction.  I'm an instructor for TSM and SPP and would like to

show the K8s provider to my students.

My K8S installation is a small Test-Installation  (no minikube or so…) 

Just for completeness I tell you the steps what I have done. I try to install "online"  and not air-gapped.

My aim was just to install ONLY the absolute necessary components, so that I can register the provider in SPP and show  the install process and 
"a PVC" .

So e.g.  currently  no velero, no metrics server  and no  application to volume claim relationship.

Install steps

• Certificate manager  - installed successfully
• Bass-options.sh created:

export DOCKER_REGISTRY_ADDRESS='cp.icr.io/cp'

export DOCKER_REGISTRY_USERNAME='cp'

export DOCKER_REGISTRY_PASSWORD='  the key I copied '

export DOCKER_REGISTRY_NAMESPACE='sppc'

export SPP_ADMIN_USERNAME='mm_admin'

export SPP_ADMIN_PASSWORD='xxxxxxx'

export DATAMOVER_USERNAME='mm_admin'

export DATAMOVER_PASSWORD='xxxxxxx'

export MINIO_USERNAME='mm_admin'

export MINIO_PASSWORD='xxxxxxx'

export REDHAT_REGISTRY_ADDRESS='registry.redhat.io'

export REDHAT_REGISTRY_USERNAME='my userid'

export REDHAT_REGISTRY_PASSWORD='my_pw'

• Access to redhat and ibm registries is OK  and I logged in successfully to both registries
• Operator Life-cycle Manager  - installed successfully
• Namespace baas ceated
• Secrets as on page 140 UG -  created successfully
• baas-k8s-catalogsource.yaml -  applied successfully
• baas-k8s-operatorgroup.yaml and baas-k8s-subscription.yaml   - applied successfully

outputs of  steps  1  and 2  mentioned on page 142  UG 10.1.10:

kubectl apply -f baas-k8s-catalogsource.yaml

 kubectl get catalogsource –A

kubectl describe catalogsource -n olm ibm-sppc-operator | grep Image

• my baas-values-cr.yaml file: (indention in "real" file is correct)

apiVersion: sppc.ibm.com/v1

#apiVersion: IBMSPPC.V1.sppc.ibm.com

kind: IBMSPPC

metadata:

  namespace: baas

# Malitz 04-2022

  name: ibmsppc-entitled-registry

spec:

  state: present

  version: 10.1.10

  license:

    accept: true

  # use_nodeport: false

  product_loglevel: INFO

  cluster_name: MM_K8s_Cluster

  image_registry_namespace: sppc

  image_registry: 'cp.icr.io/cp'

  #

  image_registry_secret: baas-registry-secret

  spp_port: 443

  spp_ips: 192.168.1.50

  spp_fqdn: spp.enablement.lab

  networkPolicy:

    cluster_api_serverips:

      - 192.168.1.210

      #- kubernetes_host_ip2

      #- kubernetes_host_ip3

    cluster_api_serverport: 6443

    cluster_cidr: 10.244.0.0/16

    is_server_installed_on_another_cluster: false

    other_cluster_cidr_block: None

    #other_cluster_cidr_block: '24'

  minio_storage_class: None

  #minio_storage_class: name_of_storageclass_to_use_with_minio

  velero_namespace: None

  cluster_nodes_fqdn:

    - mm-k8s-master.enablement.lab

    - mm-k8s-worker-1.enablement.lab

kubectl apply -f ./baas-values-cr.yaml

Result:

[root@mm-k8s-master mikels_yaml_files]# kubectl apply -f ./baas-values-cr.yaml

error: unable to recognize "./baas-values-cr.yaml": no matches for kind "IBMSPPC" in version "sppc.ibm.com/v1"

"./baas-values-cr.yaml": no matches for kind "IBMSPPC" in version "sppc.ibm.com/v1"

Could you also get the output from this command:

kubectl get pods -n olm

kubectl get catalogsource –A

Hallo Kevin,

thanks for your quick reaction.  I'm an instructor for TSM and SPP and would like to

show the K8s provider to my students.

My K8S installation is a small Test-Installation  (no minikube or so…) 

Just for completeness I tell you the steps what I have done. I try to install "online"  and not air-gapped.

My aim was just to install ONLY the absolute necessary components, so that I can register the provider in SPP and show  the install process and 
"a PVC" .

So e.g.  currently  no velero, no metrics server  and no  application to volume claim relationship.

Install steps

• Certificate manager  - installed successfully
• Bass-options.sh created:

export DOCKER_REGISTRY_ADDRESS='cp.icr.io/cp'

export DOCKER_REGISTRY_USERNAME='cp'

export DOCKER_REGISTRY_PASSWORD='  the key I copied '

export DOCKER_REGISTRY_NAMESPACE='sppc'

export SPP_ADMIN_USERNAME='mm_admin'

export SPP_ADMIN_PASSWORD='xxxxxxx'

export DATAMOVER_USERNAME='mm_admin'

export DATAMOVER_PASSWORD='xxxxxxx'

export MINIO_USERNAME='mm_admin'

export MINIO_PASSWORD='xxxxxxx'

export REDHAT_REGISTRY_ADDRESS='registry.redhat.io'

export REDHAT_REGISTRY_USERNAME='my userid'

export REDHAT_REGISTRY_PASSWORD='my_pw'

• Access to redhat and ibm registries is OK  and I logged in successfully to both registries
• Operator Life-cycle Manager  - installed successfully
• Namespace baas ceated
• Secrets as on page 140 UG -  created successfully
• baas-k8s-catalogsource.yaml -  applied successfully
• baas-k8s-operatorgroup.yaml and baas-k8s-subscription.yaml   - applied successfully

outputs of  steps  1  and 2  mentioned on page 142  UG 10.1.10:

kubectl apply -f baas-k8s-catalogsource.yaml

 kubectl get catalogsource –A

kubectl describe catalogsource -n olm ibm-sppc-operator | grep Image

• my baas-values-cr.yaml file: (indention in "real" file is correct)

apiVersion: sppc.ibm.com/v1

#apiVersion: IBMSPPC.V1.sppc.ibm.com

kind: IBMSPPC

metadata:

  namespace: baas

# Malitz 04-2022

  name: ibmsppc-entitled-registry

spec:

  state: present

  version: 10.1.10

  license:

    accept: true

  # use_nodeport: false

  product_loglevel: INFO

  cluster_name: MM_K8s_Cluster

  image_registry_namespace: sppc

  image_registry: 'cp.icr.io/cp'

  #

  image_registry_secret: baas-registry-secret

  spp_port: 443

  spp_ips: 192.168.1.50

  spp_fqdn: spp.enablement.lab

  networkPolicy:

    cluster_api_serverips:

      - 192.168.1.210

      #- kubernetes_host_ip2

      #- kubernetes_host_ip3

    cluster_api_serverport: 6443

    cluster_cidr: 10.244.0.0/16

    is_server_installed_on_another_cluster: false

    other_cluster_cidr_block: None

    #other_cluster_cidr_block: '24'

  minio_storage_class: None

  #minio_storage_class: name_of_storageclass_to_use_with_minio

  velero_namespace: None

  cluster_nodes_fqdn:

    - mm-k8s-master.enablement.lab

    - mm-k8s-worker-1.enablement.lab

kubectl apply -f ./baas-values-cr.yaml

Result:

[root@mm-k8s-master mikels_yaml_files]# kubectl apply -f ./baas-values-cr.yaml

error: unable to recognize "./baas-values-cr.yaml": no matches for kind "IBMSPPC" in version "sppc.ibm.com/v1"

"./baas-values-cr.yaml": no matches for kind "IBMSPPC" in version "sppc.ibm.com/v1"

Could you also get the output from this command:

kubectl get pods -n olm

kubectl get catalogsource –A

Hallo Kevin,

thanks for your quick reaction.  I'm an instructor for TSM and SPP and would like to

show the K8s provider to my students.

My K8S installation is a small Test-Installation  (no minikube or so…) 

Just for completeness I tell you the steps what I have done. I try to install "online"  and not air-gapped.

My aim was just to install ONLY the absolute necessary components, so that I can register the provider in SPP and show  the install process and 
"a PVC" .

So e.g.  currently  no velero, no metrics server  and no  application to volume claim relationship.

Install steps

• Certificate manager  - installed successfully
• Bass-options.sh created:

export DOCKER_REGISTRY_ADDRESS='cp.icr.io/cp'

export DOCKER_REGISTRY_USERNAME='cp'

export DOCKER_REGISTRY_PASSWORD='  the key I copied '

export DOCKER_REGISTRY_NAMESPACE='sppc'

export SPP_ADMIN_USERNAME='mm_admin'

export SPP_ADMIN_PASSWORD='xxxxxxx'

export DATAMOVER_USERNAME='mm_admin'

export DATAMOVER_PASSWORD='xxxxxxx'

export MINIO_USERNAME='mm_admin'

export MINIO_PASSWORD='xxxxxxx'

export REDHAT_REGISTRY_ADDRESS='registry.redhat.io'

export REDHAT_REGISTRY_USERNAME='my userid'

export REDHAT_REGISTRY_PASSWORD='my_pw'

• Access to redhat and ibm registries is OK  and I logged in successfully to both registries
• Operator Life-cycle Manager  - installed successfully
• Namespace baas ceated
• Secrets as on page 140 UG -  created successfully
• baas-k8s-catalogsource.yaml -  applied successfully
• baas-k8s-operatorgroup.yaml and baas-k8s-subscription.yaml   - applied successfully

outputs of  steps  1  and 2  mentioned on page 142  UG 10.1.10:

kubectl apply -f baas-k8s-catalogsource.yaml

 kubectl get catalogsource –A

kubectl describe catalogsource -n olm ibm-sppc-operator | grep Image

• my baas-values-cr.yaml file: (indention in "real" file is correct)

apiVersion: sppc.ibm.com/v1

#apiVersion: IBMSPPC.V1.sppc.ibm.com

kind: IBMSPPC

metadata:

  namespace: baas

# Malitz 04-2022

  name: ibmsppc-entitled-registry

spec:

  state: present

  version: 10.1.10

  license:

    accept: true

  # use_nodeport: false

  product_loglevel: INFO

  cluster_name: MM_K8s_Cluster

  image_registry_namespace: sppc

  image_registry: 'cp.icr.io/cp'

  #

  image_registry_secret: baas-registry-secret

  spp_port: 443

  spp_ips: 192.168.1.50

  spp_fqdn: spp.enablement.lab

  networkPolicy:

    cluster_api_serverips:

      - 192.168.1.210

      #- kubernetes_host_ip2

      #- kubernetes_host_ip3

    cluster_api_serverport: 6443

    cluster_cidr: 10.244.0.0/16

    is_server_installed_on_another_cluster: false

    other_cluster_cidr_block: None

    #other_cluster_cidr_block: '24'

  minio_storage_class: None

  #minio_storage_class: name_of_storageclass_to_use_with_minio

  velero_namespace: None

  cluster_nodes_fqdn:

    - mm-k8s-master.enablement.lab

    - mm-k8s-worker-1.enablement.lab

kubectl apply -f ./baas-values-cr.yaml

Result:

[root@mm-k8s-master mikels_yaml_files]# kubectl apply -f ./baas-values-cr.yaml

error: unable to recognize "./baas-values-cr.yaml": no matches for kind "IBMSPPC" in version "sppc.ibm.com/v1"

"./baas-values-cr.yaml": no matches for kind "IBMSPPC" in version "sppc.ibm.com/v1"

The ibmsppc-operator-controller-manager pod is the one that would need to be running in order to recognize the IBMSPPC object. You can check that with 'kubectl get pods -n baas'. If that is running, you can try the logs for it.

kubectl logs -f ibmsppc-operator-controller-manager-xyz -c manager -n baas

If it is not running, then go through the prerequisite steps and see if something got missed.

https://www.ibm.com/docs/en/spp/10.1.10?topic=cluster-preparing-install-operator-kubernetes

Could you also get the output from this command:

kubectl get pods -n olm

kubectl get catalogsource –A

Hallo Kevin,

thanks for your quick reaction.  I'm an instructor for TSM and SPP and would like to

show the K8s provider to my students.

My K8S installation is a small Test-Installation  (no minikube or so…) 

Just for completeness I tell you the steps what I have done. I try to install "online"  and not air-gapped.

My aim was just to install ONLY the absolute necessary components, so that I can register the provider in SPP and show  the install process and 
"a PVC" .

So e.g.  currently  no velero, no metrics server  and no  application to volume claim relationship.

Install steps

• Certificate manager  - installed successfully
• Bass-options.sh created:

export DOCKER_REGISTRY_ADDRESS='cp.icr.io/cp'

export DOCKER_REGISTRY_USERNAME='cp'

export DOCKER_REGISTRY_PASSWORD='  the key I copied '

export DOCKER_REGISTRY_NAMESPACE='sppc'

export SPP_ADMIN_USERNAME='mm_admin'

export SPP_ADMIN_PASSWORD='xxxxxxx'

export DATAMOVER_USERNAME='mm_admin'

export DATAMOVER_PASSWORD='xxxxxxx'

export MINIO_USERNAME='mm_admin'

export MINIO_PASSWORD='xxxxxxx'

export REDHAT_REGISTRY_ADDRESS='registry.redhat.io'

export REDHAT_REGISTRY_USERNAME='my userid'

export REDHAT_REGISTRY_PASSWORD='my_pw'

• Access to redhat and ibm registries is OK  and I logged in successfully to both registries
• Operator Life-cycle Manager  - installed successfully
• Namespace baas ceated
• Secrets as on page 140 UG -  created successfully
• baas-k8s-catalogsource.yaml -  applied successfully
• baas-k8s-operatorgroup.yaml and baas-k8s-subscription.yaml   - applied successfully

outputs of  steps  1  and 2  mentioned on page 142  UG 10.1.10:

kubectl apply -f baas-k8s-catalogsource.yaml

 kubectl get catalogsource –A

kubectl describe catalogsource -n olm ibm-sppc-operator | grep Image

• my baas-values-cr.yaml file: (indention in "real" file is correct)

apiVersion: sppc.ibm.com/v1

#apiVersion: IBMSPPC.V1.sppc.ibm.com

kind: IBMSPPC

metadata:

  namespace: baas

# Malitz 04-2022

  name: ibmsppc-entitled-registry

spec:

  state: present

  version: 10.1.10

  license:

    accept: true

  # use_nodeport: false

  product_loglevel: INFO

  cluster_name: MM_K8s_Cluster

  image_registry_namespace: sppc

  image_registry: 'cp.icr.io/cp'

  #

  image_registry_secret: baas-registry-secret

  spp_port: 443

  spp_ips: 192.168.1.50

  spp_fqdn: spp.enablement.lab

  networkPolicy:

    cluster_api_serverips:

      - 192.168.1.210

      #- kubernetes_host_ip2

      #- kubernetes_host_ip3

    cluster_api_serverport: 6443

    cluster_cidr: 10.244.0.0/16

    is_server_installed_on_another_cluster: false

    other_cluster_cidr_block: None

    #other_cluster_cidr_block: '24'

  minio_storage_class: None

  #minio_storage_class: name_of_storageclass_to_use_with_minio

  velero_namespace: None

  cluster_nodes_fqdn:

    - mm-k8s-master.enablement.lab

    - mm-k8s-worker-1.enablement.lab

kubectl apply -f ./baas-values-cr.yaml

Result:

[root@mm-k8s-master mikels_yaml_files]# kubectl apply -f ./baas-values-cr.yaml

error: unable to recognize "./baas-values-cr.yaml": no matches for kind "IBMSPPC" in version "sppc.ibm.com/v1"

"./baas-values-cr.yaml": no matches for kind "IBMSPPC" in version "sppc.ibm.com/v1"

The ibmsppc-operator-controller-manager pod is the one that would need to be running in order to recognize the IBMSPPC object. You can check that with 'kubectl get pods -n baas'. If that is running, you can try the logs for it.

kubectl logs -f ibmsppc-operator-controller-manager-xyz -c manager -n baas

If it is not running, then go through the prerequisite steps and see if something got missed.

https://www.ibm.com/docs/en/spp/10.1.10?topic=cluster-preparing-install-operator-kubernetes

Could you also get the output from this command:

kubectl get pods -n olm

kubectl get catalogsource –A

Hallo Kevin,

thanks for your quick reaction.  I'm an instructor for TSM and SPP and would like to

show the K8s provider to my students.

My K8S installation is a small Test-Installation  (no minikube or so…) 

Just for completeness I tell you the steps what I have done. I try to install "online"  and not air-gapped.

My aim was just to install ONLY the absolute necessary components, so that I can register the provider in SPP and show  the install process and 
"a PVC" .

So e.g.  currently  no velero, no metrics server  and no  application to volume claim relationship.

Install steps

• Certificate manager  - installed successfully
• Bass-options.sh created:

export DOCKER_REGISTRY_ADDRESS='cp.icr.io/cp'

export DOCKER_REGISTRY_USERNAME='cp'

export DOCKER_REGISTRY_PASSWORD='  the key I copied '

export DOCKER_REGISTRY_NAMESPACE='sppc'

export SPP_ADMIN_USERNAME='mm_admin'

export SPP_ADMIN_PASSWORD='xxxxxxx'

export DATAMOVER_USERNAME='mm_admin'

export DATAMOVER_PASSWORD='xxxxxxx'

export MINIO_USERNAME='mm_admin'

export MINIO_PASSWORD='xxxxxxx'

export REDHAT_REGISTRY_ADDRESS='registry.redhat.io'

export REDHAT_REGISTRY_USERNAME='my userid'

export REDHAT_REGISTRY_PASSWORD='my_pw'

• Access to redhat and ibm registries is OK  and I logged in successfully to both registries
• Operator Life-cycle Manager  - installed successfully
• Namespace baas ceated
• Secrets as on page 140 UG -  created successfully
• baas-k8s-catalogsource.yaml -  applied successfully
• baas-k8s-operatorgroup.yaml and baas-k8s-subscription.yaml   - applied successfully

outputs of  steps  1  and 2  mentioned on page 142  UG 10.1.10:

kubectl apply -f baas-k8s-catalogsource.yaml

 kubectl get catalogsource –A

kubectl describe catalogsource -n olm ibm-sppc-operator | grep Image

• my baas-values-cr.yaml file: (indention in "real" file is correct)

apiVersion: sppc.ibm.com/v1

#apiVersion: IBMSPPC.V1.sppc.ibm.com

kind: IBMSPPC

metadata:

  namespace: baas

# Malitz 04-2022

  name: ibmsppc-entitled-registry

spec:

  state: present

  version: 10.1.10

  license:

    accept: true

  # use_nodeport: false

  product_loglevel: INFO

  cluster_name: MM_K8s_Cluster

  image_registry_namespace: sppc

  image_registry: 'cp.icr.io/cp'

  #

  image_registry_secret: baas-registry-secret

  spp_port: 443

  spp_ips: 192.168.1.50

  spp_fqdn: spp.enablement.lab

  networkPolicy:

    cluster_api_serverips:

      - 192.168.1.210

      #- kubernetes_host_ip2

      #- kubernetes_host_ip3

    cluster_api_serverport: 6443

    cluster_cidr: 10.244.0.0/16

    is_server_installed_on_another_cluster: false

    other_cluster_cidr_block: None

    #other_cluster_cidr_block: '24'

  minio_storage_class: None

  #minio_storage_class: name_of_storageclass_to_use_with_minio

  velero_namespace: None

  cluster_nodes_fqdn:

    - mm-k8s-master.enablement.lab

    - mm-k8s-worker-1.enablement.lab

kubectl apply -f ./baas-values-cr.yaml

Result:

[root@mm-k8s-master mikels_yaml_files]# kubectl apply -f ./baas-values-cr.yaml

error: unable to recognize "./baas-values-cr.yaml": no matches for kind "IBMSPPC" in version "sppc.ibm.com/v1"

"./baas-values-cr.yaml": no matches for kind "IBMSPPC" in version "sppc.ibm.com/v1"

The ibmsppc-operator-controller-manager pod is the one that would need to be running in order to recognize the IBMSPPC object. You can check that with 'kubectl get pods -n baas'. If that is running, you can try the logs for it.

kubectl logs -f ibmsppc-operator-controller-manager-xyz -c manager -n baas

If it is not running, then go through the prerequisite steps and see if something got missed.

https://www.ibm.com/docs/en/spp/10.1.10?topic=cluster-preparing-install-operator-kubernetes

Could you also get the output from this command:

kubectl get pods -n olm

kubectl get catalogsource –A

Hallo Kevin,

thanks for your quick reaction.  I'm an instructor for TSM and SPP and would like to

show the K8s provider to my students.

My K8S installation is a small Test-Installation  (no minikube or so…) 

Just for completeness I tell you the steps what I have done. I try to install "online"  and not air-gapped.

My aim was just to install ONLY the absolute necessary components, so that I can register the provider in SPP and show  the install process and 
"a PVC" .

So e.g.  currently  no velero, no metrics server  and no  application to volume claim relationship.

Install steps

• Certificate manager  - installed successfully
• Bass-options.sh created:

export DOCKER_REGISTRY_ADDRESS='cp.icr.io/cp'

export DOCKER_REGISTRY_USERNAME='cp'

export DOCKER_REGISTRY_PASSWORD='  the key I copied '

export DOCKER_REGISTRY_NAMESPACE='sppc'

export SPP_ADMIN_USERNAME='mm_admin'

export SPP_ADMIN_PASSWORD='xxxxxxx'

export DATAMOVER_USERNAME='mm_admin'

export DATAMOVER_PASSWORD='xxxxxxx'

export MINIO_USERNAME='mm_admin'

export MINIO_PASSWORD='xxxxxxx'

export REDHAT_REGISTRY_ADDRESS='registry.redhat.io'

export REDHAT_REGISTRY_USERNAME='my userid'

export REDHAT_REGISTRY_PASSWORD='my_pw'

• Access to redhat and ibm registries is OK  and I logged in successfully to both registries
• Operator Life-cycle Manager  - installed successfully
• Namespace baas ceated
• Secrets as on page 140 UG -  created successfully
• baas-k8s-catalogsource.yaml -  applied successfully
• baas-k8s-operatorgroup.yaml and baas-k8s-subscription.yaml   - applied successfully

outputs of  steps  1  and 2  mentioned on page 142  UG 10.1.10:

kubectl apply -f baas-k8s-catalogsource.yaml

 kubectl get catalogsource –A

kubectl describe catalogsource -n olm ibm-sppc-operator | grep Image

• my baas-values-cr.yaml file: (indention in "real" file is correct)

apiVersion: sppc.ibm.com/v1

#apiVersion: IBMSPPC.V1.sppc.ibm.com

kind: IBMSPPC

metadata:

  namespace: baas

# Malitz 04-2022

  name: ibmsppc-entitled-registry

spec:

  state: present

  version: 10.1.10

  license:

    accept: true

  # use_nodeport: false

  product_loglevel: INFO

  cluster_name: MM_K8s_Cluster

  image_registry_namespace: sppc

  image_registry: 'cp.icr.io/cp'

  #

  image_registry_secret: baas-registry-secret

  spp_port: 443

  spp_ips: 192.168.1.50

  spp_fqdn: spp.enablement.lab

  networkPolicy:

    cluster_api_serverips:

      - 192.168.1.210

      #- kubernetes_host_ip2

      #- kubernetes_host_ip3

    cluster_api_serverport: 6443

    cluster_cidr: 10.244.0.0/16

    is_server_installed_on_another_cluster: false

    other_cluster_cidr_block: None

    #other_cluster_cidr_block: '24'

  minio_storage_class: None

  #minio_storage_class: name_of_storageclass_to_use_with_minio

  velero_namespace: None

  cluster_nodes_fqdn:

    - mm-k8s-master.enablement.lab

    - mm-k8s-worker-1.enablement.lab

kubectl apply -f ./baas-values-cr.yaml

Result:

[root@mm-k8s-master mikels_yaml_files]# kubectl apply -f ./baas-values-cr.yaml

error: unable to recognize "./baas-values-cr.yaml": no matches for kind "IBMSPPC" in version "sppc.ibm.com/v1"

"./baas-values-cr.yaml": no matches for kind "IBMSPPC" in version "sppc.ibm.com/v1"