vania-janet/multiturn-rag-retrieval-data huggingface dataset:
hardware_handler "1 alua"
rr_weight uniform
rr_min_io 128
}
}
Show more
* Ubuntu has multipath configuration that is built into multipath-tools. However, the built-in configuration uses a "service-time 0" load-balancing policy, which can leave your connection vulnerable to interruptions. Create a multipath.conf file and update it as follows.

defaults {
user_friendly_names no
max_fds max
flush_on_last_del yes
queue_without_daemon no
dev_loss_tmo infinity
fast_io_fail_tmo 5
}
 All data in the following section must be specific to your system.
blacklist {
wwid "SAdaptec"
devnode "^hd[a-z]"
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]"
devnode "^cciss."
}
devices {
device {
vendor "NETAPP"
product "LUN"
path_grouping_policy group_by_prio
features "2 pg_init_retries 50"
no_path_retry queue
prio "alua"
path_checker tur
failback immediate
path_selector "round-robin 0"
hardware_handler "1 alua"
rr_weight uniform
rr_min_io 128
}
}
Show more



* Restart multipathd service so that the changes take effect.

systemctl multipathd restart





3. Load the multipath module, start multipath services, and set it start on boot.



* RHEL 6

modprobe dm-multipath

service multipathd start

chkconfig multipathd on
* CentOS 7

modprobe dm-multipath

systemctl start multipathd

systemctl enable multipathd
* Ubuntu

service multipath-tools start
[Image of download certificate](https://cloud.ibm.com/docs-content/v1/content/3a120b16db5fdc3e70d071af8a63ce5515c1b096/mqcloud/images/mqoc_tls_qmdowncert.png)





Additional step for M1 Macs with ARM Processors:

This information is relevant from version 9.3.1 onwards where there was a change in how to connect to a Queue Manager with TLS.

For background the MQ MacOS toolkit makes use of native MQ client libraries delivered as universal binaries to support both x86 and Arm64. Whilst the toolkit itself consists of universal binaries it has a downstream dependency for encryption. For x86 the toolkit uses GSKit, for Arm64 it uses OpenSSL and this requires a .pem formatted truststore for TLS.

This means that is there is currently an additional requirement to export the following environment variable:



1. export MQSSLKEYR=<path_to_your_pem_file>/qmgrcert.pem







 Step 6: Create a trust store and import the queue manager's public key 

The following command creates a key database our application can use as a trust store. Navigate to the same folder as the JMS application and execute this command:

In Windows and Linux environments only:



1. run ikeycmd -keydb -create -db <trustStoreName>.jks -pw <trustStorePassword> -type jks -expire 0 where:



* <trustStorePassword> - choose a password and remember it for future use.



2. To add the certificate to the new trust store run ikeycmd -cert -add -db <trustStoreName>.jks -file qmgrcert.pem -label qmgrcert -pw <trustStorePassword>



In Mac OSX environments, run keytool -importcert -file qmgrcert.pem -alias qmgrcert -keystore <trustStoreName>.jks -storepass <trustStorePassword>
-c:a acc Use the acc audio codec for the output. 
 -ar 48000 Set the audio sample rate to 48000 Hz for the output. 
 -b:a 128k Set the audio bit rate to 128000 bits/second for the output. 
 -c:v h264 Use the h.264 video codec for the output. 
 -profile:v main Use the "main" format profile of the selected codec for widest device support. 
 -crf 23 Attempt to maintain the video quality with varying file size and bit rate. <br>The lower the CRF, the higher the quality and file size. 
 -g 61 -keyint_min 61 Set a maximum and minimum. <br>With the example source frame rate as 30.30, a keyframe should be <br>inserted every 2 seconds (61 frames). 
 -sc_threshold 0 Disable scene detection by ffmpeg. <br>Prevents a second process that might insert extraneous keyframes into the output. 
 -b:v 5300k Sets the output video stream's target bit rate to 5300000 bits/second. 
 -maxrate 5300k Limits the maximum output video bit rate at <br>the encoder to 5300000 bits/second, in case it varies. 
 -bufsize 10600k Sets the ffmpeg video decoder buffer size to 10600000 bits. <br>With 5300k bit rate, the ffmpeg encoder should check and <br>attempt to readjust the output bit rate back to the target bit rate for every 2 seconds of video. 
 -hls_time 6 Attempt to target each output video fragment length to 6 seconds. <br>Accumulates frames for at least 6 seconds of video, and then <br>stops to break off a video fragment when it encounters the next keyframe. 
 -hls_playlist_type vod Prepares the output .m3u8 playlist file for Video on Demand (VOD). 
 test-video.m3u8 Name the output playlist/manifest file to test-video.m3u8.
seed_simulator=3531074553, metadata={'parallel_state_update': 16, 'parallel_shots': 1,
'sample_measure_time': 0.000405246, 'noise': 'ideal', 'batched_shots_optimization': False,
'remapped_qubits': False, 'device': 'CPU', 'active_input_qubits': 0, 1, 2, 3], 'measure_sampling': True,
'num_clbits': 4, 'input_qubit_map': 3, 3], 2, 2], 1, 1], 0, 0]], 'num_qubits': 4, 'method': 'statevector',
'fusion': {'applied': False, 'max_fused_qubits': 5, 'threshold': 14, 'enabled': True}}, time_taken=0.001981756)],
date=2023-02-27T12:38:18.580995, status=COMPLETED, header=QobjHeader(backend_name='aer_simulator_statevector',
backend_version='0.11.2'), metadata={'mpi_rank': 0, 'num_mpi_processes': 1, 'num_processes_per_experiments': 1,
'time_taken': 0.002216379, 'max_gpu_memory_mb': 0, 'time_taken_execute': 0.002005713, 'max_memory_mb': 65536,
'time_taken_load_qobj': 0.000200642, 'parallel_experiments': 1, 'omp_enabled': True},
time_taken=0.0025920867919921875)
Show more

Now let's get the probability distribution from the output:

counts = result.get_counts(circuit)
quasi_dists = {}
for key,count in counts.items():
* [Revision 19, released 20 February 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-odf-remoteodf-remote-4.7-rev-19-change-log)





[ridge-csi-driver change log](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-ridge-csi-drivercl-ridge-csi-driver)



* [Version 1.0.0](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-ridge-csi-driver1.0.0-change-log)



* [Revision 1, released 11 October 2022](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-ridge-csi-driverridge-csi-driver-1.0.0-rev-1-change-log)





[vsphere-csi-driver change log](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-vsphere-csi-drivercl-vsphere-csi-driver)



* [Version 2.5.1](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-vsphere-csi-driver2.5.1-change-log)



* [Revision 6, released 20 February 2023](https://cloud.ibm.com/docs/satellite?topic=satellite-cl-vsphere-csi-drivervsphere-csi-driver-2.5.1-rev-6-change-log)











 FAQs 

[FAQs](https://cloud.ibm.com/docs/satellite?topic=satellite-faqsfaqs)



* [What is IBM Cloud Satellite and how does it work?](https://cloud.ibm.com/docs/satellite?topic=satellite-faqswhat-is-satellite)
* [Where is Satellite available?](https://cloud.ibm.com/docs/satellite?topic=satellite-faqssatellite-locations)
Verify that your new project is created with the [project get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project-get) command.

ibmcloud ce project get --name PROJECT_NAME

Example output

Getting project 'myproject'...
OK
Name: myproject
ID: 01234567-abcd-abcd-abcd-abcdabcd1111
Status: active
Selected: true
Region: us-south
Resource Group: default
Service Binding Service ID: ServiceId-1234abcd-abcd-abcd-1111-1a2b3c4d5e6f
Age: 52d
Created: Fri, 15 Jan 2021 13:32:30 -0500
Updated: Fri, 15 Jan 2021 13:32:45 -0500

Quotas:
Category Used Limit
App revisions 1 100
Apps 1 100
Build runs 0 100
Builds 0 100
Configmaps 2 100
CPU 1.025 64
Ephemeral storage 902625Ki 256G
Instances (active) 1 250
Instances (total) 2 2500
Job runs 1 100
Jobs 1 100
Memory 4400M 256G
Secrets 5 100
Subscriptions (cron) 0 100
Subscriptions (IBM Cloud Object Storage) 0 100

You can also list all projects and this output displays which project is your selected project. In the following example, myproject is the project that is selected as the current context.

ibmcloud ce project list

Example output

Getting projects...
OK

Name ID Status Selected Tags Region Resource Group Age
myproj-eude 01234567-abcd-abcd-abcd-abcdabcd2222 active false eu-de default 27d
myproject 01234567-abcd-abcd-abcd-abcdabcd1111 active true us-south default 52d









 Work with a project 

After you create a project, you can work with the project by using the Code Engine console or CLI.
>>> print(granger) f_stat, p_value, R2
-1.7123613937876463,-3.874412217575385,1.0
Show more
* Another basic reducer that is very useful for getting a first order understanding of the time series is the describe reducer. The following illustrates this reducer:

>>> desc = ts.describe()
>>> print(desc)
min inter-arrival-time: 1
max inter-arrival-time: 1
mean inter-arrival-time: 1.0
top: null
unique: 6
frequency: 1
first: TimeStamp: 0 Value: 1.0
last: TimeStamp: 5 Value: 6.0
count: 6
mean:3.5
std:1.707825127659933
min:1.0
max:6.0
25%:1.75
50%:3.5
75%:5.25
Show more







 Temporal joins 

The library includes functions for temporal joins or joining time series based on their timestamps. The join functions are similar to those in a database, including left, right, outer, inner, left outer, right outer joins, and so on. The following sample codes shows some of these join functions:

 Create a collection of observations (materialized TimeSeries)
observations_left = tspy.observations(tspy.observation(1, 0.0), tspy.observation(3, 1.0), tspy.observation(8, 3.0), tspy.observation(9, 2.5))
observations_right = tspy.observations(tspy.observation(2, 2.0), tspy.observation(3, 1.5), tspy.observation(7, 4.0), tspy.observation(9, 5.5), tspy.observation(10, 4.5))

 Build TimeSeries from Observations
ts_left = observations_left.to_time_series()
[root@virtuozzo ] cat > /etc/named.conf <_EOF_

options

{

directory "/var/named";

forwarders { 10.0.80.11; 10.0.80.12; };

listen-on { 10/8; };

};

_EOF_

[root@virtuozzo ] chkconfig named on

[root@virtuozzo ] chkconfig --list named

named 0:off 1:off 2:on 3:on 4:on 5:on 6:off

[root@virtuozzo ] service named start

Starting named: [ OK ]

[root@virtuozzo ]

Show more

Alternatively, you can add a bridged network interface by using Virtuozzo, assign unique internal IP addresses from your internal net block, and add a static route. Internal routing provides access to your internal infrastructure, so keep this alternative solution in mind if you have a mixed network and relaxed filtering on the servers in your internal network.
kube-dal12-crb2f60e9735254ac8b20b9c1e38b649a5-w32 169.xx.210.101 10.xxx.xx.xxx b3c.4x16.encrypted normal Ready dal12 1.26
kube-dal12-crb2f60e9735254ac8b20b9c1e38b649a5-w33 169.xx.210.102 10.xxx.xx.xxx b3c.4x16.encrypted normal Ready dal12 1.26
3. List the VLAN subnets for each unique network ID.

ibmcloud sl subnet list | grep -e <networkID1> -e <networkID2>

Example output

ID identifier type network_space datacenter vlan_id IPs hardware virtual_servers
1234567 169.xx.210.xxx ADDITIONAL_PRIMARY PUBLIC dal12 1122334 16 0 5
7654321 169.xx.178.xxx ADDITIONAL_PRIMARY PUBLIC dal10 4332211 16 0 6
4. Retrieve the subnet address. In the output, find the number of IPs. Then, raise 2 to the power of n equal to the number of IPs. For example, if the number of IPs is 16, then 2 is raised to the power of 4 (n) to equal 16. Now get the subnet CIDR by subtracting the value of n from 32 bits. For example, when n equals 4, then the CIDR is 28 (from the equation 32 - 4 = 28). Combine the identifier mask with the CIDR value to get the full subnet address. In the previous output, the subnet addresses are:



* 169.xx.210.xxx/28
* 169.xx.178.xxx/28





* Individual worker node IP addresses: If you have a small number of worker nodes that run only one app and don't need to scale, or if you want to add only one worker node, list all the worker nodes in your cluster and note the Public IP addresses.
6 Paris
7 Milano
9 Amsterdam
13 Hamburg
14 München
15 Kista
17 Calgary
18 Toronto
19 Boston
20 Seattle
21 Los Angeles
22 Miami
23 Lyon
24 Distrito Federal
25 Tokyo
26 Osaka City
28 Melbourne
29 Bilbao
30 Sao Paulo
31 Kuopio
32 Seoul
33 Singapore

BRANCH_CODE CITY
----------- --------------------------------------------------
34 Shanghai
35 London
36 Birmingham
37 Zürich
38 Heverlee
39 Wien
40 Geneve

29 rows were retrieved.
Show more











 Data science 



 Watson Studio 

After you create a project in IBM Watson Studio (formerly Data Science Experience), you add data assets to it so that you can work with data. All the collaborators in the project are automatically authorized to access the data in the project.

How you add data and from where you can add data differs between legacy and IBM Watson projects. IBM Watson projects use IBM Cloud Object Storage. The project is a legacy project if it uses Object Storage OpenStack Swift.



 To create a new connection in an IBM Watson project: 



1. Click Add to project > Connection.
2. Choose a data source.
3. Enter the connection information required for your data source. Typically, you need to provide information like the host, port number, user name, and password.
4. You can discover assets from connections to Db2 on Cloud, which gives you the ability to add all tables from the connection as data assets to a project. Select Discover data assets and choose a project.
5. Click Create. The connection appears on the Assets page.



Watch this video to see how to create a connection and add connected data to a project.





 To create a new connection in a legacy project: 



1.
Create static routes for your private networks, e.g. 192.168.0.0/16 and 10.0.0.0/8 using the private uplinks. These prefixes are for those networks that are reachable via the IBM Cloud VPC, or Transit Gateway attached to the IBM Cloud VPC. Use the 1st IP address of the private uplink subnet as the next hop, e.g. 192.168.0.9. This is the IBM Cloud VPC implicit router IP address.



For more information on creating Tier 0 logical router, see [VMware Docs](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-E9E62E02-C226-457D-B3A6-FE71E45628F7.html).

NSX-T has a strict URPF rule by default on the external uplinks. Make sure that your routing is symmetric, or otherwise Tier 0 logical routers may discard the packets arriving from a "wrong" interface.

When creating public and private uplinks, you may need to customize the security group rules. For more information, see [IBM Cloud VPC Security Groups](https://cloud.ibm.com/docs/vpc?topic=vpc-using-security-groups).

When creating public and private uplinks, a recommended best practice is to enable NSX-T Edge Gateway Firewall on the interfaces and create required rule set to secure your workloads properly. For more information for configuring Gateway Firewall, see [VMware Docs](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/administration/GUID-A52E1A6F-F27D-41D9-9493-E3A75EC35481.html).





 Step 6: Create IBM Cloud VPC routes 

In this step, you will configure static routes in your IBM Cloud VPC for the subnets/prefixes



1.
: Worker node fix pack update change log documentation is available for version [1.21.2_1524](https://cloud.ibm.com/docs/containers?topic=containers-changelog_1211212_1524), [1.20.8_1546](https://cloud.ibm.com/docs/containers?topic=containers-changelog_1201208_1546), [1.19.12_1553](https://cloud.ibm.com/docs/containers?topic=containers-changelog_11911912_1553), [1.18.29_1558](https://cloud.ibm.com/docs/containers?topic=containers-118_changelog11829_1558), and [1.17.17_1568](https://cloud.ibm.com/docs/containers?topic=containers-117_changelog11717_1568).





 15 July 2021 

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





 12 July 2021 

Snapshots
: Before updating to Kubernetes version 1.20 or 1.21, snapshot CRDs must be changed to version v1beta1. For more information, see the [Kubernetes version information and update actions](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions_121121_before).





 6 July 2021 

Ingress change logs
: Updated the [Ingress ALB change log](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelogkube_ingress_changelog) for versions 0.47.0_1376_iks, 0.45.0_1375_iks, and 0.35.0_1374_iks.

Worker node versions
The timestamp of the first generated observation is calculated by the formula TRUNCATE(first_timestamp/period)x period, so the first timestamp in the output time series is not necessarily the same as the first timestamp in the input time series. In this example, TRUNCATE(1/2)x 2 = 0. Due to the difference in periodicity of the input and output time series, some of the observations in the input time series do not appear in the output. However, the values of any skipped observations are used during interpolation.

Changing the periodicity to 3 produces the following output:

SELECT TS_RESAMPLE(ts6, 3, TS_INTERPOLATOR_PREV(-1.0))
FROM cos://us/sql/timeseries.parquet STORED AS PARQUET
INTO <your target location> STORED AS PARQUET

Following, see the result of the example query:

[(0, -1.0), (3, 2.0), (6, 3.5)]
iSCSI Session State: LOGGED_IN
Internal iscsid Session State: NO CHANGE

Timeouts:

Recovery Timeout: 5
Target Reset Timeout: 30
LUN Reset Timeout: 30
Abort Timeout: 15

CHAP:

username: IBM02SU1575811-I117305979
password: 
username_in: <empty>
password_in: 

Negotiated iSCSI params:

HeaderDigest: None
DataDigest: None
MaxRecvDataSegmentLength: 262144
MaxXmitDataSegmentLength: 65536
FirstBurstLength: 65536
MaxBurstLength: 65536
ImmediateData: Yes
InitialR2T: No
MaxOutstandingR2T: 1

Attached SCSI devices:

Host Number: 1 State: running
scsi1 Channel 00 Id 0 Lun: 0 match the "Lun: 0" here to the LUN ID.
Attached scsi disk sdc State: running

Current Portal: 161.26.110.43:3260,1041 match this target iscsi IP to the block storage device.
Persistent Portal: 161.26.110.43:3260,1041

Interface:

Iface Name: default
Iface Transport: tcp
Iface Initiatorname: iqn.2018-08.com.ibm:ibm02su1575811-i11730597
Iface IPaddress: 10.74.10.67
Iface HWaddress: <empty>
Iface Netdev: <empty>
SID: 3
iSCSI Connection State: LOGGED IN
iSCSI Session State: LOGGED_IN
Internal iscsid Session State: NO CHANGE

Timeouts:

Recovery Timeout: 5
Target Reset Timeout: 30
LUN Reset Timeout: 30
Abort Timeout: 15

CHAP:

username: IBM02SU1575811-I117305979
password:
US bank routing number b((0[0-9]) (1[0-2])(2[1-9])(3[0-2])(6[1-9])(7[0-2])80) ([0-9]{7})b 
 UPS tracking number /b(1Z ?[0-9A-Z]{3} ?[0-9A-Z]{3} ?[0-9A-Z]{2} ?[0-9A-Z]{4} ? [0-9A-Z]{3} ?[0-9A-Z][dT]ddd ?dddd ?ddd)b/ 
 USPS tracking number <br><br> * /(bd{30}b) (b91d+b) (bd{20}b)/<br> * /^ED{1}d{9}D{2}$ ^9d{15,21}$/<br> * /^91[0-9]+$/<br> * /^[A-Za-z]{2}[0-9]+US$/<br><br><br> 
 FedEx tracking number <br><br> * /(b96d{20}b) (bd{15}b) (bd{12}b)/<br> * /b((98ddddd?dddd 98dd) ?dddd ?dddd( ?ddd)?)b/<br> * /^[0-9]{15}$/<br><br><br> 









 Number 

A number response collects a single numeric value.

The customer can specify the number value in either numerals (100) or words (one hundred). Negative and decimal values are recognized.





 Date 

A date response collects a specific calendar date or a range of dates. The assistant can recognize dates that are expressed in various formats. Valid examples include:



* Today
* Friday
* Now
* 10/30/2020
* October 30th, 2020
* October 30th
Updating ALB pods for private-crc81nk5l10gfhdql4i3qg-alb1 to version '1.1.1_1949_iks' in cluster c81nk5l10gfhdql4i3qg...
OK
9. Verify that ALB pods are scheduled onto edge nodes and are not scheduled onto compute nodes.



1. Confirm that all ALB pods are deployed to edge nodes. Each public and private ALB that is enabled in your cluster has two pods.

oc describe nodes -l dedicated=edge | grep alb

Example output

kube-system private-crdf253b6025d64944ab99ed63bb4567b6-alb1-d5dd478db-27pv4 0 (0%) 0 (0%) 0 (0%) 0 (0%)
kube-system private-crdf253b6025d64944ab99ed63bb4567b6-alb1-d5dd478db-7p9q6 0 (0%) 0 (0%) 0 (0%) 0 (0%)
kube-system public-crdf253b6025d64944ab99ed63bb4567b6-alb1-5ff8cdff89-s77z6 0 (0%) 0 (0%) 0 (0%) 0 (0%)
kube-system public-crdf253b6025d64944ab99ed63bb4567b6-alb1-5ff8cdff89-kvs9f 0 (0%) 0 (0%) 0 (0%) 0 (0%)
2. Confirm that no ALB pods are deployed to non-edge nodes.

oc describe nodes -l dedicated!=edge | grep alb

If the ALB pods are correctly deployed to edge nodes, no ALB pods are returned. Your ALBs are successfully rescheduled onto only edge worker nodes.
ibm-system ibm-cloud-provider-ip-169-46-17-2-76fcb4965d-2z64r 5m (0%) 0 (0%) 10Mi (0%) 0 (0%)



7. Retrieve all existing ALBs in the cluster. Review the command output. For each ALB that has a Status of enabled, note the ALB ID and Build.

ibmcloud ks ingress alb ls --cluster <cluster_name_or_ID>

Example output

ALB ID Enabled State Type Load Balancer Hostname Zone Build Status
private-crc81nk5l10gfhdql4i3qg-alb1 true enabled private e9dd35e6-us-south.lb.test.appdomain.cloud us-south-3 ingress:1.1.1_1949_iks/ingress-auth: enabled
public-crc81nk5l10gfhdql4i3qg-alb1 true enabled public 38daf55c-us-south.lb.test.appdomain.cloud us-south-3 ingress:1.1.1_1949_iks/ingress-auth: healthy
8. Using the output from the previous step, run the ibmcloud ks ingress alb update command for each enabled ALB. This command redeploys the ALB to an edge worker node.

When you run this command to redeploy the ALB to an edge worker node, the ALB also updates to the latest version. If you do not want to update the ALB to the latest version, include the --version option and specify the version listed under Build in the output from the previous step.

ibmcloud ks ingress alb update -c <cluster_name_or_ID> --alb <ALB_ID> [--version <build_version>]

Example output
HAProxy 8d6ea6 08c969 [CVE-2022-47629](https://nvd.nist.gov/vuln/detail/CVE-2022-47629). 







 Change log for master fix pack 1.26.1_1519 and worker node fix pack 1.26.1_1520, released 1 February 2023 



Changes since version 1.25.

 Component Previous Current Description 

 Calico configuration N/A N/A Calico configuration now sets a [BGP password](https://docs.tigera.io/calico/latest/reference/resources/bgppeerbgppassword) and container network sysctl tuning for net.ipv4.tcp_keepalive_intvl to 15, net.ipv4.tcp_keepalive_probes to 6 and net.ipv4.tcp_keepalive_time to 40. 
 containerd v1.6.16 v1.7.0-beta.2 See the [containerd release notes](https://github.com/containerd/containerd/releases/tag/v1.7.0-beta.2). In addition, the image pull progress timeout has been configured to 5 minutes. 
 IBM Cloud Controller Manager v1.25.6-2 v1.26.1-2 Updated to support the Kubernetes 1.26.1 release. Updated Go dependencies and to Go version 1.19.5. VPC load balancer creation now honors a user specified name. VPC load balancer update now handles an empty default pool name. 
 Key Management Service provider v2.5.13 v2.6.2 Delayed KMS pod termination until the Kubernetes API server terminates. Updated Go dependencies and to Go version 1.19.4.