Merge pull request #7017 from wildmanonline/rc-v1.334.0

[Release Candidate] v1.334.0

Author: wildmanonline

docs/guides/development/python/installing-and-importing-modules-in-python-3/index.md

@@ -61,7 +61,7 @@ These instructions are geared toward Ubuntu users but are generally applicable f
 
 ### Install Modules with pip
 
-1. Ensure the `pip` module is already installed. `pip` can be installed using the [APT package manger](/docs/guides/apt-package-manager/).
+1. Ensure the `pip` module is already installed. `pip` can be installed using the [APT package manager](/docs/guides/apt-package-manager/).
 
         sudo apt install python3-pip
 
@@ -239,4 +239,4 @@ The `config` class can now be used in the local program as if it were defined lo
 
 Python modules are used to organize and structure larger programs. Some modules are built-in and are part of the Python library. Other third-party modules must be installed first. Python's `pip` utility is used to install most modules. If a module is not available via `pip`, it can be installed locally.
 
-To make use of the functions in a module, Python must import the module first. The `import` command is used to import an entire module. Specific functions can be imported from a module using the `from <module> import <function>` command. When a module or function is imported, it becomes part of the local symbol table and can be used as a local object. Modules or functions can be given an alias using the `from ... import ... as` directive. The alias can then be used to refer to the imported object. For more information on Python modules, consult the [Python documentation on modules](https://docs.python.org/3/tutorial/modules.html).
+To make use of the functions in a module, Python must import the module first. The `import` command is used to import an entire module. Specific functions can be imported from a module using the `from <module> import <function>` command. When a module or function is imported, it becomes part of the local symbol table and can be used as a local object. Modules or functions can be given an alias using the `from ... import ... as` directive. The alias can then be used to refer to the imported object. For more information on Python modules, consult the [Python documentation on modules](https://docs.python.org/3/tutorial/modules.html).

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

@@ -274,7 +274,7 @@ You will now complete the steps to deploy your Docker Registry to your Kubernete
 
 To enabled basic access restriction for your Docker registry, you will use the `htpasswd` utility. This utility allows you to use a file to store usernames and passwords for basic HTTP authentication. This will require you to log into your Docker registry prior to being able to push or pull images from and to it.
 
-1.  Install the `htpasswd` utility. This example is for an Ubuntu 18.04 instance, but you can use your system's package manger to install it.
+1.  Install the `htpasswd` utility. This example is for an Ubuntu 18.04 instance, but you can use your system's package manager to install it.
 
     ```command
     sudo apt install apache2-utils -y

docs/guides/platform/migrate-to-linode/migrating-a-server-to-your-linode/index.md

@@ -133,7 +133,7 @@ After the network copy is complete and the files from the existing server have b
 
     The entire mounted filesystem will be recursively searched for any instances of your old IP address. Note that this replacement operation can take a while to complete.
 
-3.  You can find your IP information in the Linode Cloud Manger under the **Networking** tab. You'll need your public IP, gateway, and DNS server. On the Linode, open the relevant network configuration files for your distribution and adjust them accordingly.
+3.  You can find your IP information in the Linode Cloud Manager under the **Networking** tab. You'll need your public IP, gateway, and DNS server. On the Linode, open the relevant network configuration files for your distribution and adjust them accordingly.
 
 ### Configuring Mount Points
 

docs/guides/tools-reference/linux-package-management/linux-package-management-overview/index.md

@@ -79,7 +79,7 @@ There are lots of package managers in Linux, each working a bit differently. Her
 - **Underlying package management tool:** [RPM](https://linux.die.net/man/8/rpm) (*RPM Package Manager*)
 - **Package file format:** `.rpm`
 
-*Yellowdog Updater, Modified*, more commonly known as [YUM](http://yum.baseurl.org/), is a package management tool for a variety of older RHEL-based distributions (such as CentOS 7) and older versions of Fedora. It provides an easy-to-use interface on top of the low-level functions available in the RPM Package Manger (RPM). It has largely been replaced by it successor *Dandified YUM*, also called DNF, on most newer RPM-based distributions.
+*Yellowdog Updater, Modified*, more commonly known as [YUM](http://yum.baseurl.org/), is a package management tool for a variety of older RHEL-based distributions (such as CentOS 7) and older versions of Fedora. It provides an easy-to-use interface on top of the low-level functions available in the RPM Package Manager (RPM). It has largely been replaced by it successor *Dandified YUM*, also called DNF, on most newer RPM-based distributions.
 
 ### Zypper
 
@@ -90,7 +90,7 @@ There are lots of package managers in Linux, each working a bit differently. Her
 - **Underlying package management tool:** ZYpp (also called [libzypp](https://doc.opensuse.org/projects/libzypp/HEAD/))
 - **Package file format:** `.rpm`
 
-[Zypper](https://en.opensuse.org/Portal:Zypper) is the CLI tool used for managing packages on openSUSE Linux distributions. Just like DNF and YUM, packages are stored in the `.rpm` file format, though Zypper interfaces with the ZYpp (libzypp) library instead of RPM. Some users report that Zypper is faster than other package mangers and, unlike many others, has the ability to add repositories directly from its own CLI. See the [Zypper manual](https://en.opensuse.org/SDB:Zypper_manual) for more usage details.
+[Zypper](https://en.opensuse.org/Portal:Zypper) is the CLI tool used for managing packages on openSUSE Linux distributions. Just like DNF and YUM, packages are stored in the `.rpm` file format, though Zypper interfaces with the ZYpp (libzypp) library instead of RPM. Some users report that Zypper is faster than other package managers and, unlike many others, has the ability to add repositories directly from its own CLI. See the [Zypper manual](https://en.opensuse.org/SDB:Zypper_manual) for more usage details.
 
 ### Pacman
 
@@ -120,4 +120,4 @@ Arch Linux and other similar distributions (like the popular Manjaro desktop dis
 - **Commands:** `slackpkg`, `pkgtool`, `installpkg`, `upgradepkg`, `removepkg`
 - **Package file format:**  `.tgz` and `.txz` (compressed tar archive)
 
-Slackware comes bundled with a few package management tools. The **pkgtool** is a TUI (menu-driven text interface) for managing packages and installing local packages. To install packages located on the internet, the **slackpkg** tool can be used. For more advanced tasks, use specialized tools like **installpkg**, **upgradepkg**, and **removepkg**.
+Slackware comes bundled with a few package management tools. The **pkgtool** is a TUI (menu-driven text interface) for managing packages and installing local packages. To install packages located on the internet, the **slackpkg** tool can be used. For more advanced tasks, use specialized tools like **installpkg**, **upgradepkg**, and **removepkg**.

docs/guides/websites/hosting/host-a-website-with-high-availability/index.md

@@ -103,7 +103,7 @@ Run the following commands on each Linode in your GlusterFS cluster.
     ```
 
     {{< note >}}
-    In the Linode Manger, you may notice that the netmask for your private IP addresses is `/17`. Firewalld does not recognize this, so a `/32` prefix should be used instead.
+    In the Linode Manager, you may notice that the netmask for your private IP addresses is `/17`. Firewalld does not recognize this, so a `/32` prefix should be used instead.
     {{< /note >}}
 
 1.  Reload your firewall configuration:
@@ -264,7 +264,7 @@ Run the following commands on each database node.
     ```
 
     {{< note >}}
-    In the Linode Manger, you may notice that the netmask for your private IP addresses is `/17`. Firewalld does not recognize this, so a `/32` prefix should be used instead.
+    In the Linode Manager, you may notice that the netmask for your private IP addresses is `/17`. Firewalld does not recognize this, so a `/32` prefix should be used instead.
     {{< /note >}}
 
 1.  Reload your firewall configuration and enable the `firewalld` service to start automatically on boot:
@@ -866,4 +866,4 @@ For more information on DNS configuration, refer to our [introduction to DNS rec
 
 ## Configuration Management
 
-Because a high availability configuration involves so many different components, you may want to consider additional software to help you manage the cluster and create new nodes when necessary. For more information on the options available for managing your nodes, see our guides on [Salt](/docs/guides/getting-started-with-salt-basic-installation-and-setup/), [Chef](/docs/guides/beginners-guide-chef/), [Puppet](/docs/guides/install-and-configure-puppet/), and [Ansible](/docs/guides/running-ansible-playbooks/). You can also refer to our guide on [Automating Server Builds](/docs/products/platform/get-started/guides/automating-deployment/) for an overview of how to choose a solution that is right for you.
+Because a high availability configuration involves so many different components, you may want to consider additional software to help you manage the cluster and create new nodes when necessary. For more information on the options available for managing your nodes, see our guides on [Salt](/docs/guides/getting-started-with-salt-basic-installation-and-setup/), [Chef](/docs/guides/beginners-guide-chef/), [Puppet](/docs/guides/install-and-configure-puppet/), and [Ansible](/docs/guides/running-ansible-playbooks/). You can also refer to our guide on [Automating Server Builds](/docs/products/platform/get-started/guides/automating-deployment/) for an overview of how to choose a solution that is right for you.

docs/products/compute/compute-instances/guides/manage-ip-addresses/index.md

@@ -126,7 +126,7 @@ This process only transfers IPv4 addresses and IPv6 ranges, not IPv6 SLAAC addre
     - **Move To:** moves the IP address to another Compute Instance. When choosing this option, select the destination Compute Instance in the next dropdown menu that appears. If you are moving a public IPv4 address, there needs to be at least one remaining public IPv4 address on the source Compute Instance.
     - **Swap With:** swaps the IP addresses of two Compute Instances. When choosing this option, select the destination Compute Instance in the next dropdown menu that appears. Then select the IP address (belonging to the destination Compute Instance) you would like to swap with the originally selected IP address.
 
-    ![The IP Transfer menu in the Cloud Manger](remote_access_ip_transfer.png)
+    ![The IP Transfer menu in the Cloud Manager](remote_access_ip_transfer.png)
 
     {{< note >}}
     The *IP Transfer* form only displays Compute Instances hosted in the same data center as the current Instance.
@@ -198,4 +198,4 @@ Each data center has its own set of DNS resolvers, which are accessed through bo
 
 1.  Navigate to the **Network** tab and review the **DNS Resolvers** list, which should appear to the right of (or below) the network transfer graph.
 
-    ![Screenshot of the DNS resolvers in the Cloud Manager](dns-resolvers.png)
+    ![Screenshot of the DNS resolvers in the Cloud Manager](dns-resolvers.png)

docs/products/compute/compute-instances/guides/resize/index.md

@@ -10,7 +10,7 @@ image: resizing_a_linode.png
 aliases: ['/platform/disk-images/resizing-a-linode-classic-manager/','/resizing/','/platform/disk-images/resizing-a-linode/','/migrate-to-linode/disk-images/resizing-a-linode/','/guides/resizing-a-linode/']
 ---
 
-You can easily change a Compute Instance's plan using Cloud Manger. Are you expecting a temporary burst of traffic to your website? Or, are you using your plan's resource allotment less than you thought? To accommodate, you can upgrade to a larger plan or downgrade to a smaller one, respectively. You can also change to a different plan type, such as switching from a Shared CPU plan to a Dedicated CPU plan.
+You can easily change a Compute Instance's plan using Cloud Manager. Are you expecting a temporary burst of traffic to your website? Or, are you using your plan's resource allotment less than you thought? To accommodate, you can upgrade to a larger plan or downgrade to a smaller one, respectively. You can also change to a different plan type, such as switching from a Shared CPU plan to a Dedicated CPU plan.
 
 ## Before you begin
 

docs/products/compute/kubernetes/guides/deploy-and-manage-cluster-with-the-linode-api/index.md

@@ -4,7 +4,7 @@ title_meta: "Deploy and Manage a Kubernetes Cluster with the Linode API"
 description: "Learn how to deploy a cluster on Linode Kubernetes Engine (LKE) through the Linode API."
 og_description: "The Linode Kubernetes Engine (LKE) is a fully-managed container orchestration engine for deploying and managing containerized applications and workloads. This guide shows you how to use the Linode API to Deploy and Manage an LKE Cluster."
 published: 2019-11-11
-modified: 2024-06-13
+modified: 2024-06-21
 keywords: ["kubernetes", "linode kubernetes engine", "managed kubernetes", "lke", "kubernetes cluster"]
 image: deploy-and-manage-cluster-copy.png
 aliases: ['/applications/containers/kubernetes/deploy-and-manage-lke-cluster-with-api-a-tutorial/','/kubernetes/deploy-and-manage-lke-cluster-with-api-a-tutorial/','/guides/deploy-and-manage-lke-cluster-with-api-a-tutorial/']
@@ -424,19 +424,24 @@ curl -H "Content-Type: application/json" \
         }' https://api.linode.com/v4/lke/clusters/{{< placeholder "12345" >}}/pools
 ```
 
-In the above command, labels are defined in the `labels` field as key-value pairs within a single object. Taints are defined as an array of dictionary objects in the `taints` field.
+In the above command, labels are defined in the `labels` field as key-value pairs within a single object. Taints are defined as an array of objects in the `taints` field.
 
--   **Labels:** The `labels` field expects a dictionary object with one or more key-value pairs. These key-value pairs should adhere to the specifications and restrictions outlined in the Kubernetes [Labels and Selectors](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) documentation.
+-   **Labels:** The `labels` field expects an object with one or more key-value pairs. These key-value pairs should adhere to the specifications and restrictions outlined in the Kubernetes [Labels and Selectors](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) documentation.
 
     ```command
     "labels": {
         "myapp.io/app": "test"
     }
     ```
 
-    A label's key and value must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to 63 characters each. Optionally, the key can begin with a valid DNS subdomain prefix and a single slash (`/`). In this case, the maximum allowed length of the domain prefix is 253 characters. For instance, `example.com/my-app` is a valid key for a label.
+    -   **Key:** A label's key must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores. Optionally, the key can begin with a valid DNS subdomain prefix.
 
--   **Taints:** The `taints` field expects an array of one or more dictionary objects, adhering to the guidelines outlined in the Kubernetes [Taints and Tolerations](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) documentation. A taint consists of a `key`, `value`, and `effect`:
+        - If the key does not begin with a DNS subdomain prefix, the maximum key length is 63 characters. Example: `my-app`.
+        - If the key begins with a DNS subdomain prefix, it must separate the prefix and the rest of the label with a forward slash (`/`). In this case, the maximum *total* length of the key is 128 characters, with up to 62 characters after the forward slash. The prefix must adhere to RFC 1123 DNS subdomain restrictions. Example: `example.com/my-app`.
+
+    -   **Value:** Must begin with a letter or number, and may contain letters, numbers, hyphens, dots, and underscores, up to 63 characters in length.
+
+-   **Taints:** The `taints` field expects an array of one or more objects, adhering to the guidelines outlined in the Kubernetes [Taints and Tolerations](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) documentation. A taint consists of a `key`, `value`, and `effect`:
 
     ```command
     "taints": [
@@ -474,7 +479,7 @@ curl -H "Content-Type: application/json" \
 
 The above command results in the following changes to the node pool, assuming the labels and taints were originally entered as shown in the first create command.
 
-- Removes the "myapp.io/app" taint by specifying an empty array in the `taint` field.
+- Removes the "myapp.io/app" taint by specifying an empty array in the `taints` field.
 - Changes the label "myapp.io/app" to have a value of "prod" instead of "test".
 - Adds the new label "example=foo".
 

docs/products/storage/object-storage/get-started/index.md

@@ -33,9 +33,11 @@ Billing for Object Storage starts when it is enabled on your account, **regardle
 
 1. Enter a label for the key pair. This label is how you reference your key pair in the Linode Cloud Manager. Then, click **Submit**.
 
-1. A window appears that contains your access key and your secret key. Write these down somewhere secure. The access key is visible in the Linode Cloud Manager, but **you are not be able to retrieve your secret key again once you close the window.**
+1. Select at least one region. You can select multiple regions for your access key.
 
-1. You now have the credentials needed to connect to Linode Object Storage.
+2. A window appears that contains your access key and your secret key. Write these down somewhere secure. The access key is visible in the Linode Cloud Manager, but **you are not able to retrieve your secret key again once you close the window.**
+
+3. You now have the credentials needed to connect to Linode Object Storage.
 
 ## Create a Bucket