vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use containers-kubernetes for the service name.

Platform roles

Service roles

Actions



Table 25. Platform roles - Kubernetes Service
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 
 Editor As an editor, you can perform all platform actions except for managing the account and assigning access policies. 
 Operator As an operator, you can perform platform actions required to configure and operate service instances, such as viewing a service's dashboard. 
 Viewer As a viewer, you can view service instances, but you can't modify them. 







 Kubernetes service access roles and corresponding RBAC roles 

The following table shows the Kubernetes resource permissions that are granted by each service access role and its corresponding RBAC role.



Table 1. Kubernetes resource permissions by service and corresponding RBAC roles

 Service access role Corresponding RBAC role, binding, and scope Kubernetes resource permissions 

 Reader role When scoped to one namespace: view cluster role applied by the ibm-view role binding in that namespace.<br><br><br><br> * When scoped to all namespaces: view cluster role applied by the ibm-view role binding in each namespace of the cluster. You can also view the cluster in the IBM Cloud console and CLI.<br><br><br> <br><br> * Read access to resources in a namespace<br> * No read access to roles and role bindings or to Kubernetes secrets<br> * Access the Kubernetes dashboard to view resources in a namespace.<br><br><br>
-22824](https://nvd.nist.gov/vuln/detail/CVE-2022-22824), [CVE-2022-22825](https://nvd.nist.gov/vuln/detail/CVE-2022-22825), [CVE-2022-22826](https://nvd.nist.gov/vuln/detail/CVE-2022-22826), [CVE-2022-22827](https://nvd.nist.gov/vuln/detail/CVE-2022-22827), [CVE-2022-22942](https://nvd.nist.gov/vuln/detail/CVE-2022-22942), [CVE-2022-23852](https://nvd.nist.gov/vuln/detail/CVE-2022-23852), [CVE-2022-23990](https://nvd.nist.gov/vuln/detail/CVE-2022-23990), [CVE-2022-24407](https://nvd.nist.gov/vuln/detail/CVE-2022-24407), [CVE-2022-25235](https://nvd.nist.gov/vuln/detail/CVE-2022-25235), [CVE-2022-25236](https://nvd.nist.gov/vuln/detail/CVE-2022-25236). 
 Kubernetes v1.21.9 v1.21.10 For more information, see the [change logs](https://github.com/kubernetes/kubernetes/releases/tag/v1.21.10). 
 HA proxy f6a2b3 15198fb Contains fixes for [CVE-2022-24407](https://nvd.nist.gov/vuln/detail/CVE-2022-24407),
[CVE-2022-3515](https://nvd.nist.gov/vuln/detail/CVE-2022-3515), [CVE-2022-35737](https://nvd.nist.gov/vuln/detail/CVE-2022-35737), [CVE-2022-39253](https://nvd.nist.gov/vuln/detail/CVE-2022-39253), [CVE-2022-39260](https://nvd.nist.gov/vuln/detail/CVE-2022-39260), [CVE-2022-40284](https://nvd.nist.gov/vuln/detail/CVE-2022-40284), [CVE-2022-40674](https://nvd.nist.gov/vuln/detail/CVE-2022-40674), [CVE-2022-40768](https://nvd.nist.gov/vuln/detail/CVE-2022-40768), [CVE-2022-41974](https://nvd.nist.gov/vuln/detail/CVE-2022-41974), [CVE-2022-42010](https://nvd.nist.gov/vuln/detail/CVE-2022-42010), [CVE-2022-42011](https://nvd.nist.gov/vuln/detail/CVE-2022-42011), [CVE-2022-42012](https://nvd.nist.gov/vuln/detail/CVE-2022-42012). 
 Kubernetes 1.23.13 1.23.14 For more information, see the [change log](https://github.com/kubernetes/kubernetes/releases/tag/v1.23.14).
: Kubernetes version [1.18.8_1525](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog1188_1525), [1.17.11_1537](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog11711_1537), [1.16.14_1544](https://cloud.ibm.com/docs/containers?topic=containers-116_changelog11614_1544), and [1.15.12_1550](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog11512_1550) .

VPC Gen 2
: Added a tutorial for migrating VPC Gen 1 cluster resources to VPC Gen 2.





 12 August 2020 

Istio add-on
: [Version 1.6.8](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog168) and [version 1.5.9](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog159) of the Istio managed add-on are released.





 6 August 2020 

CLI change log
: Updated the IBM Cloud Kubernetes Service CLI plug-in change log page for the [release of version 1.0.143](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelog10).





 5 August 2020 

Ingress ALB change log
: Updated the [nginx-ingress image build to 647 and the ingress-auth image build to 421](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog).





 4 August 2020 

Istio add-on
<br> <br>Resources <br><br><br><br> * kubernetes_secret<br> * kubernetes_config_map<br> * kubernetes_job<br><br><br> [View code snippet](https://github.com/IBM-Cloud/terraform-provider-ibm/tree/master/examples/ibm-openshift-job) 
 portworx Set up Helm in an IBM Cloud Kubernetes Service software-defined storage (SDS) cluster to install Portworx as a storage solution. Make sure that this template requires an SDS cluster on Bare Metal worker nodes. After you installed Portworx, you can create persistent volume claims (PVC) to store data on local storage of your worker nodes. For more information, about Portworx and how to create an SDS cluster, see [Storing data on SDS with Portworx](https://cloud.ibm.com/docs/containers?topic=containers-portworx). <br> <br>Resources <br><br><br><br> * random_id<br> * kubernetes_secret<br> * helm_release<br><br><br> [View code snippet](https://github.com/IBM-Cloud/terraform-provider-ibm/tree/master/examples/portworx) 
 ibm-lbaas Create an IBM Cloud® Load Balancer for a classic virtual server instance. You configure the load balancer to manage incoming HTTPS and HTTP network traffic and set up health monitoring for your virtual server instance.
: Kubernetes [1.17.4_1521](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog1174_1521), [1.16.7_1528](https://cloud.ibm.com/docs/containers?topic=containers-116_changelog1168_1528), [1.15.10_1535](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog11511_1535), and [1.14.10_1551](https://cloud.ibm.com/docs/containers?topic=containers-114_changelog11410_1551).





 6 April 2020 

CLI change log
: Updated the IBM Cloud Kubernetes Service CLI plug-in change log page for the [release of version 1.0.28](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelog10).

Kubernetes cluster context
: Added topics for [Setting the Kubernetes context for multiple clusters](https://cloud.ibm.com/docs/containers?topic=containers-cli-install) and [Creating a temporary kubeconfig file](https://cloud.ibm.com/docs/containers?topic=containers-cli-install).





 1 April 2020 

Istio add-on
: [Version 1.4.7 of the Istio managed add-on](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog147) is released.







 March 2020 



 30 March 2020 

Version change logs
: Worker node patch updates are available.
Kubernetes add-on resizer 1.8.15 1.8.16 See the [Kubernetes add-on resizer release notes](https://github.com/kubernetes/autoscaler/releases/tag/addon-resizer-1.8.16). In addition, a liveness probe has been configured to improve availability. 
 Kubernetes DNS autoscaler configuration N/A N/A Memory resource requests were increased from 5Mi to 7Mi to better align with normal resource utilization. In addition, a liveness probe has been configured to improve availability. 
 Kubernetes Metrics Server v0.6.0 v0.6.2 See the [Kubernetes Metrics Server release notes](https://github.com/kubernetes-sigs/metrics-server/releases/tag/v0.6.2). 
 Kubernetes NodeLocal DNS cache 1.22.13 1.22.15 See the [Kubernetes NodeLocal DNS cache release notes](https://github.com/kubernetes/dns/releases/tag/1.22.15). 
 Pause container image 3.8 3.9 See the [pause container image release notes](https://github.com/kubernetes/kubernetes/blob/master/build/pause/CHANGELOG.md).
Kubernetes 1.25.2 1.25.3 For more information, see the [change log](https://github.com/kubernetes/kubernetes/releases/tag/v1.25.3). 
 HAProxy b034b2 3a1392 [CVE-2022-37434](https://nvd.nist.gov/vuln/detail/CVE-2022-37434), [CVE-2022-37434](https://nvd.nist.gov/vuln/detail/CVE-2022-37434), [CVE-2020-35525](https://nvd.nist.gov/vuln/detail/CVE-2020-35525), [CVE-2020-35527](https://nvd.nist.gov/vuln/detail/CVE-2020-35527), [CVE-2022-3515](https://nvd.nist.gov/vuln/detail/CVE-2022-3515), [CVE-2022-2509](https://nvd.nist.gov/vuln/detail/CVE-2022-2509). 
 CUDA 3ea43b 576234 [CVE-2022-3515](https://nvd.nist.gov/vuln/detail/CVE-2022-3515), [CVE-2022-2509](https://nvd.nist.gov/vuln/detail/CVE-2022-2509), [CVE-2022-37434](https://nvd.nist.gov/vuln/detail/CVE-2022-37434), [CVE-2020-35525](https://nvd.nist.gov/vuln/detail/CVE-2020-35525), [CVE-2020-35527](https://nvd.nist.gov/vuln/detail/CVE-2020-35527).
Kubernetes 1.24.6 1.24.7 For more information, see the [change log](https://github.com/kubernetes/kubernetes/releases/tag/v1.24.7). 
 HAProxy b034b2 3a1392 [CVE-2022-37434](https://nvd.nist.gov/vuln/detail/CVE-2022-37434), [CVE-2022-37434](https://nvd.nist.gov/vuln/detail/CVE-2022-37434), [CVE-2020-35525](https://nvd.nist.gov/vuln/detail/CVE-2020-35525), [CVE-2020-35527](https://nvd.nist.gov/vuln/detail/CVE-2020-35527), [CVE-2022-3515](https://nvd.nist.gov/vuln/detail/CVE-2022-3515), [CVE-2022-2509](https://nvd.nist.gov/vuln/detail/CVE-2022-2509). 
 CUDA 3ea43b 576234 [CVE-2022-3515](https://nvd.nist.gov/vuln/detail/CVE-2022-3515), [CVE-2022-2509](https://nvd.nist.gov/vuln/detail/CVE-2022-2509), [CVE-2022-37434](https://nvd.nist.gov/vuln/detail/CVE-2022-37434), [CVE-2020-35525](https://nvd.nist.gov/vuln/detail/CVE-2020-35525), [CVE-2020-35527](https://nvd.nist.gov/vuln/detail/CVE-2020-35527).
Kubernetes 1.23.12 1.23.13 For more information, see the [change log](https://github.com/kubernetes/kubernetes/releases/tag/v1.23.13). 
 HAPROXY b034b2 3a1392 [CVE-2022-37434](https://nvd.nist.gov/vuln/detail/CVE-2022-37434), [CVE-2022-37434](https://nvd.nist.gov/vuln/detail/CVE-2022-37434), [CVE-2020-35525](https://nvd.nist.gov/vuln/detail/CVE-2020-35525), [CVE-2020-35527](https://nvd.nist.gov/vuln/detail/CVE-2020-35527), [CVE-2022-3515](https://nvd.nist.gov/vuln/detail/CVE-2022-3515), [CVE-2022-2509](https://nvd.nist.gov/vuln/detail/CVE-2022-2509). 
 CUDA 3ea43b 576234 [CVE-2022-3515](https://nvd.nist.gov/vuln/detail/CVE-2022-3515), [CVE-2022-2509](https://nvd.nist.gov/vuln/detail/CVE-2022-2509), [CVE-2022-37434](https://nvd.nist.gov/vuln/detail/CVE-2022-37434), [CVE-2020-35525](https://nvd.nist.gov/vuln/detail/CVE-2020-35525), [CVE-2020-35527](https://nvd.nist.gov/vuln/detail/CVE-2020-35527).
List your Kubernetes services and find the name of the LoadBalancer service you want to change.

oc get services

Example output.

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
my-load-balancer LoadBalancer 172.21.77.198 52.118.150.107 8080:32767/TCP,443:30943/TCP 5d
3. Find the VPC load balancer that corresponds with the Kubernetes LoadBalancer service.

VPC load balancer names are in the format kube-<cluster_ID>-<kubernetes_lb_service_UID>. To see your cluster ID, run ibmcloud ks cluster get --cluster <cluster_name>. To see the Kubernetes LoadBalancer service UID, run oc get svc <load-balancer-name> -o yaml and look for the metadata.uid field in the output. The dashes (-) are removed from the Kubernetes LoadBalancer service UID in the VPC load balancer name.

ibmcloud is load-balancers

Example output.

ID Name Family Subnets Is public Provision status Operating status Resource group
r000-5aaaa11f6-c111-111f-b2e0-1c11aaaaf0dc0 kube-c441c43d02mb8mg00r70-3e25d0b5bf11111111fe4ca3f11111cb Network subnet-1 true active online default Application
4. Get the Kubernetes LoadBalancer service definition and save the output as a yaml file called my-lb.yaml.

oc describe service my-load-balancer -o yaml
5. Delete the Kubernetes LoadBalancer service. This also deletes the corresponding VPC load balancer.

oc delete service my-load-balancer
6. Update the Kubernetes LoadBalancer service definition file with the subnet or zone changes you want to implement. Do not change the name of the LoadBalancer service.
Kubernetes 1.21.10 1.21.11 See [change logs](https://github.com/kubernetes/kubernetes/releases/tag/v1.21.11). 







 Change log for worker node fix pack 1.21.10_1552, released 14 March 2022 



Changes since version 1.21.10_1551

 Component Previous Current Description 

 Containerd v1.5.9 v1.5.10 See the [change log](https://github.com/containerd/containerd/releases/tag/v1.5.10) and the [security bulletin](https://www.ibm.com/support/pages/node/6564653). 
 Ubuntu 18.04 packages 4.15.0-169-generic 4.15.0-171-generic Kernel and package updates for [CVE-2016-10228](https://nvd.nist.gov/vuln/detail/CVE-2016-10228), [CVE-2019-25013](https://nvd.nist.gov/vuln/detail/CVE-2019-25013), [CVE-2020-27618](https://nvd.nist.gov/vuln/detail/CVE-2020-27618), [CVE-2020-29562](https://nvd.nist.gov/vuln/detail/CVE-2020-29562), [CVE-2020-6096](https://nvd.nist.gov/vuln/detail/CVE-2020-6096), [CVE-2021-3326](
Storage options on IBM Cloud and Red Hat OpenShift 



 vSphere storage for Kubernetes 

You can use the VMware vSphere® datastores as a location for storing persistent volumes for Kubernetes by using the VMware® Cloud Provider.

Complete the following steps to create a new volume:



1. From the bastion host, use govc to enable the vSphere connection.

export GOVC_URL='10.208.17.2'
export GOVC_USERNAME='administrator@vsphere.local'
export GOVC_PASSWORD='xxx'
export GOVC_INSECURE=1
export GOVC_NETWORK='SDDC-DPortGroup-Mgmt'
export GOVC_DATASTORE='vsanDatastore'
2. Create a folder on the specified datastore.

govc datastore.mkdir ocp-volumes
3. Create a new persistent volume (vmdk).

govc datastore.disk.create -size 10G volumes/ocp-pv-001.vmdk
4. Log in to your Kubernetes environment from the command line.

oc login
5. Create a persistent volume in Kubernetes, for the recently created vdmk. Replace volumePath with your vmdk, in the example file called vsphere-volume-pv.yaml.

apiVersion: v1
kind: PersistentVolume
metadata:
name: ocpvsan002
spec:
capacity:
storage: 10Gi
accessModes:
- ReadWriteOnce
persistentVolumeReclaimPolicy: Retain
vsphereVolume:
volumePath: "[ESX_OCP] volumes/ocp-pv-001.vmdk"
fsType: ext4
storageClassName: "vsphere-standard"

Show more

kubectl create -f vsphere-volume-pvc.yaml
6. Create a Persistent Volume Claim in Kubernetes.
See the IAM Policy Management [API reference](https://cloud.ibm.com/apidocs/iam-policy-managementlist-roles) for more information on managing IAM roles with the API.



 Kubernetes Service 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use containers-kubernetes for the service name.

Platform roles

Service roles

Actions



Table 25. Platform roles - Kubernetes Service
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 
 Editor As an editor, you can perform all platform actions except for managing the account and assigning access policies. 
 Operator As an operator, you can perform platform actions required to configure and operate service instances, such as viewing a service's dashboard. 
 Viewer As a viewer, you can view service instances, but you can't modify them. 







 Kubernetes service access roles and corresponding RBAC roles 

The following table shows the Kubernetes resource permissions that are granted by each service access role and its corresponding RBAC role.



Table 1. Kubernetes resource permissions by service and corresponding RBAC roles

 Service access role Corresponding RBAC role, binding, and scope Kubernetes resource permissions 

 Reader role When scoped to one namespace: view cluster role applied by the ibm-view role binding in that namespace.<br><br><br><br> * When scoped to all namespaces: view cluster role applied by the ibm-view role binding in each namespace of the cluster.
To support multizone clusters, added zone and region labels to persistent volumes. 
 Kubernetes v1.9.8 v1.9.9 See the Kubernetes [release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.9.9) 
 Kernel N/A N/A Minor improvements to worker node network settings for high performance networking workloads. 
 OpenVPN client N/A N/A The OpenVPN client vpn deployment that runs in the kube-system namespace is now managed by the Kubernetes addon-manager. 







 Change log for worker node fix pack 1.9.8_1517, released 3 July 2018 

The following table shows the changes that are in the worker node fix pack 1.9.8_1517.



Table 1. Changes since version 1.9.8_1516

 Component Previous Current Description 

 Kernel N/A N/A Optimized sysctl for high performance networking workloads. 







 Change log for worker node fix pack 1.9.8_1516, released 21 June 2018 

The following table shows the changes that are in the worker node fix pack 1.9.8_1516.



Table 1. Changes since version 1.9.8_1515

 Component Previous Current Description 

 Docker N/A N/A For non-encrypted flavors, the secondary disk is cleaned by getting a fresh file system when you reload or update the worker node. 







 Change log for 1.9.8_1515, released 19 June 2018 

The following table shows the changes that are in patch 1.9.8_1515.



Table 1. Changes since version 1.9.7_1513

 Component Previous Current Description 

 Kubernetes v1.9.7 v1.9.8 See th [Kubernetes release notes]([https://github.com/kubernetes/kubernetes/releases/tag/v1.9.8](https://github.com/kubernetes/kubernetes/releases/tag/v1.9.8)]
[KMS commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cliks_kms) Enable a key management service (KMS) provider in your cluster to encrypt the etcd component and Kubernetes secrets with a root key that you control. 
 [Quota commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_quota) View the quota and limits for cluster-related resources in your IBM Cloud account. 
 [Subnets commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_subnets) List available subnets in your IBM Cloud infrastructure account. 
 [VLAN commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clivlan) List public and private VLANs for a zone and view the VLAN spanning status. 
 [VPCS commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_vpcs) List all VPCs in the targeted resource group. If no resource group is targeted, then all VPCs in the account are listed. 
 [Flavor commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_machine_types) Get the information of a flavor or list available flavors for a zone. 
 [Locations commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_supported-locations) List the locations that are supported by IBM Cloud Kubernetes Service. 
 [Messages commands](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_messages) View the current user messages.
Change log for 1.8.11_1509, released 19 April 2018 



Table 1. Changes since version 1.8.8_1507

 Component Previous Current Description 

 Kubernetes v1.8.8 v1.8.11 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.8.11). This release addresses [CVE-2017-1002101](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1002101)[ and [CVE-2017-1002102](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1002102)[ vulnerabilities. <br>Now secret, configMap, downwardAPI, and projected volumes are mounted as read-only. Previously, apps could write data to these volumes, but the system could automatically revert the data. If your apps rely on the previous insecure behavior, modify them accordingly. 
 Pause container image 3.0 3.1 Removes inherited orphaned zombie processes. 
 IBM Cloud Provider v1.8.8-86 v1.8.11-126 NodePort and LoadBalancer services now support [preserving the client source IP](https://cloud.ibm.com/docs/containers?topic=containers-loadbalancerlb_source_ip) by setting service.spec.externalTrafficPolicy to Local. 
 General N/A N/A Fix [edge node](https://cloud.ibm.com/docs/containers?topic=containers-edgeedge) toleration setup for older clusters.
Kubernetes v1.18.18 v1.18.19 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.18.19). The update resolves CVE-2020-8562 (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/6457271)) and CVE-2021-25737 (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/6457273)). 
 Kubernetes add-on resizer 1.8.11 1.8.12 See the [Kubernetes add-on resizer release notes](https://github.com/kubernetes/autoscaler/releases/tag/addon-resizer-1.8.12). 
 Kubernetes Metrics Server v0.3.7 v0.4.4 See the [Kubernetes Metrics Server release notes](https://github.com/kubernetes-sigs/metrics-server/releases/tag/v0.4.4). 
 Load balancer and load balancer monitor for IBM Cloud Provider 1274 1328 Updated to use Go version 1.15.11. Updated image to implement additional IBM security controls and for [CVE-2021-28831](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-28831), [CVE-2021-30139](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-30139), [CVE-2021-3449](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3449) and [CVE-2021-3450](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3450).
Where previously smart contracts were instantiated on a channel by a single channel member and other organizations only had the ability to choose whether to install the smart contract, the new lifecycle allows organizations to propose, approve, and commit smart contracts at an organizational level.

This separation of concerns opens exciting new opportunities for collaborating organizations. For example, different organizations can install smart contracts on their peers that contain only the code relevant to their business role and make minor updates to these smart contracts where necessary, without needing to seek new approvals from other organizations.

For a tutorial on how this process is handled by the console, check out [Deploy a smart contract using Fabric v2.x](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2).

For information about to take advantage of the new lifecycle when writing a smart contract, check out [Writing powerful smart contracts](https://cloud.ibm.com/docs/blockchain?topic=blockchain-write-powerful-smart-contracts).
* How can I check and interpret the status of my components through the Kubernetes command line?

To check the status of your component, run the following command:

kubectl get <CUSTOM_RESOURCE_TYPE> <CUSTOM_RESOURCE_NAME> -n <NAMESPACE> -o yaml



* Replace <CUSTOM_RESOURCE_TYPE> with the custom resource type of your component (ibpca, ibppeer, ibporderer, or ibpconsole).
* Replace <CUSTOM_RESOURCE_NAME> with the name of your component.
* Replace <NAMESPACE> with the name of your IBM Support for Hyperledger Fabric deployment namespace or OpenShift project.



The spec.status field will contain details of your component's status:



* errorCode
* lastHeartbeatTime: when the controller last reconciled the component
* message: long explanation of the status type
* reason: short explanation of the status
* status: "true" or "false" based on if status is valid
* version: the product (IBP) version of the component
* versions: the operand version of the component
* type: describes the current status of the component