vania-janet/multiturn-rag-retrieval-data huggingface dataset:
: Kubernetes version [1.19.4_1527](https://cloud.ibm.com/docs/containers?topic=containers-changelog_1191194_1527_worker), [1.18.12_1533](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog11812_1533_worker), [1.17.14_1545](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog11714_1545_worker), and [1.16.15_1552](https://cloud.ibm.com/docs/containers?topic=containers-116_changelog11615_1552_worker).





 20 November 2020 

New! Portieris for image security enforcement
: With the [open source Portieris project](https://github.com/IBM/portieris), you can set up a Kubernetes admission controller to enforce image security policies by namespace or cluster. Use [Portieris](https://cloud.ibm.com/docs/Registry?topic=Registry-security_enforce_portieris) instead of the deprecated Container Image Security Enforcement Helm chart.





 19 November 2020 

Ingress ALB change log
: Updated the [nginx-ingress build to 653 and the ingress-auth build to 425](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog) for the IBM Cloud Kubernetes Service Ingress image.





 18 November 2020 

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

Knative add-on deprecation
: As of 18 November 2020 the Knative managed add-on is deprecated.
Kubernetes DNS autoscaler 1.1.2-r2 1.2.0 See the [Kubernetes DNS autoscaler release notes](https://github.com/kubernetes-sigs/cluster-proportional-autoscaler/releases/tag/1.2.0). 
 IBM Cloud Provider v1.10.7-146 v1.10.8-172 Updated to support Kubernetes 1.10.8 release. Also, updated the documentation link in load balancer error messages. 
 IBM file storage classes N/A N/A Removed mountOptions in the IBM file storage classes to use the default that is provided by the worker node. Removed duplicate reclaimPolicy parameter in the IBM file storage classes. <br>Also, now when you update the cluster master, the default IBM file storage class remains unchanged. 







 Change log for worker node fix pack 1.10.7_1521, released 20 September 2018 

The following table shows the changes that are in the worker node fix pack 1.10.7_1521.



Table 1. Changes since version 1.10.7_1520

 Component Previous Current Description 

 Log rotate N/A N/A Switched to use systemd timers instead of cronjobs to prevent logrotate from failing on worker nodes that are not reloaded or updated within 90 days. Note: In all earlier versions for this minor release, the primary disk fills up after the cron job fails because the logs are not rotated. The cron job fails after the worker node is active for 90 days without being updated or reloaded. If the logs fill up the entire primary disk, the worker node enters a failed state. The worker node can be fixed by using the ibmcloud ks worker reload[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_reload) or the ibmcloud ks worker update[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_update).
: Kubernetes [1.16.3_1519](https://cloud.ibm.com/docs/containers?topic=containers-116_changelog1163_1519_worker), [1.15.6_1526](https://cloud.ibm.com/docs/containers?topic=containers-115_changelog1156_1526_worker), [1.14.9_1542](https://cloud.ibm.com/docs/containers?topic=containers-114_changelog1149_1542_worker), and [1.13.12_1545](https://cloud.ibm.com/docs/containers?topic=containers-113_changelog11312_1545_worker).





 4 December 2019 

Exposing apps with load balancers or Ingress ALBs
: Added quick start pages to help you get up and running with [load balancers](https://cloud.ibm.com/docs/containers?topic=containers-loadbalancer-qs) and [Ingress ALBs](https://cloud.ibm.com/docs/containers?topic=containers-managed-ingress-about).

Kubernetes web terminal for VPC clusters
: To use the Kubernetes web terminal for VPC clusters, make sure to [configure access to external endpoints](https://cloud.ibm.com/docs/containers?topic=containers-cli-install).

Monitoring Istio
: Added [steps](https://cloud.ibm.com/docs/containers?topic=containers-istio-healthistio_inspect) to launch the ControlZ component inspection and Envoy sidecar dashboards for the Istio managed add-on.

Tuning network performance
: Added [steps](https://cloud.ibm.com/docs/containers?topic=containers-kernelcalico-portmap) for disabling the portmap plug-in for for the Calico container network interface (CNI).

Use the internal KVDB in Portworx
The file extension of the Kubernetes resource file that you want to add. Supported file types are yaml.

--description DESCRIPTION
: Optional. A description for your version, such as the purpose of the Kubernetes resources that the version contains. For example, Added replicas and zone affinity for HA version of app for multizone clusters.

--q
: Optional. Do not show the message of the day or update reminders.





 Example 

ibmcloud sat config version create --name 1.0 --read-config /file/path/myapp.yaml --config myapp_prod --file-format yaml







 ibmcloud sat config version get 

Get the details of a particular version that you added to your Satellite configuration.

ibmcloud sat config version get --config CONFIG --version VERSION [--output JSON] [--save-config] [-q]



 Minimum required permissions 

IBM Cloud IAM Viewer platform role for the Configuration resource in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--config CONFIG
: Required. The name or ID of the configuration that the version belongs to. To list available configurations, run ibmcloud sat config ls.

--version VERSION
: Required. The name or ID of your version. To list versions in your configuration, run ibmcloud sat config get --config <configuration_name_or_ID>.

--output JSON
: Optional. Displays the command output in JSON format.

--save-config
: Optional. Download and save the Kubernetes resource configuration file of the version to a temporary file.

-q
: Optional. Do not show the message of the day or update reminders.





 Example
With Kubernetes, you can enable [horizontal pod autoscaling](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/) to automatically increase or decrease the number of instances of your apps based on CPU.

To create an autoscaler and to define your policy, run the below command

kubectl autoscale deployment kubernetesnodeapp-deployment --cpu-percent=5 --min=1 --max=5

Once the autoscaler is successfully created, you should see horizontalpodautoscaler.autoscaling/<deployment-name> autoscaled.





 Step 8: Remove resources 



* Delete the horizontal pod autoscaler:

kubectl delete horizontalpodautoscaler.autoscaling/kubernetesnodeapp-deployment
* Delete the resources applied:

kubectl delete -f ingress-customdomain-https.yaml
kubectl delete -f ingress-customdomain-http.yaml
kubectl delete -f ingress-ibmsubdomain.yaml
* Delete the Kubernetes artifacts created for this application:

helm uninstall $MYAPP --namespace $KUBERNETES_NAMESPACE
* Delete the Kubernetes secret:

kubectl -n $KUBERNETES_NAMESPACE delete secret kubernetesnodeapp-api-key
* Delete the External Secrets Operator:

helm uninstall external-secrets
* Delete the service ID:

ibmcloud iam service-id-delete $SERVICE_ID
* Delete the cluster.







 Related content 



* [IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers)
* [Continuous Deployment to Kubernetes](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-continuous-deployment-to-kubernetescontinuous-deployment-to-kubernetes)
Kubernetes Service 



 Resources Data sources 

 <br><br> * [ibm_container_addons](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_addons)<br> * [ibm_container_alb](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_alb)<br> * [ibm_container_alb_cert](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_alb_cert)<br> * [ibm_container_alb_create](https://registry.terraform.io/providers/IBM-Cloud/ibm/1.37.0/docs/resources/container_alb_create)<br> * [ibm_container_api_key_reset](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_api_key_Reset)<br> * [ibm_container_bind_service](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_bind_service)<br> * [ibm_container_cluster](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_cluster)<br> * [ibm_container_cluster_feature](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_cluster_feature)<br> * [ibm_container_dedicated_host](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_dedicated_host)<br> * [ibm_container_dedicated_host_pool](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/container_dedicated_host_pool)<br> * [ibm_
In the following Kubernetes job, a curl pod makes an API request to IBM Cloud IAM to verify that the cluster's public key is exchanged for an IAM access token. Your app might call other IBM Cloud services that the trusted profile authorizes.

apiVersion: batch/v1
kind: Job
metadata:
name: token-exchange-job
namespace: default
spec:
template:
spec:
containers:
- name: curl
image: curlimages/curl:7.77.0
command: ["/bin/sh"]
args: ["-c", "curl -s -H "Content-Type: application/x-www-form-urlencoded" -H "Accept: application/json" -d grant_type=urn:ibm:params:oauth:grant-type:cr-token -d cr_token=$(cat /var/run/secrets/tokens/sa-token) -d profile_id=<profile_id> https://iam.cloud.ibm.com/identity/token"]
volumeMounts:
- mountPath: /var/run/secrets/tokens
name: sa-token
restartPolicy: Never
serviceAccountName: default
volumes:
- name: sa-token
projected:
sources:
- serviceAccountToken:
path: sa-token
expirationSeconds: 3600
audience: iam
Show more
4. Deploy the job.

kubectl apply -f exchange-job.yaml
5. Review the job details to verify it was successful.

kubectl describe job token-exchange-job
6. Review the output for the job completed and succeeded messages to verify the job was a success.
7. If the job succeeded, check your Activity Tracker global events in Frankfurt to verify the log line with details on the Trusted Profile request. If the job failed, review your configuration and try again.
KUBERNETES_PORT_443_TCP_ADDR=172.21.0.1
KUBERNETES_PORT_443_TCP_PORT=443
KUBERNETES_PORT_443_TCP_PROTO=tcp
KUBERNETES_SERVICE_HOST=172.21.0.1
KUBERNETES_SERVICE_PORT=443
KUBERNETES_SERVICE_PORT_HTTPS=443
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/
SHLVL=1
TARGET=My big literal secret
6. Resubmit the job run and specify to use the myliteralsecret2 secret for this job run.

ibmcloud ce jobrun resubmit --jobrun myjobrun --name myjobrunresubmit --env-from-secret myliteralsecret2

When you update a job or app with an environment variable that fully references a secret to fully reference a different secret, full references override other full references in the order in which they are set (the last referenced set overrides the first set).
7. Use the jobrun get command to display details of the job run, including the instances of the job run. Notice that the job run references both myliteralsecret and myliteralsecret2 secrets.

ibmcloud ce jobrun get --name myjobrunresubmit

Example output

Getting jobrun 'myjobrunresubmit'...
Getting instances of jobrun 'myjobrunresubmit'...
Getting events of jobrun 'myjobrunresubmit'...
[...]

Name: myjobrunresubmit
ID: 79f01367-932b-4a76-be18-b1e68790a85b
Project Name: myproject
Why does the Kubernetes dashboard terminate with an out of memory error? 

When listing pods in large clusters, the dashboard interface performs poorly and terminates in a OOMKilled error.

Last State: Terminated
Reason: OOMKilled
Exit Code: 137

The Kubernetes dashboard for your cluster requires a large amount of memory.

You can resolve this issue by changing the resource auto-refresh time interval to 60 for the Kubernetes dashboard.



 Changing the resource auto refresh time interval from the Kubernetes dashboard 



1. Select Settings in the navigation pane.
2. Set Resource auto-refresh time interval to 60.
3. Save







 Changing the resource auto refresh time interval from the command line 

[Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)



1. Edit your Kubernetes dashboard ConfigMap.

kubectl -n kube-system edit configmap kubernetes-dashboard-settings
2. In the data._global field, set the resourceAutoRefreshTimeInterval to 60. Example ConfigMap with resourceAutoRefreshTimeInterval set to 60.

apiVersion: v1
data:
_global: '{"clusterName":"mycluster","itemsPerPage":10,"logsAutoRefreshTimeInterval":5,"resourceAutoRefreshTimeInterval":60}'
kind: ConfigMap
metadata:
creationTimestamp: "2021-06-08T04:23:35Z"
labels:
addonmanager.kubernetes.io/mode: EnsureExists
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard-settings
namespace: kube-system
resourceVersion: "1253"
Configuring persistent volumes and persistent volume claims 



 Before you begin 

Before you begin, it is important to understand the Kubernetes concepts of a persistent volume (PV) and a persistent volume claim (PVC) and how they work together in a cluster. Review [Understanding Kubernetes storage basics](https://cloud.ibm.com/docs/openshift?topic=openshift-kube_concepts) for more information.





 Creating the PV and PVC 

Complete the following steps to create the PV and PVC on the NFS storage that was provisioned for your cluster:



1. In the login node, create a file (pvc.yml) and populate it with the following:

---
 Create a PV with your NFS shared folder.
apiVersion: v1
kind: PersistentVolume
metadata:
name: nfs-pv-hpcc
spec:
capacity:
storage: 100Gi
volumeMode: Filesystem
accessModes:
- ReadWriteMany
persistentVolumeReclaimPolicy: Recycle
storageClassName: nfs-sc-hpcc
mountOptions:
- hard
- nfsvers=4.1
nfs:
path: /data Shared folder of NFS server
server: 163.68.86.201 IP address of the NFS server

---
 Create a PVC from PV.
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: nfs-pvc-hpcc
namespace: hpcc Choose your own Namespace
spec:
accessModes:
- ReadWriteMany
storageClassName: nfs-sc-hpcc
resources:
requests:
storage: 100Gi
Show more
2. Before you create the PV and PVC, you need to update the following values in the pvc.yml file that you create:



* Replace the server IP address with the NFS storage node IP address.
You can override the default Kubernetes configuration file by setting the KUBECONFIG environment variable. This value is optional. The default value is false.

--name, -n
: The name of the project. This value is required if --id is not specified.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.





 Example 

ibmcloud ce project select --name myproject





 Example output 

Selecting project 'myproject'...
OK







 ibmcloud ce project tag 

Manages the tags of a single project.

ibmcloud ce project tag (--name PROJECT_NAME | --id PROJECT_ID) [--quiet] [--tag TAG] [--tag-rm TAG_RM]



 Command Options 

--id, --guid
: The ID of the project. This value is required if --name is not specified.

--name, -n
: The name of the project. This value is required if --id is not specified.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.

--tag, -t
: A label to assign to your project. The label must be 128 characters or fewer and can contain letters, numbers, spaces ( ), periods (.), colons (:), underscores (_), and hyphens (-). Specify one label per --tag option; for example, --tag tagA --tag tagB. This value is optional.

--tag-rm, --trm
: Remove a label assigned to your project. Specify one label per --tag-rm option; for example, --tag-rm tagA --tag-rm tagB. This value is optional.





 Example 

ibmcloud ce project tag --name myproject --tag tag1 --tag tag2





 Example output
Kubernetes Service 1.20 end of support date change
: The end of support date of Kubernetes Service 1.20 is now March 2022. The [Kubernetes version information and update actions](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionscs_versions_available) page has been updated with the new date.





 4 January 2022 

Worker node fix pack update
: Change log documentation is available for worker node versions [4.8.24_1540_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_484824_1540),[4.7.40_1545_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_474740_1545), [4.6.52_1568_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_464652_1568), and [3.11.570_1617_openshift](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_changelog_311311570_1617).







 December 2021 

Review the release notes for December 2021.



 20 December 2021 

Worker node fix pack update
For instructions on how to update Kubernetes, see [Updating clusters, worker nodes, and cluster components](https://cloud.ibm.com/docs/containers?topic=containers-updateupdate). For the list of IBM Cloud Kubernetes Service supported versions and expiration dates see the [release history](https://cloud.ibm.com/docs/containers?topic=containers-cs_versionsrelease-history).

You must wait for the update to complete before you can [resume the IBM Blockchain Platform deployment](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-deploy-iks-icibp-v2-deploy-iks-steps).





 How to assign Kubernetes access roles 

The user who links the blockchain service instance to the Kubernetes cluster must have the Administrator and Manager roles in Kubernetes. To configure this access you must complete the following steps:

1. In the IBM Cloud dashboard, click the Manage drop-down list, then Access (IAM).
2. In the left navigation menu, click Users and click the ID of user who will link the service instance to the Kubernetes cluster.
3. Click Access Policies, then Assign access.
4. Click the tile Assign access to resources.
5. In the Services drop-down list, select Kubernetes Service.
6. Check the Administrator and Manager roles for this user.
7. Click Assign.

For more information about Kubernetes access control, see [how to pick the right access policy and role for your users](https://cloud.ibm.com/docs/containers?topic=containers-userschecking-perms).





 Post-install instructions 

After you deploy your console, you can click the Launch the IBM Blockchain Platform button to open the console in your browser. You can add the console URL as a bookmark to your browser.



 Returning to your console from IBM Cloud 

If you don't have the console URL, you can find it from your IBM Cloud dashboard.
: Kubernetes [1.23.4_1521](https://cloud.ibm.com/docs/containers?topic=containers-changelog_1231234_1521), [1.22.7_1542](https://cloud.ibm.com/docs/containers?topic=containers-changelog_1221227_1542), [1.21.10_1551](https://cloud.ibm.com/docs/containers?topic=containers-changelog_12112110_1551), [1.20.15_1572](https://cloud.ibm.com/docs/containers?topic=containers-changelog_12012015_1572), and [1.19.16_1579](https://cloud.ibm.com/docs/containers?topic=containers-changelog_11911916_1579).





 24 February 2022 

Container service CLI
: The [CLI change log](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelog) is updated for version 1.0.374.

Kubernetes Ingress image
: Versions 1.1.1_1996_iks, 1.0.3_1995_iks, and 0.49.3_1994_iks of the [Kubernetes Ingress image](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog) are released.





 23 February 2022 

Cluster autoscaler
: Version [1.0.4_410](https://cloud.ibm.com/docs/containers?topic=containers-ca_changelog) is available.

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





 18 February 2022 

Container service CLI
Kubernetes v1.19.7 v1.19.8 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.19.8). 
 Load balancer and load balancer monitor for IBM Cloud Provider 1078 1165 Updated to run as a non-root user by default, with privileged escalation as needed. Updated to use Go version 1.15.7. 
 Operator Lifecycle Manager 0.16.1-IKS-3 0.16.1-IKS-5 Updated image for [CVE-2021-23839](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23839), [CVE-2021-23840](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23840), and [CVE-2021-23841](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23841). 







 Change log for worker node fix pack 1.19.7_1535, released 15 February 2021 

The following table shows the changes that are in the worker node fix pack 1.19.7_1535. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.19.7_1534

 Component Previous Current Description
Kubernetes v1.24.2 v1.24.3 See the [Kubernetes release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.24.3). 
 Kubernetes NodeLocal DNS cache 1.22.2 1.22.5 See the [Kubernetes NodeLocal DNS cache release notes](https://github.com/kubernetes/dns/releases/tag/1.22.5). 
 Load balancer and load balancer monitor for IBM Cloud Provider 1998 2058 Updated image for [CVE-2022-2097](https://nvd.nist.gov/vuln/detail/CVE-2022-2097). 
 Portieris admission controller v0.12.4 v0.12.5 See the [Portieris admission controller release notes](https://github.com/IBM/portieris/releases/tag/v0.12.5). 







 Change log for worker node fix pack 1.24.2_1529, released 18 July 2022 

The following table shows the changes that are in the worker node fix pack 1.24.2_1529. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.24.2_1527

 Component Previous Current Description
Kubernetes N/A N/A N/A 







 Change log for worker node fix pack 1.24.2_1527, released 05 July 2022 

The following table shows the changes that are in the worker node fix pack 1.24.2_1527. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.24.2_1526

 Component Previous Current Description 

 Ubuntu 18.04 packages 4.15.0-187 4.15.0-188 Worker node kernel & package updates for [CVE-2022-1292](https://nvd.nist.gov/vuln/detail/CVE-2022-1292), [CVE-2022-2068](https://nvd.nist.gov/vuln/detail/CVE-2022-2068), [CVE-2022-2084](https://nvd.nist.gov/vuln/detail/CVE-2022-2084), [CVE-2022-28388](https://nvd.nist.gov/vuln/detail/CVE-2022-28388), [CVE-2022-32206](https://nvd.nist.gov/vuln/detail/CVE-2022-32206), [CVE-2022-32208](https://nvd.nist.gov/vuln/detail/CVE-2022-32208). 
 Kubernetes N/A N/A N/A 







 Change log for master fix pack 1.24.2_1526, released 22 June 2022 

The following table shows the changes that are in the master fix pack 1.24.2_1526. Master patch updates are applied automatically.



Changes since version 1.24.1_1523

 Component Previous Current Description 

 IBM Cloud Block Storage driver and plug-in v2.2.4 v2.2.6 Bug fixes for the driver installation.