[Release Candidate] v1.353.0

ci/vale/dictionary.txt

@@ -21,6 +21,7 @@ adhoc
 adminpack
 adnanh
 adodb
+adoptium
 aes
 ag
 agentless
@@ -375,6 +376,7 @@ configr
 configs
 configtest
 configurability
+configurator
 connectionism
 connectionless
 connectionStatus
@@ -1241,6 +1243,7 @@ kickbans
 kickstarter
 killall
 kinect
+kinesis
 kinser
 kitchensalt
 klei
@@ -1302,6 +1305,7 @@ len
 lennart
 Lerna
 letsencrypt
+Letsencrypt
 lf
 li181
 li263
@@ -2275,6 +2279,7 @@ sentdex
 sentora
 seo
 serializable
+serializer
 serv
 server1
 serverless
@@ -2504,6 +2509,7 @@ Tectia
 telecom
 telehealth
 teleporting
+temurin
 tensorflow
 terrahelp
 terraria

docs/guides/kubernetes/how-to-setup-a-private-docker-registry-with-lke-and-object-storage/index.md

@@ -7,7 +7,7 @@ og_description: "In this guide you will create a private Docker registry on Lino
 authors: ["Leslie Salazar"]
 contributors: ["Leslie Salazar"]
 published: 2020-03-26
-modified: 2023-07-26
+modified: 2024-10-30
 keywords: ['docker registry','kubernetes','object storage', 'lke', 'linode kubernetes engine']
 tags: ["docker","kubernetes","container","nginx","linode platform"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
@@ -362,6 +362,19 @@ If you have not yet [generated an Object Storage key pair](/docs/products/storag
       bucket: registry
     ```
 
+    {{< note title="Multipart uploads" >}}
+    If you require multipart uploading when pushing to your Docker registry, you can set and increase the threshold of the `multipartcopythresholdsize` value using an additional `configData` parameter in your `docker-configs.yaml` file.
+
+    The example below sets the threshold size to 5GB (5368709120 bytes):
+
+    ```
+    configData:
+      storage:
+        s3:
+          multipartcopythresholdsize: 5368709120
+    ```
+    {{< /note >}}
+
     - The NGINX Ingress annotation `nginx.ingress.kubernetes.io/proxy-body-size: "0"` disables a [maximum allowed size client request body](http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size) check and ensures that you won't receive a `413` error when pushing larger Docker images to your registry. The values for `nginx.ingress.kubernetes.io/proxy-read-timeout: "6000"` and `nginx.ingress.kubernetes.io/proxy-send-timeout: "6000"` are sane values to begin with, but [may be adjusted as needed](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#custom-timeouts).
 
 1.  Deploy your Docker registry using the configurations you created in the previous step:

docs/guides/kubernetes/migrating-from-aws-lambda-to-knative/index.md

@@ -584,7 +584,7 @@ The [`func`](https://github.com/knative/func) CLI streamlines the developer expe
 
 ### Build a Function Image
 
-The next step is to create a container image from your function. Since the function is intended run on a Kubernetes cluster, it must be containerized. Knative Functions facilitates this process for developers, abstracting the complexities of Docker and Dockerfiles.
+The next step is to create a container image from your function. Since the function is intended to run on a Kubernetes cluster, it must be containerized. Knative Functions facilitates this process for developers, abstracting the complexities of Docker and Dockerfiles.
 
 1.  Navigate into the `~/get-emojis` directory: