diff --git a/docs/products/compute/kubernetes/guides/deploy-cluster-using-pulumi/index.md b/docs/guides/kubernetes/deploy-lke-cluster-using-pulumi/index.md similarity index 98% rename from docs/products/compute/kubernetes/guides/deploy-cluster-using-pulumi/index.md rename to docs/guides/kubernetes/deploy-lke-cluster-using-pulumi/index.md index 6b72c5d5332..0684d1d23d4 100644 --- a/docs/products/compute/kubernetes/guides/deploy-cluster-using-pulumi/index.md +++ b/docs/guides/kubernetes/deploy-lke-cluster-using-pulumi/index.md @@ -1,4 +1,5 @@ --- +slug: deploy-lke-cluster-using-pulumi title: "Deploy a Linode Kubernetes Engine Cluster Using Pulumi" description: "In this tutorial, you'll deploy a Kubernetes cluster using the Linode Kubernetes Engine (LKE) and Pulumi." authors: ["Pulumi"] @@ -7,6 +8,7 @@ published: 2023-08-22 keywords: ['kubernetes','pulumi','infrastructure as code','container orchestration'] tags: ["linode platform","kubernetes","automation","managed hosting"] license: "[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)" +aliases: ['/products/compute/kubernetes/guides/deploy-cluster-using-pulumi/'] external_resources: - '[Setting Up a Private Docker Registry with Linode Kubernetes Engine and Object Storage](/docs/guides/how-to-setup-a-private-docker-registry-with-lke-and-object-storage/)' - '[Deploying a Static Site on Linode Kubernetes Engine](/docs/guides/how-to-deploy-a-static-site-on-linode-kubernetes-engine/)' @@ -69,8 +71,8 @@ Pulumi defines the elements of your Linode infrastructure using a regular progra Enter a value or leave blank to accept the (default), and press . Press ^C at any time to quit. - project name: (lke-cluster) - project description: (A minimal Linode TypeScript Pulumi program) + project name: (lke-cluster) + project description: (A minimal Linode TypeScript Pulumi program) Created project 'lke-cluster' Please enter your desired stack name. @@ -78,7 +80,7 @@ Pulumi defines the elements of your Linode infrastructure using a regular progra stack name: (dev) Created stack 'dev' - linode:token: The token that allows you access to your Linode account: + linode:token: The token that allows you access to your Linode account: Saved config Installing dependencies... @@ -206,9 +208,9 @@ Now that all your Pulumi configuration is ready, you can deploy your Kubernetes View in Browser (Ctrl+O): https://app.pulumi.com/team-ce/lke-cluster/dev/updates/2 - Type Name Status - pulumi:pulumi:Stack lke-cluster-dev - + └─ linode:index:LkeCluster foobar created (108s) + Type Name Status + pulumi:pulumi:Stack lke-cluster-dev + + └─ linode:index:LkeCluster foobar created (108s) Outputs: diff --git a/docs/products/compute/kubernetes/guides/deploy-cluster-using-terraform/deploy-lke-cluster-with-terraform.png b/docs/guides/kubernetes/deploy-lke-cluster-using-terraform/deploy-lke-cluster-with-terraform.png similarity index 100% rename from docs/products/compute/kubernetes/guides/deploy-cluster-using-terraform/deploy-lke-cluster-with-terraform.png rename to docs/guides/kubernetes/deploy-lke-cluster-using-terraform/deploy-lke-cluster-with-terraform.png diff --git a/docs/products/compute/kubernetes/guides/deploy-cluster-using-terraform/index.md b/docs/guides/kubernetes/deploy-lke-cluster-using-terraform/index.md similarity index 98% rename from docs/products/compute/kubernetes/guides/deploy-cluster-using-terraform/index.md rename to docs/guides/kubernetes/deploy-lke-cluster-using-terraform/index.md index 1668bbcd053..f40898b1011 100644 --- a/docs/products/compute/kubernetes/guides/deploy-cluster-using-terraform/index.md +++ b/docs/guides/kubernetes/deploy-lke-cluster-using-terraform/index.md @@ -1,8 +1,12 @@ --- +slug: deploy-lke-cluster-using-terraform title: "Deploy a Linode Kubernetes Engine Cluster Using Terraform" description: "In this tutorial, you'll deploy a Kubernetes cluster using the Linode Kubernetes Engine (LKE) and Terraform." published: 2020-05-05 modified: 2023-02-09 +authors: ['Linode'] +contributors: ['Linode'] +license: "[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)" keywords: ['kubernetes','terraform','infrastructure as code','container orchestration'] tags: ["linode platform","kubernetes","automation","managed hosting"] image: deploy-lke-cluster-with-terraform.png @@ -10,7 +14,7 @@ external_resources: - '[Setting Up a Private Docker Registry with Linode Kubernetes Engine and Object Storage](/docs/guides/how-to-setup-a-private-docker-registry-with-lke-and-object-storage/)' - '[Deploying a Static Site on Linode Kubernetes Engine](/docs/guides/how-to-deploy-a-static-site-on-linode-kubernetes-engine/)' - '[Linode Provider Terraform Documentation](https://www.terraform.io/docs/providers/linode/index.html)' -aliases: ['/kubernetes/how-to-deploy-an-lke-cluster-using-terraform/','/guides/how-to-deploy-an-lke-cluster-using-terraform/'] +aliases: ['/kubernetes/how-to-deploy-an-lke-cluster-using-terraform/','/guides/how-to-deploy-an-lke-cluster-using-terraform/','/products/compute/kubernetes/guides/deploy-cluster-using-terraform/'] --- ## In this Guide diff --git a/docs/guides/platform/disk-images/kvm-reference/config_direct_disk.png b/docs/guides/platform/disk-images/kvm-reference/config_direct_disk.png deleted file mode 100644 index 6e8d8da4fa3..00000000000 Binary files a/docs/guides/platform/disk-images/kvm-reference/config_direct_disk.png and /dev/null differ diff --git a/docs/guides/platform/disk-images/kvm-reference/index.md b/docs/guides/platform/disk-images/kvm-reference/index.md deleted file mode 100644 index bb813ff8e1e..00000000000 --- a/docs/guides/platform/disk-images/kvm-reference/index.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -slug: kvm-reference -title: 'KVM Migration Reference' -description: KVM Reference explains the differences when going from Xen to KVM virtualization. -authors: ["Josh Sager"] -contributors: ["Josh Sager"] -published: 2015-06-15 -modified: 2020-12-01 -keywords: ["kvm", "kvm reference", "virtual machine mode", "kvm linode", "xen"] -aliases: ['/platform/disk-images/kvm-reference/','/platform/kvm-reference/','/platform/kvm/'] -license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)' -tags: ["linode platform"] -deprecated: true ---- - -Linode's current virtualization stack is built on KVM. Previously, Linode used Xen, and older Linodes may still be on the Xen platform. Along with the increased performance of KVM virtualization, several details are different between Xen and KVM Linodes. - -{{% content "all-linodes-kvm-shortguide" %}} - -## What's Changed? - -### Block Device Assignment - -Device assignments for Xen Linodes were labeled as: - - * */dev/xvda* - * */dev/xvdb* - * */dev/xvdc* - -KVM Linodes use the "*sd*" naming convention: - - * */dev/sda* - * */dev/sdb* - * */dev/sdc* - -### Console - -On KVM Linodes, the console device moves from *hvc0* in Xen to *ttyS0* . - -### Virtual Machine Mode - -Virtual machine mode determines whether devices inside your virtual machine are *paravirtualized* or *fully virtualized*. The differences are listed below: - -| Device Type | Paravirtualization | Full-virtualization | -| -- | -- | -- | -| Block | Virtio SCSI | IDE | -| Net | Virtio Net | e1000 | -| Serial | ttyS0 | ttyS0 | -{{< note >}} -If you're unfamiliar with these distinctions, choose paravirtualization -{{< /note >}} - -### Custom Kernel Configuration - -If you want to build your own guest kernel, you must include the following modules: - -* KVM Guest -* Enable Virtio drivers -* IDE support (for full virtualization) -* e1000 support (for full virtualization) - -For standard paravirtualized KVM Linodes, add the following to your kernel `.config` file: - - CONFIG_KVM_GUEST=y - CONFIG_VIRTIO_PCI=y - CONFIG_VIRTIO_PCI_LEGACY=y - CONFIG_BLK_DEV_SD=y - CONFIG_SCSI_VIRTIO=y - CONFIG_VIRTIO_NET=y - CONFIG_SERIAL_8250=y - CONFIG_SERIAL_8250_CONSOLE=y - -For full virtualization, use the following parameters: - - CONFIG_E1000=y - CONFIG_ATA_PIIX=y - CONFIG_SERIAL_8250=y - CONFIG_SERIAL_8250_CONSOLE=y - -You should also move your block device assignments to be sequential, without skipped block devices. - -### Direct Disk Boot - -An upgrade to KVM Linode includes the ability to do **Direct Disk** booting. Choosing Direct Disk means we will boot the Linode using the Master Boot Record on your boot device: - -![Direct Disk Boot Mode.](config_direct_disk.png) - -## How to Enable KVM - -All new Linodes are created as KVM guests. Older Xen Linodes will need to migrate to KVM before receiving other plan upgrades. - -If your Linode is currently running on Xen, go to the Linode's Dashboard page. In the bottom right of the sidebar is an "Upgrade to KVM" link. Click on the link and follow the instructions to upgrade: - - ![The KVM Upgrade Button.](kvm_upgrade_context.png) - -## Troubleshooting - -There have been a few minor issues reported when upgrading to KVM. If you're using any of the Linux distributions listed below and encounter an issue, please read on. If you are running a different distribution, or encounter an issue not listed here, please contact [Support](/docs/products/platform/get-started/guides/support/). - -### Migration from Xen - -If you are using a kernel other than the one provided by Linode and you migrate from Xen to KVM, you may encounter this error on boot: - -![KVM Kernel Boot Error: "This isn't a KVM kernel! Fix your configuration profile."](kvm-kernel-error.png "KVM Kernel Boot Error: "This isn't a KVM kernel! Fix your configuration profile."") - -This means your Kernel doesn't have the necessary `virtio` drivers. To resolve: - -1. Edit your Linode's configuration profile to use the Linode-supplied kernel. - -2. Boot your Linode to update the kernel and regenerate `initramfs`. The steps will differ depending on your distribution. Assuming you're still using Grub 1 (Legacy Grub), refer to the [Run a Distribution-Supplied Kernel with PV-GRUB](/docs/guides/run-a-distributionsupplied-kernel-with-pvgrub/) guide. - -3. Update `/boot/grub/menu.lst` to use your newly built kernel and `initramfs` file. - -3. Edit your Linode's configuration profile back to the previous setting. - -{{< note >}} -Remember to check [Glish](/docs/products/compute/compute-instances/guides/glish/) as well as Lish while testing. Without the grub terminal set to serial, your startup output may only appear on the Glish output. -{{< /note >}} - -### CentOS 6 - -There are some reported cases of Linodes running CentOS 6.X that lose network connectivity after upgrading. To resolve this issue, open the [LISH Console](/docs/products/compute/compute-instances/guides/lish/) and run: - - rm -f /etc/udev/rules.d/70-persistent-net.rules - -Then, reboot the Linode. - -### Arch Linux - -An upstream change to persistent device naming in systemd has resulted in broken connectivity for any Linode running Arch Linux on a KVM host. The latest version of systemd (226-1+) uses "Predictable Network Interface Names," which prevent the network interface on our platform from being brought online at boot. - -You can disable the use of Predictable Network Interface Names with the command below. - - ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules - -If you have already upgraded and lost connectivity to your Linode, you will need to use the [LISH Console](/docs/products/compute/compute-instances/guides/lish/) to regain access to your Linode to run this command. Once you've done so, reboot your system. diff --git a/docs/guides/platform/disk-images/kvm-reference/kvm-kernel-error.png b/docs/guides/platform/disk-images/kvm-reference/kvm-kernel-error.png deleted file mode 100644 index 35a0adff7f7..00000000000 Binary files a/docs/guides/platform/disk-images/kvm-reference/kvm-kernel-error.png and /dev/null differ diff --git a/docs/guides/platform/disk-images/kvm-reference/kvm_upgrade_context.png b/docs/guides/platform/disk-images/kvm-reference/kvm_upgrade_context.png deleted file mode 100644 index b5a229dd312..00000000000 Binary files a/docs/guides/platform/disk-images/kvm-reference/kvm_upgrade_context.png and /dev/null differ diff --git a/docs/guides/platform/disk-images/tokyo2-migration/index.md b/docs/guides/platform/disk-images/tokyo2-migration/index.md deleted file mode 100644 index 0780e6ef65e..00000000000 --- a/docs/guides/platform/disk-images/tokyo2-migration/index.md +++ /dev/null @@ -1,146 +0,0 @@ ---- -slug: tokyo2-migration -title: Migrating from Tokyo 1 to Tokyo 2 -description: Linode is retiring our Tokyo 1 data center, and this guide shows how to migrate to our new Tokyo 2 location. -authors: ["Linode"] -contributors: ["Linode"] -published: 2018-12-31 -keywords: ["tokyo 1", "tokyo 2", "migrate", "migration", "migrating", "data center"] -license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)' -promo_default: false -tags: ["linode platform"] -aliases: ['/platform/tokyo2-migration/'] -_build: - list: false -noindex: true ---- - -In November 2016, Linode [announced and opened](https://blog.linode.com/2016/11/21/new-linode-datacenter-tokyo-2/) the Tokyo 2 data center. This is the second facility operated by Linode in the Tokyo region. Linode is now making preparations to retire the original Tokyo 1 facility. All Linodes hosted in this data center will be migrated to Tokyo 2. This guide is written to prepare customers for this migration and to make migrating easier. - -## Benefits of Tokyo 2 - -The Tokyo 2 data center provides access to features that are not available in Tokyo 1. These features are: - -- The [Block Storage Service](https://www.linode.com/blockstorage). -- The [newest Linode plans](https://blog.linode.com/2018/05/17/updated-linode-plans-new-larger-linodes/). -- Future features on Linode's product roadmap. - -## When will My Linodes be Migrated? - -The [Linode Classic Manager](https://manager.linode.com) will display the scheduled dates and times for the migrations of your Tokyo 1 Linodes. If you visit the Classic Manager before this schedule is set by Linode, the information will not be displayed. - -When your migration schedule first becomes visible in the Classic Manager, you will receive a support ticket from Linode to let you know. This ticket will be sent to you at least two months in advance of the start of your first migration. Your different Linodes will be scheduled to migrate on different dates and times. **Linode will not be able to adjust this schedule of migrations.** - -You are able to move your servers to Tokyo 2 before the scheduled migration dates. We recommend that all customers move their servers early. Moving early will help you better control the uptime of your services. - -### Will my Linode Backups be Migrated? - -If your Tokyo 1 Linode is enrolled in the [Linode Backup Service](https://www.linode.com/backups), it will remain enrolled in the service after the migration. However, the saved backups and snapshots that have been created for your Linode prior to the migration **will not move** to the new Tokyo 2 facility. Instead, your Linode will start creating new scheduled backups after it is migrated to the Tokyo 2 date center (according to its [backup schedule](/docs/products/storage/backups/guides/schedule/)). - -{{< note >}} -Before migrating, we recommend that you create at least one backup **separate from the Linode Backup Service** for each of your Tokyo 1 Linodes. The [Backing Up your Data](/docs/guides/backing-up-your-data/) guide has suggestions for alternative ways to back up your Linode. -{{< /note >}} - -## What are My Options for Migrating? - -There are three different options for moving your servers to the Tokyo 2 data center. The first two of these methods can be followed before the scheduled migration deadlines for your Linodes. - -Regardless of which option you choose, **all of your Tokyo 1 Linodes' IP addresses will change** when moving to the new location. This includes all public and private IPv4 addresses, as well as public and link-local IPv6 addresses. When the schedule for your Linodes' migrations is set, new IP addresses in the Tokyo 2 data center will be reserved in advance for each of your Tokyo 1 Linodes. These reserved addresses will be listed for each Linode under the [Networking tab](/docs/products/compute/compute-instances/guides/manage-ip-addresses/#viewing-ip-addresses) of the Linode's dashboard. - -Later sections in this guide describe how to update your [network interface configuration](#update-your-network-configuration) and [DNS records](#update-dns-records) to use the new IPs. - -### Option 1: Migrate Early - -When you receive the support ticket which announces your Tokyo 1 Linodes' migrations, you will also see a new banner appear in the dashboard of each of your Tokyo 1 Linodes. This banner will give you the option to initiate an early migration of your Linode to Tokyo 2. - -{{< note >}} -The early migration banner will actually appear on your Tokyo 1 Linodes' dashboards before you receive the support ticket which announces the migrations. You will be able to perform a migration as soon as you see this banner. However, new IPs in the Tokyo 2 data center will not be reserved for your Linode until you receive the support ticket. - -This means that if you migrate before you receive your ticket, you will not know what your new IP addresses will be before you start the migration. Once you start the early migration, your new Tokyo 2 IP addresses will become visible in the [Networking tab](/docs/products/compute/compute-instances/guides/manage-ip-addresses/#viewing-ip-addresses) of the Linode's dashboard. -{{< /note >}} - -Clicking on the banner will take you to a new page which shows the estimated duration for the migration. This page will let you initiate the migration. - -The following sequence executes when you start the migration: - -1. If your Linode is running, your Linode is gracefully powered down. - -1. At the same time, your Linode will be assigned its reserved Tokyo 2 IP addresses. These new IPs will become visible in the [Networking tab](/docs/products/compute/compute-instances/guides/manage-ip-addresses/#viewing-ip-addresses) of your Linode's dashboard. - -1. The migration of your Linode is started immediately after the shutdown completes. - -1. If the Linode was running before the migration started, it will be automatically booted after the migration completes. If the Linode was not running, it will remain offline after the migration. - -You will be able to monitor the progress of your Linode's migration from its dashboard. While waiting on the migration to complete, update your [DNS records](#update-dns-records) to use your new IP addresses. DNS changes can take time to propagate, so we recommend doing this quickly after the migration is initiated. Consider updating your [domain's TTL](#update-your-ttl) *before* you initiate the migration. - -When the migration finishes, you may need to update your Linode's [network configuration](#update-your-network-configuration) to work properly with its new IP addresses. - -### Option 2: Clone your Linodes - -Because migrating a Linode will power it down during the migration, your Linode's services will be offline during that time. In addition, if you run a cluster of multiple Linodes for a service, then migrating one or more of them may cause problems for the cluster. - -To avoid these issues, you can instead create new Linodes in Tokyo 2 and then **clone** your Tokyo 1 Linode's disks to them. Performing a clone will create exact copies of your disks on the new Linode. - -{{< note >}} -You can perform a clone of a Linode when it is running. However, this can sometimes result in filesystem inconsistencies on the target Linode (your source Linode will never be negatively affected, even if the clone fails). You may need to power your source Linode down to perform a successful clone. -{{< /note >}} - -Cloning your Linodes offers these benefits: - -- You will be able to set up your new Linodes in Tokyo 2 and verify that they run normally before you remove your Tokyo 1 Linodes. - -- To move your customers to your new Tokyo 2 servers, you can update your DNS records with your new Tokyo 2 IP addresses. You can keep your Tokyo 1 servers running while you update your DNS. Updating your DNS records in this way will gracefully direct your users to your new servers without downtime. - -{{< note >}} -New Linodes that you create in Tokyo 2 will not receive the IP addresses that are reserved for your Tokyo 1 Linodes' scheduled migrations. If you choose to clone your Linodes, your new Tokyo 2 Linodes' IP addresses will be listed in the [Networking tab](/docs/products/compute/compute-instances/guides/manage-ip-addresses/#viewing-ip-addresses) of your Linodes' dashboards. -{{< /note >}} - -To clone a Linode, follow these steps: - -1. Create a new Linode in Tokyo 2. Make sure that you [select a plan](https://www.linode.com/pricing) that has as much disk space as the size of your disks on your source Tokyo 1 Linode. - -1. Follow the [cloning guide](/docs/products/compute/compute-instances/guides/clone-instance/) to complete the clone operation. When following these steps, enable all of the configuration profile options for your Linode. - -1. Boot the new Tokyo 2 Linode when the clone completes. - -After you have completed the clone, you may need to update your new Linode's [network configuration](#update-your-network-configuration) to work properly with its new IP addresses. After making sure that your new Tokyo 2 servers all work as expected, update your [DNS records](#update-dns-records). Consider updating your [domain's TTL](#update-your-ttl) *before* you update your DNS records. -{{< note type="alert" >}} -If you clone your Tokyo 1 Linodes to Tokyo 2, your Tokyo 1 Linodes will remain running and active on your account by default. To prevent double-billing, [remove](/docs/products/platform/billing/guides/stop-billing/) the original Tokyo 1 Linodes after you have finished your clones. -{{< /note >}} - -### Option 3: Migrate when Scheduled - -If you do not choose to migrate or clone early, Linode will automatically start your migrations at the time listed in your support ticket. -{{< note type="alert" >}} -If Linode initiates your migration when it is scheduled, **your Linode will not be powered on automatically when the migration finishes**. Your Linode is not powered on in order to minimize potential security issues that could result from booting under a new IP assignment. -{{< /note >}} - -After the scheduled migration completes, you can log into the Linode's dashboard and power it on. You may need to update your new Linode's [network configuration](#update-your-network-configuration) to work properly with its new IP addresses. Then, update your [DNS records](#update-dns-records). You can also choose to update your DNS records as soon as the migration starts. Consider updating your [domain's TTL](#update-your-ttl) *before* the scheduled migration starts. - -## Update your Network Configuration - -In order for your new IP address assignment to work, your Linux deployment's network interface configuration needs to use the new IPs. If Linode's [Network Helper](/docs/products/compute/compute-instances/guides/network-helper/) tool is enabled for your configuration profile, your network interface should automatically adopt the new IPs without any extra action needed from you. - -If Network Helper is not enabled, but you use DHCP for your network assignments, then your networking should also work automatically. - -If you do not use Network Helper or DHCP, then you will need to update your static interface configuration files. Follow the [Linux Static IP Configuration](/docs/products/compute/compute-instances/guides/manual-network-configuration/) guide to enter your new IP addresses. Your new IPs are listed in the [Networking tab](/docs/products/compute/compute-instances/guides/manage-ip-addresses/#viewing-ip-addresses) of your Linode's dashboard. These new IPs will only appear **after you start its migration** (if you choose to migrate instead of cloning). - -You may also need to update the configuration of your applications if they explicitly bind to your public or private IP addresses. Review Linode's [web server](/docs/guides/web-servers/) and [application](/docs/guides/applications/) guides for more information on this topic. - -## Update DNS Records - -To direct your users to your new Tokyo 2 servers' IPs, you need to update your DNS records to use the new IPs. If you are using Linode's DNS Manager, follow the DNS Manager guide to update your [DNS records](/docs/products/networking/dns-manager/guides/manage-dns-records/). - -If you use a different DNS provider, you will need to visit that provider's website to update your records. - -{{% content "update-dns-at-common-name-server-authorities" %}} - -### Update your TTL - -DNS resolvers hold a cache for your domain's records. A resolver will update its cached records according to your domain's *Time To Live* (TTL) value. This means that when you update your DNS records, other DNS resolvers will not immediately update their records for your domain. Instead, they will receive your new records when their caches expires. - -Having a short TTL means that your users will be directed to your new IP addresses faster when you update your DNS records. It is recommended that you lower your TTL ahead of your migrations. After you complete your migrations and have updated your DNS successfully, you can raise your TTL back to the default value of 24 hours. - -## Contact Linode Support - -If you have any issues when migrating or cloning to Tokyo 2, or if you have any questions about this process, please [contact Linode Support](https://www.linode.com/support/). Technical questions about your Linux deployment's configuration are often outside the scope of support. For any out-of-scope issues, we also recommend searching and asking technical questions in the [Linode Community Site](https://www.linode.com/community/questions/). diff --git a/docs/guides/platform/manager/_index.md b/docs/guides/platform/manager/_index.md deleted file mode 100644 index 681c0a52bcf..00000000000 --- a/docs/guides/platform/manager/_index.md +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: Linode Manager -description: 'Explore features of the Linode Manager.' -authors: ["Linode"] -contributors: ["Linode"] -published: 2018-07-16 -keywords: ["manager"] -license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)' -aliases: ['/platform/manager/','/manager/'] -show_in_lists: true ---- - diff --git a/docs/guides/platform/manager/feature.png b/docs/guides/platform/manager/feature.png deleted file mode 100644 index 5a19cce13da..00000000000 Binary files a/docs/guides/platform/manager/feature.png and /dev/null differ diff --git a/docs/guides/platform/manager/feature.svg b/docs/guides/platform/manager/feature.svg deleted file mode 100644 index f3ffa2bd57c..00000000000 --- a/docs/guides/platform/manager/feature.svg +++ /dev/null @@ -1 +0,0 @@ - \ No newline at end of file diff --git a/docs/guides/platform/manager/members-linode-com-migration/index.md b/docs/guides/platform/manager/members-linode-com-migration/index.md deleted file mode 100644 index cff1e645b3c..00000000000 --- a/docs/guides/platform/manager/members-linode-com-migration/index.md +++ /dev/null @@ -1,101 +0,0 @@ ---- -slug: members-linode-com-migration -title: "Migrating Away from members.linode.com and nodebalancer.linode.com" -title_meta: "members.linode.com and nodebalancer.linode.com Migration" -description: "The members.linode.com and nodebalancer.linode.com are deprecated. Follow the steps in this guide to use the new domain for forward and reverse DNS." -authors: ["Linode"] -contributors: ["Linode"] -published: 2021-10-13 -keywords: ['dns','members.linode.com','reverse dns'] -license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)' ---- - -## What are members.linode.com and nodebalancer.linode.com? - -All Linode Compute Instances and NodeBalancers are created with a default domain (*forward* DNS address) and a preconfigured rDNS (*reverse* DNS) entry for that domain. These default domains use the following patterns: - -- **Compute Instance:** - - li[signifier].members.linode.com - - (*Example:* `li999-999.members.linode.com`) - -- **NodeBalancer:** - - nb-[ip-address].[region].nodebalancer.linode.com - - (*Example:* `nb-192-0-2-1.dallas.nodebalancer.linode.com`) - -Linode Instances and NodeBalancers are accessible at these addresses for testing and other non-production purposes. While it's much more favorable to provide access to these services with a personal or company domain name, it's possible that some users have referenced the default domain within their own workflows, scripts, and applications. - -## What's Changing? - -Linode is changing the default domain and rDNS entry associated with every Linode Instance and NodeBalancer. This new domain name follows a new pattern, where *[ip-address]* is replaced with the primary public IPv4 address for your server: - -- **Compute Instances and NodeBalancers:** - - [ip-address].ip.linodeusercontent.com - - (*Example:* `192-0-2-1.ip.linodeusercontent.com`) - -Note that dashes (**not periods**) separate the values of the IP address. - -## What Action Should I Take? - -If you *don't* actively use the `members.linode.com` or `nodebalancer.linode.com` forward or reverse DNS in any of your scripts, applications, or domain settings, then this migration does not impact your properties. - -If you *do* use your Linode Instance's `members.linode.com` or NodeBalancer's `nodebalancer.linode.com` forward or reverse DNS, please change your scripts, applications, or domain settings to either the new default domain, the IP address of your service, or your own FQDN (fully qualified domain name) if you've configured one for the service. In the future, Linode will end support for `members.linode.com` and `nodebalancer.linode.com`. - -### How to Adopt the New Domain Addresses - -For forward DNS, all Linodes and NodeBalancers can be accessed at the new address of `[ip-address].ip.linodeusercontent.com` without further configuration. However, you should locate all instances of prior `members.linode.com` or `nodebalancer.linode.com` domain addresses in your codebase, application configuration files, etc., and change them to the new address. - -#### Finding a Linode's IP Address - -1. In [Cloud Manager](https://cloud.linode.com), select **Linodes** from the navigation menu, then select the Linode for which you'd like to find the IP Address. - -1. Under *IP Addresses*, select the top IPv4 address. This is the IP address that you can use with the new forward DNS. - -#### Finding a NodeBalancer's IP Address - -1. In [Cloud Manager](https://cloud.linode.com), select **NodeBalancers** from the navigation menu, then select the NodeBalancer for which you'd like to find the IP Address. - -1. On the right hand of the screen, under *IP Addresses*, note the top IPv4 Address. This is the address you can use to access your NodeBalancer's forward DNS. - -#### Finding an Existing members.linode.com Address - -To find an existing `members.linode.com` address: - -1. In [Cloud Manager](https://cloud.linode.com), select **Linodes** from the navigation menu, then select the Linode for which you'd like to find the domain. - -1. Click on the **Network** tab. - -1. Under **IP Addresses**, find the Linode Instance's IP address and it's corresponding reverse DNS entry. - - !["A Linode Instance's Network page displays the Linode's reverse DNS"](locate-rdns-linode.png) - - The value under reverse DNS is the Linode Instance's current `members.linode.com` address. - -{{< note >}} -If you're following these instructions and do not find a `members.linode.com` address, and instead find an `ip.linodeusercontent.com` address, then your Linode Instance has already been configured to use the new domain. -{{< /note >}} - -#### Finding an Existing nodebalancer.linode.com Address - -To find an existing `nodebalancer.linode.com` address: - -1. In [Cloud Manager](https://cloud.linode.com), select **NodeBalancers** from the navigation menu, then select the NodeBalancer for which you'd like to find the domain. - -1. On the **Summary** page, on the right of the page, find the NodeBalancer's Hostname. - - !["A NodeBalancer's forward DNS is available on a NodeBalancer's summary page"](locate-domain-nodebalancer.png) - - This is your NodeBalancer's existing forward DNS. - -{{< note >}} -If you're following these instructions and do not find a `nodebalancer.linode.com` address, and instead find an `ip.linodeusercontent.com` address, then your NodeBalancer has already been configured to use the new domain. -{{< /note >}} - -### Updating Reverse DNS - -To change a Linode's reverse DNS records, review the [Configure Your Linode for Reverse DNS](/docs/products/compute/compute-instances/guides/configure-rdns/) guide. The new forward DNS records already exist for your Linode's IP, so you can set your Linode's reverse DNS records to match the new name by following the linked guide. diff --git a/docs/guides/platform/manager/members-linode-com-migration/locate-domain-nodebalancer.png b/docs/guides/platform/manager/members-linode-com-migration/locate-domain-nodebalancer.png deleted file mode 100644 index eaf58d24b44..00000000000 Binary files a/docs/guides/platform/manager/members-linode-com-migration/locate-domain-nodebalancer.png and /dev/null differ diff --git a/docs/guides/platform/manager/members-linode-com-migration/locate-rdns-linode.png b/docs/guides/platform/manager/members-linode-com-migration/locate-rdns-linode.png deleted file mode 100644 index 957bf01d368..00000000000 Binary files a/docs/guides/platform/manager/members-linode-com-migration/locate-rdns-linode.png and /dev/null differ diff --git a/docs/guides/quick-answers/linode-platform/dhcp-ip-address-reference/index.md b/docs/guides/quick-answers/linode-platform/dhcp-ip-address-reference/index.md deleted file mode 100644 index 54dae5fb309..00000000000 --- a/docs/guides/quick-answers/linode-platform/dhcp-ip-address-reference/index.md +++ /dev/null @@ -1,103 +0,0 @@ ---- -slug: dhcp-ip-address-reference -title: DHCP IP Address Reference -description: 'Shortguide that displays a list of all IP addresses used for configurations that rely on DHCP by their data center.' -authors: ["Linode"] -contributors: ["Linode"] -published: 2021-09-10 -license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)' -keywords: [dhcp", "cloud firewall", "firewall", "networking"] -tags: ["linode platform","cloud manager"] -aliases: ['/quick-answers/linode-platform/dhcp-ip-address-reference/'] ---- - -In some cases, such as when configuring a firewall, you may need to know the IP addresses that Linode uses for our DHCP servers. Below is a list of all DHCP IP addresses categorized by their data center, to assist in any configuration you may need. - -## Fremont - -173.255.254.129
-50.116.6.33
-66.175.222.121
-50.116.1.128
-173.255.245.39
-66.175.223.241 - -## Dallas -50.116.29.9
-72.14.182.149
-50.116.18.11
-72.14.189.93
-66.228.55.26
-173.255.199.165 - -## Atlanta -198.74.55.159
-50.116.46.210
-173.230.139.221
-192.155.93.9
-173.230.139.4
-74.207.234.190 - -## Newark -97.107.131.49
-69.164.219.39
-66.228.42.172
-66.175.213.64
-97.107.132.48
-96.126.108.78 - -## London -176.58.106.63
-151.236.222.62
-151.236.218.42
-176.58.111.6
-178.79.152.230
-178.79.187.246 - -## Singapore -103.3.60.28
-103.3.60.29
-103.3.60.30
-103.3.60.31
-103.3.60.32
-103.3.60.33 - -## Frankfurt -139.162.128.28
-139.162.128.29
-139.162.128.30
-139.162.128.31
-139.162.128.32
-139.162.128.33 - -## Tokyo -139.162.65.28
-139.162.65.29
-139.162.65.30
-139.162.65.31
-139.162.65.32
-139.162.65.33 - -## Toronto -172.105.0.50
-172.105.0.53
-172.105.0.52
-172.105.0.54
-172.105.0.51
-172.105.0.55 - -## Mumbai -172.105.33.16
-172.105.33.17
-172.105.33.12
-172.105.33.13
-172.105.33.14
-172.105.33.15 - -## Sydney -172.105.176.4
-172.105.166.4
-172.105.180.4
-172.105.170.4
-172.105.181.4
-172.105.171.4 \ No newline at end of file diff --git a/docs/guides/quick-answers/linode-platform/find-your-linodes-ip-address/index.md b/docs/guides/quick-answers/linode-platform/find-your-linodes-ip-address/index.md deleted file mode 100644 index 7e928738338..00000000000 --- a/docs/guides/quick-answers/linode-platform/find-your-linodes-ip-address/index.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -slug: find-your-linodes-ip-address -title: Find Your Linode's IP Address -description: 'This quick answer guide shows how to find the IP address of your Linode either through the Linode Manager or while in an SSH session.' -authors: ["Linode"] -contributors: ["Linode"] -published: 2017-09-21 -keywords: ["ip address", "ip addresses", "address", "addresses"] -tags: ["linode platform","cloud manager","networking"] -license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)' -aliases: ['/quick-answers/linode-platform/find-your-linodes-ip-address-classic-manager/','/quick-answers/linode-platform/find-your-linodes-ip-address/'] ---- - -Finding your Linode's IP address (or addresses) is easy and can be done in two different ways. - -## From the Cloud Manager - -1. Log in to the Cloud Manager. - -2. From the **Linodes** tab of your account, select the Linode you want to work with. - -3. Click the **Networking** tab. - - - You will see sections for IPv4 and IPv6. - - Your public IPs are listed under the Address columns in these sections. -![Public IPs.](networking_ips.png) - -4. View more information about the IP by clicking the more options ellipsis to the right, then click **View** in the exposed dropdown menu. -![View IP Details.](view_ip_detail_menu.png) - -5. A side panel opens to reveal more networking information including the [subnet mask](https://en.wikipedia.org/wiki/Subnetwork). -![View IP Detail Panel.](view_ip_details.png) - -## From an SSH Session - -Use the command below to view your Linode's IP addresses: - - ip addr | grep inet - -An example of the output: - - root@localhost:~# ip addr | grep inet - inet 127.0.0.1/8 scope host lo - inet6 ::1/128 scope host - inet 45.56.111.42/24 brd 45.56.111.255 scope global eth0 - inet 97.107.134.191/24 scope global eth0:1 - inet 192.168.192.154/17 scope global eth0:2 - inet6 2600:3c03::f03c:91ff:fe73:9675/64 scope global mngtmpaddr noprefixroute - inet6 fe80::f03c:91ff:fe26:7e8e/64 scope link - -The output shows: - -- Two public IPv4 addresses, `45.56.111.42` and `97.107.134.191` -- One private IPv4 address, `192.168.192.154` -- One public IPv6 address, `2600:3c03::f03c:91ff:fe73:9675` -- One private IPv6 address, `fe80::f03c:91ff:fe26:7e8e` -{{< note >}} -DHCP will only recognize one IPv4 address. If you have more than one IPv4 address assigned to your Linode, you must either set those addresses statically or enable Network Helper. Otherwise, those addresses will not be usable to the system, nor will they display in `ip` commands. See the following guides for more information: - -[Linux Static IP Configuration](/docs/products/compute/compute-instances/guides/manual-network-configuration/) - -[Network Helper](/docs/products/compute/compute-instances/guides/network-helper/) -{{< /note >}} diff --git a/docs/guides/quick-answers/linode-platform/find-your-linodes-ip-address/networking_ips.png b/docs/guides/quick-answers/linode-platform/find-your-linodes-ip-address/networking_ips.png deleted file mode 100644 index c2afd24da5c..00000000000 Binary files a/docs/guides/quick-answers/linode-platform/find-your-linodes-ip-address/networking_ips.png and /dev/null differ diff --git a/docs/guides/quick-answers/linode-platform/find-your-linodes-ip-address/view_ip_detail_menu.png b/docs/guides/quick-answers/linode-platform/find-your-linodes-ip-address/view_ip_detail_menu.png deleted file mode 100644 index 8fedf795e0b..00000000000 Binary files a/docs/guides/quick-answers/linode-platform/find-your-linodes-ip-address/view_ip_detail_menu.png and /dev/null differ diff --git a/docs/guides/quick-answers/linode-platform/find-your-linodes-ip-address/view_ip_details.png b/docs/guides/quick-answers/linode-platform/find-your-linodes-ip-address/view_ip_details.png deleted file mode 100644 index e57ade3aa7a..00000000000 Binary files a/docs/guides/quick-answers/linode-platform/find-your-linodes-ip-address/view_ip_details.png and /dev/null differ diff --git a/docs/products/compute/compute-instances/guides/install-a-custom-distribution/custom-distro-configuration-profiles.png b/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/custom-distro-configuration-profiles.png similarity index 100% rename from docs/products/compute/compute-instances/guides/install-a-custom-distribution/custom-distro-configuration-profiles.png rename to docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/custom-distro-configuration-profiles.png diff --git a/docs/products/compute/compute-instances/guides/install-a-custom-distribution/custom-distro-debian-installer.png b/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/custom-distro-debian-installer.png similarity index 100% rename from docs/products/compute/compute-instances/guides/install-a-custom-distribution/custom-distro-debian-installer.png rename to docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/custom-distro-debian-installer.png diff --git a/docs/products/compute/compute-instances/guides/install-a-custom-distribution/custom-distro-disks.png b/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/custom-distro-disks.png similarity index 100% rename from docs/products/compute/compute-instances/guides/install-a-custom-distribution/custom-distro-disks.png rename to docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/custom-distro-disks.png diff --git a/docs/products/compute/compute-instances/guides/install-a-custom-distribution/custom-distro-glish-small.png b/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/custom-distro-glish-small.png similarity index 100% rename from docs/products/compute/compute-instances/guides/install-a-custom-distribution/custom-distro-glish-small.png rename to docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/custom-distro-glish-small.png diff --git a/docs/products/compute/compute-instances/guides/install-a-custom-distribution/custom-distro-glish.png b/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/custom-distro-glish.png similarity index 100% rename from docs/products/compute/compute-instances/guides/install-a-custom-distribution/custom-distro-glish.png rename to docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/custom-distro-glish.png diff --git a/docs/products/compute/compute-instances/guides/install-a-custom-distribution/glish-post-install.png b/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/glish-post-install.png similarity index 100% rename from docs/products/compute/compute-instances/guides/install-a-custom-distribution/glish-post-install.png rename to docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/glish-post-install.png diff --git a/docs/products/compute/compute-instances/guides/install-a-custom-distribution/index.md b/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/index.md similarity index 98% rename from docs/products/compute/compute-instances/guides/install-a-custom-distribution/index.md rename to docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/index.md index bebc314dbff..21993b23d14 100644 --- a/docs/products/compute/compute-instances/guides/install-a-custom-distribution/index.md +++ b/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/index.md @@ -1,11 +1,15 @@ --- +slug: install-a-custom-distribution title: "Install a Custom Linux Distribution on a Compute Instance" description: "Learn how to install and configure an unsupported Linux distribution on your Linode Compute Instance" published: 2017-03-02 modified: 2023-01-18 +authors: ['Linode'] +contributors: ['Linode'] +license: "[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)" keywords: ["custom distro", "custom distribution", "advanced Linux", "kvm"] tags: ["debian", "cloud manager"] -aliases: ['/tools-reference/custom-kernels-distros/install-a-custom-distribution-on-a-linode/','/tools-reference/custom-kernels-distros/running-a-custom-linux-distro-on-a-linode-vps/','/tools-reference/custom-kernels-distros/custom-distro-on-kvm-linode/','/guides/install-a-custom-distribution-on-a-linode/','/guides/install-a-custom-distribution/'] +aliases: ['/tools-reference/custom-kernels-distros/install-a-custom-distribution-on-a-linode/','/tools-reference/custom-kernels-distros/running-a-custom-linux-distro-on-a-linode-vps/','/tools-reference/custom-kernels-distros/custom-distro-on-kvm-linode/','/guides/install-a-custom-distribution-on-a-linode/','/products/compute/compute-instances/guides/install-a-custom-distribution/'] image: install-a-custom-distribution-on-a-linode.png --- diff --git a/docs/products/compute/compute-instances/guides/install-a-custom-distribution/install-a-custom-distribution-on-a-linode.png b/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/install-a-custom-distribution-on-a-linode.png similarity index 100% rename from docs/products/compute/compute-instances/guides/install-a-custom-distribution/install-a-custom-distribution-on-a-linode.png rename to docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/install-a-custom-distribution-on-a-linode.png diff --git a/docs/products/compute/compute-instances/guides/install-a-custom-distribution/install-custom-distro-glish-console.png b/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/install-custom-distro-glish-console.png similarity index 100% rename from docs/products/compute/compute-instances/guides/install-a-custom-distribution/install-custom-distro-glish-console.png rename to docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/install-custom-distro-glish-console.png diff --git a/docs/products/compute/compute-instances/guides/install-a-custom-distribution/rescue-mode-assign-disks.png b/docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/rescue-mode-assign-disks.png similarity index 100% rename from docs/products/compute/compute-instances/guides/install-a-custom-distribution/rescue-mode-assign-disks.png rename to docs/guides/tools-reference/custom-kernels-distros/install-a-custom-distribution/rescue-mode-assign-disks.png diff --git a/docs/products/compute/compute-instances/guides/_index.md b/docs/products/compute/compute-instances/guides/_index.md index 6a092d24ad6..0d0968f96b7 100644 --- a/docs/products/compute/compute-instances/guides/_index.md +++ b/docs/products/compute/compute-instances/guides/_index.md @@ -50,6 +50,7 @@ aliases: ['/products/compute/shared-linodes/guides/','/products/compute/shared-c - [Manual Network Configuration](/docs/products/compute/compute-instances/guides/manual-network-configuration/) - [Configure Failover](/docs/products/compute/compute-instances/guides/failover/) - [An Overview of IPv6 on Linode](/docs/products/compute/compute-instances/guides/ipv6/) +- [DHCP IP Address Reference](/docs/products/compute/compute-instances/guides/dhcp-ip-address-reference/) ## Metadata (Automated System Configuration with Cloud-Init) diff --git a/docs/products/compute/compute-instances/guides/configuration-profiles/index.md b/docs/products/compute/compute-instances/guides/configuration-profiles/index.md index 142a2397788..1b39ef37ff0 100644 --- a/docs/products/compute/compute-instances/guides/configuration-profiles/index.md +++ b/docs/products/compute/compute-instances/guides/configuration-profiles/index.md @@ -7,7 +7,7 @@ modified: 2024-01-30 keywords: ["configuration profiles"] tags: ["linode platform","cloud manager"] image: Linode-Configuration-Profiles.jpg -aliases: ['/platform/disk-images/disk-images-and-configuration-profiles-classic-manager/','/disk-images-config-profiles/','/platform/disk-images/disk-images-and-configuration-profiles/','/migrate-to-linode/disk-images/disk-images-and-configuration-profiles/','/guides/linode-configuration-profiles/','/guides/disk-images-and-configuration-profiles/'] +aliases: ['/platform/disk-images/disk-images-and-configuration-profiles-classic-manager/','/disk-images-config-profiles/','/platform/disk-images/disk-images-and-configuration-profiles/','/migrate-to-linode/disk-images/disk-images-and-configuration-profiles/','/guides/linode-configuration-profiles/','/guides/disk-images-and-configuration-profiles/','/platform/disk-images/kvm-reference/','/platform/kvm-reference/','/platform/kvm/','/guides/kvm-reference/'] --- A **configuration profile** functions as a boot loader for a Compute Instance. It controls general boot settings, including the disk the instance will boot from, the disks that will be mounted, the kernel that will be used, and the network interfaces on the instance. Multiple configuration profiles can be created, each one booting from different disks with different settings. This can allow you to try out new Linux distributions without paying for additional Compute Instances (see [Deploy an Image to a Disk on an Existing Compute Instance](/docs/products/tools/images/guides/deploy-image-to-existing-linode/)) or to create custom software testing environments. diff --git a/docs/products/compute/compute-instances/guides/dhcp-ip-address-reference/index.md b/docs/products/compute/compute-instances/guides/dhcp-ip-address-reference/index.md new file mode 100644 index 00000000000..7098e1291a4 --- /dev/null +++ b/docs/products/compute/compute-instances/guides/dhcp-ip-address-reference/index.md @@ -0,0 +1,132 @@ +--- +slug: dhcp-ip-address-reference +title: DHCP IP Address Reference +description: 'A list of all IP addresses used for configurations that rely on DHCP by their data center.' +published: 2021-09-10 +keywords: [dhcp", "cloud firewall", "firewall", "networking"] +tags: ["linode platform","cloud manager"] +aliases: ['/quick-answers/linode-platform/dhcp-ip-address-reference/','/guides/dhcp-ip-address-reference/'] +--- + +In some cases, such as when configuring a firewall, you may need to know the IP addresses that Linode uses for our DHCP servers. Below is a list of all DHCP IP addresses categorized by their data center, to assist in any configuration you may need. + +## Fremont + +``` +173.255.254.129 +50.116.6.33 +66.175.222.121 +50.116.1.128 +173.255.245.39 +66.175.223.241 +``` + +## Dallas + +``` +50.116.29.9 +72.14.182.149 +50.116.18.11 +72.14.189.93 +66.228.55.26 +173.255.199.165 +``` + +## Atlanta + +``` +198.74.55.159 +50.116.46.210 +173.230.139.221 +192.155.93.9 +173.230.139.4 +74.207.234.190 +``` + +## Newark + +``` +97.107.131.49 +69.164.219.39 +66.228.42.172 +66.175.213.64 +97.107.132.48 +96.126.108.78 +``` + +## London + +``` +176.58.106.63 +151.236.222.62 +151.236.218.42 +176.58.111.6 +178.79.152.230 +178.79.187.246 +``` + +## Singapore + +``` +103.3.60.28 +103.3.60.29 +103.3.60.30 +103.3.60.31 +103.3.60.32 +103.3.60.33 +``` + +## Frankfurt + +``` +139.162.128.28 +139.162.128.29 +139.162.128.30 +139.162.128.31 +139.162.128.32 +139.162.128.33 +``` + +## Tokyo + +``` +139.162.65.28 +139.162.65.29 +139.162.65.30 +139.162.65.31 +139.162.65.32 +139.162.65.33 +``` + +## Toronto + +``` +172.105.0.50 +172.105.0.53 +172.105.0.52 +172.105.0.54 +172.105.0.51 +172.105.0.55 +``` + +## Mumbai + +``` +172.105.33.16 +172.105.33.17 +172.105.33.12 +172.105.33.13 +172.105.33.14 +172.105.33.15 +``` + +## Sydney + +``` +172.105.176.4 +172.105.166.4 +172.105.180.4 +172.105.170.4 +172.105.181.4 +172.105.171.4 +``` \ No newline at end of file diff --git a/docs/products/compute/compute-instances/guides/manage-ip-addresses/index.md b/docs/products/compute/compute-instances/guides/manage-ip-addresses/index.md index 93b122fb6ab..cfae910b280 100644 --- a/docs/products/compute/compute-instances/guides/manage-ip-addresses/index.md +++ b/docs/products/compute/compute-instances/guides/manage-ip-addresses/index.md @@ -6,7 +6,7 @@ published: 2016-08-23 modified: 2024-01-30 keywords: ["ip addresses", "ip failover", "swapping ip addresses", "add ip address", "add additional ip address"] tags: ["linode platform","cloud manager","networking"] -aliases: ['/platform/manager/remote-access-classic-manager/','/platform/manager/remote-access/','/remote-access/','/networking/remote-access/', '/guides/remote-access/','/guides/managing-ip-addresses/'] +aliases: ['/platform/manager/remote-access-classic-manager/','/platform/manager/remote-access/','/remote-access/','/networking/remote-access/', '/guides/remote-access/','/guides/managing-ip-addresses/','/guides/find-your-linodes-ip-address/'] --- Each Linode Compute Instance is equipped with several IP addresses, which may enable it to be accessible over the public Internet and other Linode services or accessible just to other Compute Instances within a VPC. This guide covers how to manage these IP addresses (including viewing, adding, removing, transferring, or sharing them) through the Cloud Manager. diff --git a/docs/products/networking/vpc/guides/_index.md b/docs/products/networking/vpc/guides/_index.md index 2ad5cc12c31..61b47e995ae 100644 --- a/docs/products/networking/vpc/guides/_index.md +++ b/docs/products/networking/vpc/guides/_index.md @@ -22,4 +22,4 @@ tab_group_main: ## Going Further -- [Configure a Forward Proxy to Enable Internet Access within a VPC](/docs/guides/forward-proxy-for-vpc/): This guide explains how to use a forward proxy to securely enable public internet access on Compute Instances located entirely behind a VPC. \ No newline at end of file +- [Configure a Forward Proxy to Enable Internet Access within a VPC](/docs/products/networking/vpc/guides/forward-proxy-for-vpc/): This guide explains how to use a forward proxy to securely enable public internet access on Compute Instances located entirely behind a VPC. \ No newline at end of file diff --git a/docs/guides/networking/linode-network/forward-proxy-for-vpc/index.md b/docs/products/networking/vpc/guides/forward-proxy-for-vpc/index.md similarity index 98% rename from docs/guides/networking/linode-network/forward-proxy-for-vpc/index.md rename to docs/products/networking/vpc/guides/forward-proxy-for-vpc/index.md index c00fa06bab7..f414130aee9 100644 --- a/docs/guides/networking/linode-network/forward-proxy-for-vpc/index.md +++ b/docs/products/networking/vpc/guides/forward-proxy-for-vpc/index.md @@ -2,11 +2,9 @@ slug: forward-proxy-for-vpc title: "Configure a Forward Proxy to Enable Internet Access within a VPC" description: "This guide explains how to use a forward proxy to securely enable public internet access on Compute Instances located entirely behind a VPC." -authors: ["Jeff Novotny", "Matt Wildman"] -contributors: ["Jeff Novotny", "Matt Wildman"] published: 2024-02-14 keywords: ['forward proxy vpc','configure forward proxy firewall','access internet from vpc','how to use forward proxy'] -license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)' +aliases: ['/guides/forward-proxy-for-vpc/'] --- Placing sensitive computing resources inside of a [*Virtual Private Cloud* (VPC)](https://en.wikipedia.org/wiki/Virtual_private_cloud) helps limit exposure and protect those systems. However, this also means it is impossible for these servers to directly access the internet without additional infrastructure. This limitation can be resolved through the use of a forward proxy, which acts as a gateway between the VPC and the public internet. This guide explains how to use a forward proxy to enable public internet access for devices within a VPC. It also demonstrates how to secure the VPC using an Akamai Cloud Firewall and how to provide applications with proxy access. diff --git a/docs/products/tools/cloud-manager/_index.md b/docs/products/tools/cloud-manager/_index.md index 5a750d7fa63..26cd360776e 100644 --- a/docs/products/tools/cloud-manager/_index.md +++ b/docs/products/tools/cloud-manager/_index.md @@ -9,6 +9,7 @@ tab_group_main: cascade: date: 2020-06-02 product_description: "Cloud Manager is a user and mobile-friendly interface to deploy and manage virtual machines, configure networking, control user accounts, and access and configure the full range of Linode services." +aliases: ['/platform/manager/','/manager/','/guides/platform/manager/'] --- ## Availability