vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If you attached hosts that are not showing up as available, see [Debugging host health](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-hosts-debug).





 R0023, R0101: Wait for location to be ready 

Location message
: R0023: Wait while Satellite sets up the location control plane.
: R0101: The Satellite location has clusters in the middle of an operation. Wait for them to finish and check back later.

Steps to resolve
: Wait for the location control plane to finish setting up and check back later.





 R0024, R0025: Cluster issues 

Location message
: R0024: The Satellite location has Red Hat OpenShift clusters in warning health.
: R0025: The Satellite location has Red Hat OpenShift clusters in critical health.

Steps to resolve
: 

1. Wait to see if another message is returned, such as a message about host capacity.
2. If a host message is returned, try [Debugging hosts](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-hosts-debug).
3. If no further message is returned, try [Debugging your Red Hat OpenShift on IBM Cloud clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_clusters).







 R0026: Host disk space 

Location message
: R0026: Hosts in the location control plane are running out of disk space. Assign more hosts to the location control plane or reload the hosts with disk space issues.

Steps to resolve
: 

1. List the hosts that are assigned to the control plane. by running ibmcloud sat host ls --location <location_name_or_ID> | grep infrastructure.
2. Check the details of the hosts by running ibmcloud sat host get --host <host_ID> --location <location_name_or_ID>.
3. In the infrastructure provider for the host, check the disk space of your host machine.
* If the error message has a broken webhook, replace trust.hooks.securityenforcement.admission.cloud.ibm.com with the broken webhook that you previously identified.

oc get mutatingwebhookconfigurations,validatingwebhookconfigurations -o jsonpath='{.items[?(@.webhooks].name=="trust.hooks.securityenforcement.admission.cloud.ibm.com")].metadata.name}{"n"}'

Example output

image-admission-config
* If the error does not have a broken webhook, list all the webhooks in your cluster and check their configurations in the following steps.

oc get mutatingwebhookconfigurations,validatingwebhookconfigurations



3. Review the service and location details of the mutating or validating webhook configuration in the clientConfig section in the output of the following command. Replace image-admission-config with the name that you previously identified. If the webhook exists outside the cluster, contact the cluster owner to check the webhook status.

oc get mutatingwebhookconfiguration image-admission-config -o yaml

oc get validatingwebhookconfigurations image-admission-config -o yaml

Example output

clientConfig:
caBundle: <redacted>
service:
name: <name>
namespace: <namespace>
path: /inject
port: 443
4. Optional: Back up the webhooks, especially if you don't know how to reinstall the webhook.

oc get mutatingwebhookconfiguration <name> -o yaml > mutatingwebhook-backup.yaml

oc get validatingwebhookconfiguration <name> -o yaml > validatingwebhook-backup.yaml
5. Check the status of the related service and pods for the webhook.



1.
Pinging with a source of 10.177.137.251 to 172.16.100.2, the traffic leaves through dp0bond1, fails to transit the tunnel, and never matches the NAT rules properly. The static route fixes this:

K > 172.16.100.0/24 via 169.63.66.49, dp0bond1
S > 172.16.100.2/32 [1/0] is directly connected, vfp0

This creates a more specific route for the traffic to take through vfp0.

At this point, NAT works as configured, and the traffic travels through the tunnel.

NAT requires a route with a CIDR smaller than the IPsec remote prefix (it cannot be the same size) pointing your traffic over the vfp0 virtual interface.

After everything is in place, you can ping and verify:

[root@acs-jmat-migserver ] ping 172.16.100.1
PING 172.16.100.1 (172.16.100.1) 56(84) bytes of data.
64 bytes from 172.16.100.1: icmp_seq=1 ttl=63 time=44.7 ms
64 bytes from 172.16.100.1: icmp_seq=2 ttl=63 time=44.2 ms
64 bytes from 172.16.100.1: icmp_seq=3 ttl=63 time=44.3 ms
^C
--- 172.16.100.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 44.247/44.431/44.727/0.272 ms

vyatta@acs-jmat-migsim01:$ show nat source translations
Pre-NAT Post-NAT Prot Timeout
10.177.137.251:7553 172.16.200.2:7553 icmp 48
As cluster resource SAPHana_${SID}_${INSTNO} is configured with AUTOMATED_REGISTER=true, SAP HANA restarts when NODE1 joins the cluster and the former primary is registered as secondary.

Then, rerun the steps in [Test2 - Test the manual move of SAPHana resource to another node](https://cloud.ibm.com/docs/sap?topic=sap-ha-rhel-hana-sr-cost-optimizedha-rhel-hana-sr-co-test2-manual-move) to revert to the initial situation.







 Test4 - Testing failure of the secondary database instance 

Use the following information to test the failure of the secondary database instance.



 Test4 - Description 

Simulate a crash of the secondary HANA database.





 Test4 - Prerequisites 



* A functional two-node RHEL HA Add-On cluster for HANA system replication.
* Both nodes active.
* Cluster is started on NODE1 and NODE2.
* Cluster Resource SAPHana_${SID}_${INSTNO} is configured with AUTOMATED_REGISTER=true.
* Check SAP HANA System Replication status:



* The primary SAP HANA database is running on NODE1.
* The secondary SAP HANA database is running on NODE2.
* HANA System Replication is activated and sync.









 Test4 - Test Procedure 

Crash SAP HANA secondary by sending a SIGKILL signal as user ${sid}adm.

On NODE2, run the following command.

sudo -i -u ${sid}adm -- HDB kill-9





 Test4 - Expected behavior 



* SAP HANA secondary on NODE2 crashes.
* The cluster detects the stopped secondary HANA database and marks the resource as failed.
* The cluster restarts the secondary HANA database.
* The cluster detects that the system replication is in sync again.







 Test4 - Recovery Procedure 

Wait until the secondary HANA instance starts and synchronized again (SOK), then cleanup the failed resource actions as shown in pcs status.

On NODE2, run the following command.

pcs resource refresh SAPHana_${SID}_${INSTNO}

pcs status --full
Start by checking for error messages in the Ingress resource deployment events and ALB pod logs. These error messages can help you find the root causes for failures and further debug your Ingress setup in the next sections.



1. Check your Ingress resource deployment and look for warnings or error messages.

kubectl describe ingress <myingress>

In the Events section of the output, you might see warning messages about invalid values in your Ingress resource or in certain annotations that you used. Check the [Ingress resource configuration documentation](https://cloud.ibm.com/docs/containers?topic=containers-managed-ingress-setup) or the [annotations documentation](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotations).

NAME: myingress
Namespace: default
Address: 169.xx.xxx.xxx,169.xx.xxx.xxx
Default backend: default-http-backend:80 (<none>)
Rules:
Host Path Backends
---- ---- --------
mycluster-<hash>-0000.us-south.containers.appdomain.cloud
/tea myservice1:80 (<none>)
/coffee myservice2:80 (<none>)
Annotations:
custom-port: protocol=http port=7490; protocol=https port=4431
location-modifier: modifier='' serviceName=myservice1;modifier='^' serviceName=myservice2
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Success 1m public-cr87c198fcf4bd458ca61402bb4c7e945a-alb1-258623678-gvf9n Successfully applied ingress resource.
Review the following outbound network requirements for RHEL and RHCOS hosts for use with RHCOS enabled locations in the Sydney (au-syd) region.

Allow access to Red Hat network time protocol (NTP) servers.
: 

* Destination hostnames: 0.rhel.pool.ntp.org, 1.rhel.pool.ntp.org, 2.rhel.pool.ntp.org, 3.rhel.pool.ntp.org
* Protocol and ports: Allow NTP protocol and provide UDP on port 123



: If you don't want to use Red Hat network time protocol (NTP) servers, you can instead define a [custom NTP server for your RHCOS hosts](https://cloud.ibm.com/docs/satellite?topic=satellite-config-custom-ntp).

Allow hosts to communicate with Red Hat Container Registry.
: Allow your hosts to access the required sites for OpenShift Container Platform. For more information, see [Configuring your firewall](https://docs.openshift.com/container-platform/4.8/installing/install_config/configuring-firewall.html).

Allow control plane worker nodes to communicate with the control plane master.
: 

* Destination IP addresses: 168.1.27.26,130.198.65.146,135.90.87.90
* Destination hostnames: c114.au-syd.satellite.cloud.ibm.com, c114-1.au-syd.satellite.cloud.ibm.com, c114-2.au-syd.satellite.cloud.ibm.com, c114-3.au-syd.satellite.cloud.ibm.com, c114-e.au-syd.satellite.cloud.ibm.com
* Protocol and ports: TCP 30000 - 32767



Allow hosts to be attached to a location and assigned to services in the location.
: 

* Destination IP addresses: 130.198.66.26, 135.90.69.66, 168.1.8.195
yq version 3.4.1

 yq4 --version
yq (https://github.com/mikefarah/yq/) version v4.30.5

 kubectl version --client
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.3", GitCommit:"aef86a93758dc3cb2c658dd9657ab4ad4afc21cb", GitTreeState:"clean", BuildDate:"2022-07-13T14:30:46Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4

 buildctl --version
buildctl github.com/moby/buildkit v0.10.6 0c9b5aeb269c740650786ba77d882b0259415ec7

 helm version --client
Client: &version.Version{SemVer:"v2.17.0", GitCommit:"a690bad98af45b015bd3da1a41f6218b1a451dbe", GitTreeState:"clean"}

 helm3 version --client
version.BuildInfo{Version:"v3.10.2", GitCommit:"50f003e5ee8704ec937a756c646870227d7c8b58", GitTreeState:"clean", GoVersion:"go1.18.8"}

 ibmcloud -version
ibmcloud version 2.13.0+05fd406-2022-11-30T20:39:15+00:00
yq version 3.4.1

 yq4 --version
yq (https://github.com/mikefarah/yq/) version v4.30.8

 kubectl version --client
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.3", GitCommit:"aef86a93758dc3cb2c658dd9657ab4ad4afc21cb", GitTreeState:"clean", BuildDate:"2022-07-13T14:30:46Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4

 buildctl --version
buildctl github.com/moby/buildkit v0.11.0 830288a71f447b46ad44ad5f7bd45148ec450d44

 helm version --client
Client: &version.Version{SemVer:"v2.17.0", GitCommit:"a690bad98af45b015bd3da1a41f6218b1a451dbe", GitTreeState:"clean"}

 helm3 version --client
version.BuildInfo{Version:"v3.10.3", GitCommit:"835b7334cfe2e5e27870ab3ed4135f136eecc704", GitTreeState:"clean", GoVersion:"go1.18.9"}

 ibmcloud -version
ibmcloud version 2.13.0+05fd406-2022-11-30T20:39:15+00:00
yq version 3.4.1

 yq4 --version
yq (https://github.com/mikefarah/yq/) version 4.27.2

 kubectl version --client
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.3", GitCommit:"aef86a93758dc3cb2c658dd9657ab4ad4afc21cb", GitTreeState:"clean", BuildDate:"2022-07-13T14:30:46Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4

 buildctl --version
buildctl github.com/moby/buildkit v0.10.3 c8d25d9a103b70dc300a4fd55e7e576472284e31

 helm version --client
Client: &version.Version{SemVer:"v2.17.0", GitCommit:"a690bad98af45b015bd3da1a41f6218b1a451dbe", GitTreeState:"clean"}

 helm3 version --client
version.BuildInfo{Version:"v3.9.4", GitCommit:"dbc6d8e20fe1d58d50e6ed30f09a04a77e4c68db", GitTreeState:"clean", GoVersion:"go1.17.13"}

 ibmcloud -version
ibmcloud version 2.10.0+e37e09e-2022-08-24T17:31:27+00:00
* Remove support for .NET Core runtime version 1.0.1
* Remove support for .NET Core SDK version 1.0.0-preview2-1-003177
* Add staging_task.log file to app container
* Lower disk usage when caching dependencies







 12 June 2017 

Updated Liberty buildpack v3.10-20170525-1107
: The default Liberty runtime version was updated to the 17.0.0.2 release.



* The monthly Liberty runtime version was updated to the [2017.5.0.0](https://developer.ibm.com/wasdev/blog/2017/05/12/beta-websphere-liberty-tools-may-2017/) release.
* The Node.js runtime that is used by the [App Management utility](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-app_management) was updated to the 6.10.0 version.
* The buildpack also provides an updated version of the Extreme Scale Client.







 12 May 2017 

Updated ASP.NET Core buildpack v1.0.18-20170516-1601
: This release includes the following updates:



* Add support for .NET Core runtime 1.0.5
* Add support for .NET Core runtime 1.1.2
* Add support for .NET Core SDK 1.0.3
* Add support for .NET Core SDK 1.0.4
* Update Node version to 6.10.2
* Remove support for .NET Core SDK 1.0.1
* Remove support for .NET Core SDK 1.0.0-preview4-004233
* Use ASPNETCORE_URLS environment variable to specify port







 5 May 2017 

Updated Node.js buildpack v3.12
: The SDK for Node.js buildpack v3.12 provides IBM SDK for Node.js versions 0.12.17, 0.12.18, 4.8.0, 4.8.2, 6.10.0 and 6.10.2.
* [Version 4.13.0, release 10 July 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-odf_addon_changelog4.13.0_odf)



* [Version 4.12](https://cloud.ibm.com/docs/openshift?topic=openshift-odf_addon_changelog4.12_odf)



* [Version 4.12.6, release 28 June 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-odf_addon_changelog4.12.6_odf)
* [Version 4.12.5, release 09 June 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-odf_addon_changelog4.12.5_odf)
* [Version 4.12.4, release 05 May 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-odf_addon_changelog4.12.4_odf)
* [Version 4.12.0, released 16 March 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-odf_addon_changelog4.12.0_odf)



* [Version 4.11](https://cloud.ibm.com/docs/openshift?topic=openshift-odf_addon_changelog4.11_odf)



* [Version 4.11.12, release 28 June 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-odf_addon_changelog4.11.12_odf)
* [Version 4.11.11, release 09 June 2023](https://cloud.ibm.com/docs/openshift?topic=openshift-odf_addon_changelog4.11.11_odf)
: For more information, see the [Istio security bulletin 2021-008](https://istio.io/latest/news/security/istio-security-2021-008/).





 Change log for 1.10.3, released 5 August 2021 

Review the changes that are in version 1.10.3 of the managed Istio add-on.

Previous version
: 1.10.2

Current version
: 1.10.3

Updates in this version
: See the Istio release notes for [Istio 1.10.3](https://istio.io/latest/news/releases/1.10.x/announcing-1.10.3/.).





 Change log for 1.10.2, released 15 July 2021 

Review the changes that are in version 1.10.2 of the managed Istio add-on.

Previous version
: 1.9.5

Current version
: 1.10.2

Updates in this version
: See the Istio release notes for:



* [Istio 1.10.0](https://istio.io/latest/news/releases/1.10.x/announcing-1.10/)
* [Istio 1.10.1](https://istio.io/latest/news/releases/1.10.x/announcing-1.10.1/)
* [Istio 1.10.2](https://istio.io/latest/news/releases/1.10.x/announcing-1.10.2/).



: The API version of the IstioOperator (IOP) custom resource definition is updated from v1beta1 to v1. Although this update does not impact existing custom IOP resources, you can optionally back up your IOP resources before upgrading to Istio version 1.10.
: The IstioOperator deployment is now created by the Istio add-on instead of the Operator Lifecycle Manager (OLM).
* The alternate Liberty runtime GA version was changed to the 20.0.0.8 release.
* The IBM JRE version was updated to 8 SR6 FP11.
* The AdoptOpenJDK OpenJ9 alternate JRE was updated to version 11.0.8_10_openj9-0.21.0.







 7 July 2020 

Updated Liberty buildpack v3.46-20200626-1029
: The default Liberty runtime GA version is the [20.0.0.6](https://openliberty.io/blog/2020/06/05/graphql-open-liberty-20006.html) release.



* The alternate Liberty runtime GA version was changed to [20.0.0.7](https://openliberty.io/blog/2020/07/02/disable-default-cookies-20007.html) release.







 18 June 2020 

Updated the ASP.NET Core buildpack v2.7-20200615-1457
: This release includes version 2.3.11 of the dotnet-core Cloud Foundry buildpack.



* Add support for .NET ASP.NET Core 2.1.18
* Add support for .NET ASP.NET Core 3.1.4
* Add support for .NET Runtime 3.1.4
* Add support for .NET SDK 2.1.701
* Add support for .NET SDK 2.1.806
* Add support for .NET SDK 3.1.202
* Remove support for .NET ASP.NET Core 3.1.2
* Remove support for .NET ASP.NET Core 2.1.16
* Remove support for .NET Runtime 2.1.16
* Remove support for .NET SDK 2.1.804
* Remove support for .NET SDK 3.1.200
* Update Node.js version to 10.21.0







 8 June 2020 

Updated Node.js buildpack v4.3-20200606-1928
* [Change log for version 5.1.8_1970, released 15 May 2023](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog5.1.8_1970_is_block_relnote)
* [Change log for version 5.1.6_1872, released 05 April 2023](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog5.1.6_1872_is_block_relnote)
* [Change log for version 5.1.5_1857, released 29 March 2023](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog5.1.5_1857_is_block_relnote)
* [Change log for version 5.1.4_1852, released 07 March 2023](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog5.1.4_1852_is_block_relnote)
* [Change log for version 5.1.2_1828, released 21 February 2023](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog5.1.2-1828_is_block_relnote)
* [Change log for version 5.1, released 9 February 2023](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog5.1_is_block_relnote)



* [Version 5.0](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog050_is_block)



* [Change log for version 5.0.16_127, released 21 June 2023](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog5.0.16_127_is_block_relnote)
4.5.0 4.5.0 4.6.29 or later 
 4.0.9 4.0.9 4.8 
 4.0.9 4.0.9 4.6.29 or later 
 4.0.8 4.0.8 4.8 
 4.0.8 4.0.8 4.6.29 or later 
 4.0.7 4.0.7 4.8 
 4.0.7 4.0.7 4.6.29 or later 
 4.0.6 4.0.6 4.8 
 4.0.6 4.0.6 4.6.29 or later 
 4.0.5 4.0.5 4.8 
 4.0.5 4.0.5 4.6.29 or later 
 4.0.4 4.0.4 4.8 
 4.0.4 4.0.4 4.6.29 or later 
 4.0.3 4.0.3 4.8 
 4.0.3 4.0.3 4.6.29 or later 
 4.0.2 4.0.2 4.8 
 4.0.2 4.0.2 4.6 
 4.0.0 4.0.0 4.6 
 2.2.1 3.5.0 4.5, 4.6 
 2.2.1 3.5.0 3.11.188 
 2.2.1 3.0.1 4.5, 4.6 
 2.2.1 3.0.1 3.11.188 
 2.2.0 3.5.0 4.5 
 2.2.0 3.5.0 3.11.188 
 2.2.0 3.0.1 4.5 
 2.2.0 3.0.1 3.11 
 2.1.4 3.0.1 3.11.188 
 2.1.4 2.5 3.11 
 2.1.3 3.0.1 3.11.188 
 2.1.3 2.5 3.11
version.BuildInfo{Version:"v3.10.2", GitCommit:"50f003e5ee8704ec937a756c646870227d7c8b58", GitTreeState:"clean", GoVersion:"go1.18.8"}

 ibmcloud -version
ibmcloud version 2.13.0+05fd406-2022-11-30T20:39:15+00:00

 ibmcloud plugin list
Listing installed plug-ins...

Plugin Name Version Status Private endpoints supported
cloud-functions[wsk/functions/fn] 1.0.62 false
cloud-internet-services[cis] 1.14.9 true
code-engine[ce] 1.40.3 true
container-registry[cr] 1.0.5 true
container-service[kubernetes-service/ks] 1.0.480 false
cra 1.0.7 false
doi 0.4.1 false
schematics 1.12.5 true

 ibmcloud dev --version
ibmcloud dev version 2.16.0

 java -version
openjdk version "11.0.17" 2022-10-18
IBM Semeru Runtime Open Edition 11.0.17.0 (build 11.0.17+8)
Eclipse OpenJ9 VM 11.0.17.0 (build openj9-0.35.0, JRE 11 Linux amd64-64-Bit Compressed References 20221031_559 (JIT enabled, AOT enabled)
OpenJ9 - e04a7f6c1
OMR - 85a21674f
JCL - a94c231303 based on jdk-11.0.17+8)

 ant -version
Apache Ant(TM) version 1.10.12 compiled on October 13 2021

 mvn -version
Change log for patch update 1.1.0_1066, released 15 May 2023 



* Image tags: 1.21.0 110-9, 1.22.0 110-9, 1.23.0 110-9, 1.24.0 110-9, 1.25.0 110-9
* Resolves issues while reading secrets.







 Change log for patch update 1.1.0_1060, released 26 April 2023 



* Image tags: 1.19.1 110-8, 1.20.0 110-8, 1.21.0 110-8, 1.22.0 110-8, 1.23.0 110-8.
* Updates golang version to 1.19.8.
* Adds support for Satellite cluster versions 4.11 and 4.12.







 Change log for patch update 1.1.0_978, released 16 March 2023 



* Image tags: 1.19.1 110-6, 1.20.0 110-6, 1.21.0 110-6, 1.22.0 110-6, 1.23.0 110-6.
* Updates golang version to 1.19.6.







 Change log for patch update 1.1.0_897, released 9 January 2023 



* Image tags: 1.19.1 110-5, 1.20.0 110-5, 1.21.0 110-5, 1.22.0 110-5, 1.23.0 110-5.
* Golang updated to 1.18.9
* Updates the storage-secret-sidecar image to v1.2.14
* [Change log for 1.11.4, released 2 November 2021](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog1114)
* [Change log for 1.11.3, released 7 October 2021](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog1113)
* [Change log for 1.11.2, released 23 September 2021](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog1112)
* [Change log for 1.11.1, released 31 August 2021](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog1111)



* [Version 1.10 (unsupported)](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelogv110)



* [Change log for 1.10.6, released 13 January 2022](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog1106)
* [Change log for 1.10.5, released 28 October 2021](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog1105)
* [Change log for 1.10.4, released 14 September 2021](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog1104)
* [Change log for 1.10.3, released 5 August 2021](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog1103)
* [Change log for 1.10.2, released 15 July 2021](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog1102)



* [Version 1.9 (unsupported)](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelogv19)
* [Change log for version 5.0.7_1836, released 21 February 2023](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog5.0.7-1836_is_block_relnote)
* [Change log for version 5.0.5_1784, released 24 January 2023](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog5.0.5-1784_is_block_relnote)
* [Change log for version 5.0.4_1773, released 10 January 2023](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog5.0.4-1773_is_block_relnote)
* [Change log for version 5.0.2_1713, released 17 November 2022](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog5.0.2-1713_is_block_relnote)
* [Change log for version 5.0.1_1695, released 9 November 2022](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog5.0.1-1695_is_block_relnote)
* [Change log for version 5.0, released 11 October 2022](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog5.0_is_block_relnote)
* [Change log for version 5.0.4-beta_1566, released 14 July 2022](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog5.0.4-beta_1556_is_block_relnote)