linode · nmelehan-akamai · May 4, 2026 · May 5, 2026 · May 5, 2026 · May 7, 2026
diff --git a/docs/guides/quick-answers/linux/how-to-use-grep/index.md b/docs/guides/quick-answers/linux/how-to-use-grep/index.md
@@ -12,8 +12,6 @@ license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 tags: ["linux"]
 ---
 
-<div class="wistia_responsive_padding" style="padding:56.25% 0 0 0;position:relative;"><div class="wistia_responsive_wrapper" style="height:100%;left:0;position:absolute;top:0;width:100%;"><iframe src="https://fast.wistia.net/embed/iframe/pz2xgdch29?videoFoam=true" title="Linode - How to use the grep command" allowtransparency="true" frameborder="0" scrolling="no" class="wistia_embed" name="wistia_embed" allowfullscreen mozallowfullscreen webkitallowfullscreen oallowfullscreen msallowfullscreen width="100%" height="100%"></iframe></div></div>
-
 In this guide, you'll learn how to use the `grep` command. When performing administrative tasks on your Linode, many commands will give you more information than you need. Using `grep` allows you to filter that output in order to find only the data that's relevant.
 
 1.  To search a file for a particular string, provide the string and filename as arguments:

diff --git a/docs/guides/quick-answers/linux/how-to-use-head/index.md b/docs/guides/quick-answers/linux/how-to-use-head/index.md
@@ -11,9 +11,6 @@ aliases: ['/quick-answers/linux/how-to-use-head/','/quick-answers/how-to-use-hea
 tags: ["linux"]
 ---
 
-<div class="wistia_responsive_padding" style="padding:56.0% 0 0 0;position:relative;"><div class="wistia_responsive_wrapper" style="height:100%;left:0;position:absolute;top:0;width:100%;"><iframe src="https://fast.wistia.net/embed/iframe/0nhqzoqhea?videoFoam=true" title="Linode - How to use the head command" allowtransparency="true" frameborder="0" scrolling="no" class="wistia_embed" name="wistia_embed" allowfullscreen mozallowfullscreen webkitallowfullscreen oallowfullscreen msallowfullscreen width="100%" height="100%"></iframe></div></div>
-<script src="https://fast.wistia.net/assets/external/E-v1.js" async></script>
-
 In this guide, you'll learn how to use the `head` command. Using `head` is a simple way to show the beginning of text files, for example, when analyzing logs and other text files that change over time. It may also be combined with other tools for selective, real-time monitoring. When performing administrative tasks on your Linode, `head` is one of the most useful tools available.
 
 1.  Enter the `head` command, followed by the file of which you'd like to view:

diff --git a/docs/guides/quick-answers/linux/how-to-use-tail/index.md b/docs/guides/quick-answers/linux/how-to-use-tail/index.md
@@ -11,9 +11,6 @@ aliases: ['/quick-answers/linux/how-to-use-tail/','/quick-answers/how-to-use-tai
 tags: ["linux"]
 ---
 
-<div class="wistia_responsive_padding" style="padding:56.0% 0 0 0;position:relative;"><div class="wistia_responsive_wrapper" style="height:100%;left:0;position:absolute;top:0;width:100%;"><iframe src="https://fast.wistia.net/embed/iframe/6ds1r8kveb?videoFoam=true" title="Linode - How to use the tail command" allowtransparency="true" frameborder="0" scrolling="no" class="wistia_embed" name="wistia_embed" allowfullscreen mozallowfullscreen webkitallowfullscreen oallowfullscreen msallowfullscreen width="100%" height="100%"></iframe></div></div>
-<script src="https://fast.wistia.net/assets/external/E-v1.js" async></script>
-
 In this guide, you'll learn how to use the `tail` command. Using `tail` is a simple way to show the ends of files, for example, when analyzing logs and other text files that change over time. It may also be combined with other tools for selective, real-time monitoring. When performing administrative tasks on your Linode, `tail` is one of the most useful tools available.
 
 1.  Enter the `tail` command, followed by the file you'd like to view:

diff --git a/docs/guides/quick-answers/linux/log-in-to-coreos-container-linux/index.md b/docs/guides/quick-answers/linux/log-in-to-coreos-container-linux/index.md
@@ -13,8 +13,6 @@ aliases: ['/quick-answers/linux/log-in-to-coreos-container-linux/','/quick-answe
 
 The `root` user is not active by default in Container Linux, so root login is not available. Instead, log in as the `core` user.
 
-<div class="wistia_responsive_padding" style="padding:56.25% 0 0 0;position:relative;"><div class="wistia_responsive_wrapper" style="height:100%;left:0;position:absolute;top:0;width:100%;"><iframe src="//fast.wistia.net/embed/iframe/5vtavtxheq?videoFoam=true" title="Log in to coreOS container Linux" allowtransparency="true" frameborder="0" scrolling="no" class="wistia_embed" name="wistia_embed" allowfullscreen mozallowfullscreen webkitallowfullscreen oallowfullscreen msallowfullscreen width="100%" height="100%"></iframe></div></div><script src="//fast.wistia.net/assets/external/E-v1.js" async></script>
-
 ## Log in to CoreOS Over SSH
 
 ![Log in as core user SSH](container-linux-login-ssh.png)

diff --git a/docs/guides/security/security-patches/cve-2026-31431-copy-fail-mitigation/index.md b/docs/guides/security/security-patches/cve-2026-31431-copy-fail-mitigation/index.md
@@ -80,8 +80,9 @@ For virtual machines (Linode VMs) you can:
 * Older versions of the different Linux distributions remain available for customers to launch. The reason for this is that we cannot assess for our customers what risks they are willing to accept, and that we cannot break automated deployment pipelines for them. We strongly recommend that customers who continue to deploy older releases manually mitigate the vulnerability as described above.
 * If you are using "GRUB 2" (default since August 2018), your Linode will boot with the kernel in the OS disk image. However, if you are [still using one of our kernels to boot](https://techdocs.akamai.com/cloud-computing/docs/manage-the-kernel-on-a-compute-instance), the latest kernel configuration (version 7.0.3) contains the patch for the vulnerability. Older Linode provided kernel configurations (e.g., "6.15.7-x86_64-linode169") remain vulnerable. Customers using these configurations are strongly encouraged to switch to the latest kernel and reboot, or use "GRUB 2" to boot from their own kernel on their primary disk, which has been Linode's default boot option since 2018.
 
-For Linode Kubernetes Engine (LKE and LKE-E), the underlying nodes run a Linux kernel based on the Debian 12 (for LKE) and Ubuntu 22/24 (for LKE-Enterprise) distribution. Existing deployments will need patching until we can provide updated images. We will update this post when they are available. You can choose one of the following options:
+For Linode Kubernetes Engine (LKE and LKE-E), the underlying nodes run a Linux kernel based on the Debian 12 (for LKE) and Ubuntu 22/24 (for LKE-Enterprise) distribution. These have been updated, but existing deployments will need patching. You can choose one of the following options:
 
+* Upgrade to the latest images by [recycling your node pools](https://techdocs.akamai.com/linode-api/reference/post-lke-cluster-pool-recycle).
 * The most durable option is to apply the mitigations outlined above via a DaemonSet. This will ensure mitigations are in place should scaling provision new nodes.
   * Note: A `RuntimeDefault` seccomp profile is insufficient.
 * Alternatively, mitigations can be applied manually or via infrastructure as code (IaC) tools like Terraform or Ansible.
diff --git a/docs/guides/websites/cms/drupal/update-and-secure-drupal-8-on-ubuntu/index.md b/docs/guides/websites/cms/drupal/update-and-secure-drupal-8-on-ubuntu/index.md
@@ -15,9 +15,6 @@ deprecated_link: 'websites/cms/drupal/how-to-update-drupal-8-on-ubuntu-18-04/'
 
 Drupal 8 is the latest version of the popular [Drupal](https://www.drupal.org/) content management system. While a simple incremental update feature is included in version 8.1, manual core updates are required for all preceding versions. This guide demonstrates how to manually install an incremental Drupal 8 update on your Linode. This guide assumes you have a functional Drupal 8 installation running on Apache and Debian or Ubuntu.
 
-<div class="wistia_responsive_padding" style="padding:56.25% 0 0 0;position:relative;"><div class="wistia_responsive_wrapper" style="height:100%;left:0;position:absolute;top:0;width:100%;"><iframe src="//fast.wistia.net/embed/iframe/w7l9omoxr3?videoFoam=true" allowtransparency="true" frameborder="0" scrolling="no" class="wistia_embed" title="Update and secure Drupal 8 on Ubuntu or Debian" name="wistia_embed" allowfullscreen mozallowfullscreen webkitallowfullscreen oallowfullscreen msallowfullscreen width="100%" height="100%"></iframe></div></div>
-<script src="//fast.wistia.net/assets/external/E-v1.js" async></script>
-
 ## Before You Begin
 
 1.  Ensure that you have completed the following guides:

diff --git a/docs/guides/websites/cms/wordpress/how-to-install-and-configure-wordpress/index.md b/docs/guides/websites/cms/wordpress/how-to-install-and-configure-wordpress/index.md
@@ -26,9 +26,6 @@ If you're using Ubuntu 16.04, please use our guide on how to [Install WordPress
 This guide is written for a non-root user. Commands that require elevated privileges are prefixed with `sudo`. If you're not familiar with the `sudo` command, you can check our [Users and Groups](/cloud/guides/linux-users-and-groups/) guide.
 {{< /note >}}
 
-<div class="wistia_responsive_padding" style="padding:56.25% 0 0 0;position:relative;"><div class="wistia_responsive_wrapper" style="height:100%;left:0;position:absolute;top:0;width:100%;"><iframe src="//fast.wistia.net/embed/iframe/weh2nc2dad?videoFoam=true" title="How to install and configure WordPress" allowtransparency="true" frameborder="0" scrolling="no" class="wistia_embed" name="wistia_embed" allowfullscreen mozallowfullscreen webkitallowfullscreen oallowfullscreen msallowfullscreen width="100%" height="100%"></iframe></div></div>
-<script src="//fast.wistia.net/assets/external/E-v1.js" async></script>
-
 ## Before You Begin
 
 -  Ensure that you have followed the [Getting Started](https://techdocs.akamai.com/cloud-computing/docs/getting-started) and [Securing Your Server](https://techdocs.akamai.com/cloud-computing/docs/set-up-and-secure-a-compute-instance) guides, and that the Linode's [hostname is set](https://techdocs.akamai.com/cloud-computing/docs/set-up-and-secure-a-compute-instance#configure-a-custom-hostname).

diff --git a/docs/marketplace-docs/guides/akamai-mcp-gateway-client/index.md b/docs/marketplace-docs/guides/akamai-mcp-gateway-client/index.md
@@ -5,7 +5,7 @@ published: 2026-05-18
 modified: 2026-05-18
 keywords: ['LLM', 'AI Agent', 'Akamai MCP', 'Akamai MCP Gateway']
 tags: ["quick deploy apps", "AI", "AI Agent", "LLM"]
-aliases: ['/products/tools/marketplace/guides/akamai-mcp-client/','/guides/akamai-mcp-client/']
+aliases: ['/products/tools/marketplace/guides/akamai-mcp-client/','/guides/akamai-mcp-client/','/marketplace-docs/guides/akamai-mcp-client/']
 external_resources:
 - '[Akamai MCP Gateway](https://techdocs.akamai.com/mcp-gateway/docs/welcome)'
 authors: ["Akamai"]