From 2c8381a711b43e65a3288177e33db248b9f931af Mon Sep 17 00:00:00 2001 From: Nathan Melehan Date: Mon, 4 May 2026 19:59:39 +0000 Subject: [PATCH 1/4] Fix sitemap search/replace --- .github/workflows/build-production-site.yaml | 4 ++-- .github/workflows/build-staging-site.yaml | 4 ++-- .github/workflows/build-testing-site.yaml | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/.github/workflows/build-production-site.yaml b/.github/workflows/build-production-site.yaml index f75613d757b..ff69c1a875c 100644 --- a/.github/workflows/build-production-site.yaml +++ b/.github/workflows/build-production-site.yaml @@ -219,8 +219,8 @@ jobs: cp sitemap.xml ${{ vars.DUPE_SITEMAP_NAME }} SED_ESCAPED_URL=$(echo ${{ secrets.DOCS_WEBSITE_URL }} | sed 's|\.|\\\.|g') - sed -i 's|$SED_ESCAPED_URL\([a-z0-9\/-]*\)/|https://akamai.com/cloud/\1|g' ${{ vars.DUPE_SITEMAP_NAME }} - sed -i 's|$SED_ESCAPED_URL|https://akamai.com/cloud|' ${{ vars.DUPE_SITEMAP_NAME }} + sed -i "s|$SED_ESCAPED_URL\([a-z0-9\/-]*\)/|https://akamai.com/cloud/\1|g" ${{ vars.DUPE_SITEMAP_NAME }} + sed -i "s|$SED_ESCAPED_URL|https://akamai.com/cloud|g" ${{ vars.DUPE_SITEMAP_NAME }} # Make a tarball of the site, because it will upload much, much quicker # than the uncompressed rendered site. The commit for this workflow run diff --git a/.github/workflows/build-staging-site.yaml b/.github/workflows/build-staging-site.yaml index aec58a82a1c..c9c53cb1033 100644 --- a/.github/workflows/build-staging-site.yaml +++ b/.github/workflows/build-staging-site.yaml @@ -226,8 +226,8 @@ jobs: cp sitemap.xml ${{ vars.DUPE_SITEMAP_NAME }} SED_ESCAPED_URL=$(echo ${{ secrets.DOCS_WEBSITE_URL }} | sed 's|\.|\\\.|g') - sed -i 's|$SED_ESCAPED_URL\([a-z0-9\/-]*\)/|https://akamai.com/cloud/\1|g' ${{ vars.DUPE_SITEMAP_NAME }} - sed -i 's|$SED_ESCAPED_URL|https://akamai.com/cloud|' ${{ vars.DUPE_SITEMAP_NAME }} + sed -i "s|$SED_ESCAPED_URL\([a-z0-9\/-]*\)/|https://akamai.com/cloud/\1|g" ${{ vars.DUPE_SITEMAP_NAME }} + sed -i "s|$SED_ESCAPED_URL|https://akamai.com/cloud|g" ${{ vars.DUPE_SITEMAP_NAME }} # Make a tarball of the site, because it will upload much, much quicker # than the uncompressed rendered site. The commit for this workflow run diff --git a/.github/workflows/build-testing-site.yaml b/.github/workflows/build-testing-site.yaml index aa00d782ee6..a5d57cfe6ba 100644 --- a/.github/workflows/build-testing-site.yaml +++ b/.github/workflows/build-testing-site.yaml @@ -227,8 +227,8 @@ jobs: cp sitemap.xml ${{ vars.DUPE_SITEMAP_NAME }} SED_ESCAPED_URL=$(echo ${{ secrets.DOCS_WEBSITE_URL }} | sed 's|\.|\\\.|g') - sed -i 's|$SED_ESCAPED_URL\([a-z0-9\/-]*\)/|https://akamai.com/cloud/\1|g' ${{ vars.DUPE_SITEMAP_NAME }} - sed -i 's|$SED_ESCAPED_URL|https://akamai.com/cloud|' ${{ vars.DUPE_SITEMAP_NAME }} + sed -i "s|$SED_ESCAPED_URL\([a-z0-9\/-]*\)/|https://akamai.com/cloud/\1|g" ${{ vars.DUPE_SITEMAP_NAME }} + sed -i "s|$SED_ESCAPED_URL|https://akamai.com/cloud|g" ${{ vars.DUPE_SITEMAP_NAME }} # Make a tarball of the site, because it will upload much, much quicker # than the uncompressed rendered site. The commit for this workflow run From 236f609f5a8ee4fd653b9b31f0e6ffc38893e671 Mon Sep 17 00:00:00 2001 From: Nathan Melehan Date: Thu, 7 May 2026 21:09:35 +0000 Subject: [PATCH 2/4] [Update] CVE-2026-31431: Copy Fail Mitigation Update guidance for recycling node pools --- .../cve-2026-31431-copy-fail-mitigation/index.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) 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 index 5ec2996e39c..417191b1f4e 100644 --- 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. \ No newline at end of file From 77ec7872bc869e23a1da4a36e6541db34183b2b0 Mon Sep 17 00:00:00 2001 From: Nathan Melehan Date: Thu, 21 May 2026 17:19:24 +0000 Subject: [PATCH 3/4] [Update] Deploy Akamai MCP Gateway Client Add alias from previous guide slug --- docs/marketplace-docs/guides/akamai-mcp-gateway-client/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/marketplace-docs/guides/akamai-mcp-gateway-client/index.md b/docs/marketplace-docs/guides/akamai-mcp-gateway-client/index.md index 8c02601e9ef..967635fdba5 100644 --- 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"] From d9263c37bd3d7cf8b897dc06df1cfaa1731a5176 Mon Sep 17 00:00:00 2001 From: Jason Tremblay <4190+alertmybanjos@users.noreply.github.com> Date: Tue, 2 Jun 2026 14:18:56 -0400 Subject: [PATCH 4/4] Remove wistia embeds --- docs/guides/quick-answers/linux/how-to-use-grep/index.md | 2 -- docs/guides/quick-answers/linux/how-to-use-head/index.md | 3 --- docs/guides/quick-answers/linux/how-to-use-tail/index.md | 3 --- .../linux/log-in-to-coreos-container-linux/index.md | 2 -- .../cms/drupal/update-and-secure-drupal-8-on-ubuntu/index.md | 3 --- .../wordpress/how-to-install-and-configure-wordpress/index.md | 3 --- 6 files changed, 16 deletions(-) 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 index 20c058aebbe..902f2ae78b4 100644 --- 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"] --- -
- 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 index 32da1dcf83a..a8c5da7780c 100644 --- 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"] --- -
- - 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 index 630f2e951e4..1def7d9b9db 100644 --- 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"] --- -
- - 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 index 4b9f4933582..0fa12287696 100644 --- 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. -
- ## Log in to CoreOS Over SSH ![Log in as core user SSH](container-linux-login-ssh.png) 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 index 6c5e5ff77f5..7347e959075 100644 --- 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. -
- - ## 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 index ac8fab09a8e..3e6c153c2e8 100644 --- 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](/docs/guides/linux-users-and-groups/) guide. {{< /note >}} -
- - ## Before You Begin - Ensure that you have followed the [Getting Started](/docs/products/platform/get-started/) and [Securing Your Server](/docs/products/compute/compute-instances/guides/set-up-and-secure/) guides, and that the Linode's [hostname is set](/docs/products/compute/compute-instances/guides/set-up-and-secure/#configure-a-custom-hostname).