Skip to content

Commit 5fb1d39

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

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
@@ -61,8 +61,8 @@ The following system requirements must be met to install a PCG in MAAS:
6161
For production environments, we recommend using three nodes, each with 100 GiB of storage, as nodes can exhaust the 60
6262
GiB storage with prolonged use. If you initially set up the gateway with one node, you can resize it later.
6363

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

6767
- The DNS server that the PCG installer will use must be able to resolve the DNS names of machines that MAAS deploys so
6868
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)