Skip to content

Commit 8af9fe3

Browse files
committed
docs: fix broken MAAS API auth link (#9504)
* docs: fix broken MAAS API auth link * Apply suggestion from @brent-eritou * ci: auto-formatting prettier issues --------- Co-authored-by: brent-eritou <[email protected]> (cherry picked from commit ae78286)
1 parent da19ca6 commit 8af9fe3

File tree

1 file changed

+2
-2
lines changed
  • docs/docs-content/clusters/pcg/deploy-pcg

1 file changed

+2
-2
lines changed

docs/docs-content/clusters/pcg/deploy-pcg/maas.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,8 +66,8 @@ The following system requirements must be met to install a PCG in MAAS:
6666
For production environments, we recommend using three nodes, each with 100 GiB of storage, as nodes can exhaust the 60
6767
GiB storage with prolonged use. If you initially set up the gateway with one node, you can resize it later.
6868

69-
- An active MAAS API key. Refer to the [Authenticating to the MAAS API](https://maas.io/docs/api) guide to learn more
70-
about how to create an API key.
69+
- An active MAAS API key. Refer to the [Authenticating to the MAAS API](https://canonical.com/maas/docs) guide to learn
70+
more about how to create an API key.
7171

7272
- The DNS server that the PCG installer will use must be able to resolve the DNS names of machines that MAAS deploys so
7373
it can connect to them. The default setup is to use the MAAS server as the DNS server for any bare metal servers that

0 commit comments

Comments
 (0)