ci: auto-formatting prettier issues

spectrocloud · Oct 18, 2024 · 3134683 · 3134683
1 parent a67837f
commit 3134683
Show file tree

Hide file tree

Showing 4 changed files with 72 additions and 40 deletions.
diff --git a/docs/deprecated/integrations/kubernetes.md b/docs/deprecated/integrations/kubernetes.md
@@ -429,17 +429,23 @@ In this example, Palette is used as the IDP, and all users in the `dev-east-2` w
 
 ### Custom API server endpoint for MAAS clusters
 
-By default, Palette will register a DNS record in MAAS for the deployed cluster, linking it to the IP address(es) of the control plane node(s) of the cluster. However you may not want to depend on MAAS for your cluster DNS record. The Kubernetes pack provides an option to configure a custom API server endpoint for your cluster instead. This feature is only supported in Palette eXtended Kubernetes (PXK).
+By default, Palette will register a DNS record in MAAS for the deployed cluster, linking it to the IP address(es) of the
+control plane node(s) of the cluster. However you may not want to depend on MAAS for your cluster DNS record. The
+Kubernetes pack provides an option to configure a custom API server endpoint for your cluster instead. This feature is
+only supported in Palette eXtended Kubernetes (PXK).
 
-When you configure this option, a DNS record will not be created in MAAS and the configured endpoint will be used instead. If you use this option, you are responsible for:
-* Ensuring the endpoint FQDN can be resolved by your DNS infrastructure
-* Ensuring the endpoint connects to the API server port on your control plane node(s), by either:
-  * pointing directly to the IP address(es) of your control plane node(s), or
-  * pointing to a load balancer that balances traffic to your control plane node(s)
+When you configure this option, a DNS record will not be created in MAAS and the configured endpoint will be used
+instead. If you use this option, you are responsible for:
+
+- Ensuring the endpoint FQDN can be resolved by your DNS infrastructure
+- Ensuring the endpoint connects to the API server port on your control plane node(s), by either:
+  - pointing directly to the IP address(es) of your control plane node(s), or
+  - pointing to a load balancer that balances traffic to your control plane node(s)
 
 :::warning
 
-This endpoint must exist before the cluster gets deployed, otherwise deployment will fail as components will not be able to connect to the cluster API endpoint.
+This endpoint must exist before the cluster gets deployed, otherwise deployment will fail as components will not be able
+to connect to the cluster API endpoint.
 
 :::
 
@@ -458,7 +464,8 @@ cloud:
     customEndpointPort: "6443"
 ```
 
-In order to prevent needing per-cluster profile adjustments (which can become difficult to deal with at scale), it is recommend to use a system macro to automatically populate the cluster name:
+In order to prevent needing per-cluster profile adjustments (which can become difficult to deal with at scale), it is
+recommend to use a system macro to automatically populate the cluster name:
 
 ```yaml hideClipboard {10-14}
 pack:
@@ -817,17 +824,23 @@ In this example, Palette is used as the IDP, and all users in the `dev-east-2` w
 
 ### Custom API server endpoint for MAAS clusters
 
-By default, Palette will register a DNS record in MAAS for the deployed cluster, linking it to the IP address(es) of the control plane node(s) of the cluster. However you may not want to depend on MAAS for your cluster DNS record. The Kubernetes pack provides an option to configure a custom API server endpoint for your cluster instead. This feature is only supported in Palette eXtended Kubernetes (PXK).
+By default, Palette will register a DNS record in MAAS for the deployed cluster, linking it to the IP address(es) of the
+control plane node(s) of the cluster. However you may not want to depend on MAAS for your cluster DNS record. The
+Kubernetes pack provides an option to configure a custom API server endpoint for your cluster instead. This feature is
+only supported in Palette eXtended Kubernetes (PXK).
+
+When you configure this option, a DNS record will not be created in MAAS and the configured endpoint will be used
+instead. If you use this option, you are responsible for:
 
-When you configure this option, a DNS record will not be created in MAAS and the configured endpoint will be used instead. If you use this option, you are responsible for:
-* Ensuring the endpoint FQDN can be resolved by your DNS infrastructure
-* Ensuring the endpoint connects to the API server port on your control plane node(s), by either:
-  * pointing directly to the IP address(es) of your control plane node(s), or
-  * pointing to a load balancer that balances traffic to your control plane node(s)
+- Ensuring the endpoint FQDN can be resolved by your DNS infrastructure
+- Ensuring the endpoint connects to the API server port on your control plane node(s), by either:
+  - pointing directly to the IP address(es) of your control plane node(s), or
+  - pointing to a load balancer that balances traffic to your control plane node(s)
 
 :::warning
 
-This endpoint must exist before the cluster gets deployed, otherwise deployment will fail as components will not be able to connect to the cluster API endpoint.
+This endpoint must exist before the cluster gets deployed, otherwise deployment will fail as components will not be able
+to connect to the cluster API endpoint.
 
 :::
 
@@ -846,7 +859,8 @@ cloud:
     customEndpointPort: "6443"
 ```
 
-In order to prevent needing per-cluster profile adjustments (which can become difficult to deal with at scale), it is recommend to use a system macro to automatically populate the cluster name:
+In order to prevent needing per-cluster profile adjustments (which can become difficult to deal with at scale), it is
+recommend to use a system macro to automatically populate the cluster name:
 
 ```yaml hideClipboard {10-14}
 pack:

diff --git a/docs/docs-content/clusters/data-center/maas/architecture.md b/docs/docs-content/clusters/data-center/maas/architecture.md
@@ -35,8 +35,10 @@ Refer to the [PCG Architecture](../../pcg/architecture.md) section to learn more
 
 ## Custom API server endpoint for MAAS clusters
 
-By default, Palette will register a DNS record in MAAS for the deployed cluster, linking it to the IP address(es) of the control plane node(s) of the cluster. However you may not want to depend on MAAS for your cluster DNS record. The Kubernetes pack provides an option to configure a custom API server endpoint for your cluster instead.
+By default, Palette will register a DNS record in MAAS for the deployed cluster, linking it to the IP address(es) of the
+control plane node(s) of the cluster. However you may not want to depend on MAAS for your cluster DNS record. The
+Kubernetes pack provides an option to configure a custom API server endpoint for your cluster instead.
 
-This feature is only supported in Palette eXtended Kubernetes (PKX). For more
-information, refer to the [Custom API server endpoint for MAAS clusters](../../../integrations/kubernetes.md#custom-api-server-endpoint-for-maas-clusters) section of
-the PXK reference page.
+This feature is only supported in Palette eXtended Kubernetes (PKX). For more information, refer to the
+[Custom API server endpoint for MAAS clusters](../../../integrations/kubernetes.md#custom-api-server-endpoint-for-maas-clusters)
+section of the PXK reference page.
diff --git a/docs/docs-content/clusters/data-center/maas/create-manage-maas-clusters.md b/docs/docs-content/clusters/data-center/maas/create-manage-maas-clusters.md
@@ -31,11 +31,13 @@ create a Kubernetes cluster in MAAS that is managed by Palette.
 
 :::warning
 
-By default, Palette will register a DNS record in MAAS for the deployed cluster, linking it to the IP address(es) of the control plane node(s) of the cluster. However you may not want to depend on MAAS for your cluster DNS record. The Kubernetes pack provides an option to configure a custom API server endpoint for your cluster instead.
+By default, Palette will register a DNS record in MAAS for the deployed cluster, linking it to the IP address(es) of the
+control plane node(s) of the cluster. However you may not want to depend on MAAS for your cluster DNS record. The
+Kubernetes pack provides an option to configure a custom API server endpoint for your cluster instead.
 
-This feature is only supported in Palette eXtended Kubernetes (PXK). For more
-information, refer to the [Custom API server endpoint for MAAS clusters](../../../integrations/kubernetes.md#custom-api-server-endpoint-for-maas-clusters) section of
-the PXK reference page.
+This feature is only supported in Palette eXtended Kubernetes (PXK). For more information, refer to the
+[Custom API server endpoint for MAAS clusters](../../../integrations/kubernetes.md#custom-api-server-endpoint-for-maas-clusters)
+section of the PXK reference page.
 
 :::
 

diff --git a/docs/docs-content/integrations/kubernetes.md b/docs/docs-content/integrations/kubernetes.md
@@ -404,17 +404,23 @@ In this example, Palette is used as the IDP, and all users in the `dev-east-2` w
 
 ### Custom API server endpoint for MAAS clusters
 
-By default, Palette will register a DNS record in MAAS for the deployed cluster, linking it to the IP address(es) of the control plane node(s) of the cluster. However you may not want to depend on MAAS for your cluster DNS record. The Kubernetes pack provides an option to configure a custom API server endpoint for your cluster instead. This feature is only supported in Palette eXtended Kubernetes (PXK).
+By default, Palette will register a DNS record in MAAS for the deployed cluster, linking it to the IP address(es) of the
+control plane node(s) of the cluster. However you may not want to depend on MAAS for your cluster DNS record. The
+Kubernetes pack provides an option to configure a custom API server endpoint for your cluster instead. This feature is
+only supported in Palette eXtended Kubernetes (PXK).
 
-When you configure this option, a DNS record will not be created in MAAS and the configured endpoint will be used instead. If you use this option, you are responsible for:
-* Ensuring the endpoint FQDN can be resolved by your DNS infrastructure
-* Ensuring the endpoint connects to the API server port on your control plane node(s), by either:
-  * pointing directly to the IP address(es) of your control plane node(s), or
-  * pointing to a load balancer that balances traffic to your control plane node(s)
+When you configure this option, a DNS record will not be created in MAAS and the configured endpoint will be used
+instead. If you use this option, you are responsible for:
+
+- Ensuring the endpoint FQDN can be resolved by your DNS infrastructure
+- Ensuring the endpoint connects to the API server port on your control plane node(s), by either:
+  - pointing directly to the IP address(es) of your control plane node(s), or
+  - pointing to a load balancer that balances traffic to your control plane node(s)
 
 :::warning
 
-This endpoint must exist before the cluster gets deployed, otherwise deployment will fail as components will not be able to connect to the cluster API endpoint.
+This endpoint must exist before the cluster gets deployed, otherwise deployment will fail as components will not be able
+to connect to the cluster API endpoint.
 
 :::
 
@@ -433,7 +439,8 @@ cloud:
     customEndpointPort: "6443"
 ```
 
-In order to prevent needing per-cluster profile adjustments (which can become difficult to deal with at scale), it is recommend to use a system macro to automatically populate the cluster name:
+In order to prevent needing per-cluster profile adjustments (which can become difficult to deal with at scale), it is
+recommend to use a system macro to automatically populate the cluster name:
 
 ```yaml hideClipboard {10-14}
 pack:
@@ -758,17 +765,23 @@ In this example, Palette is used as the IDP, and all users in the `dev-east-2` w
 
 ### Custom API server endpoint for MAAS clusters
 
-By default, Palette will register a DNS record in MAAS for the deployed cluster, linking it to the IP address(es) of the control plane node(s) of the cluster. However you may not want to depend on MAAS for your cluster DNS record. The Kubernetes pack provides an option to configure a custom API server endpoint for your cluster instead. This feature is only supported in Palette eXtended Kubernetes (PXK).
+By default, Palette will register a DNS record in MAAS for the deployed cluster, linking it to the IP address(es) of the
+control plane node(s) of the cluster. However you may not want to depend on MAAS for your cluster DNS record. The
+Kubernetes pack provides an option to configure a custom API server endpoint for your cluster instead. This feature is
+only supported in Palette eXtended Kubernetes (PXK).
+
+When you configure this option, a DNS record will not be created in MAAS and the configured endpoint will be used
+instead. If you use this option, you are responsible for:
 
-When you configure this option, a DNS record will not be created in MAAS and the configured endpoint will be used instead. If you use this option, you are responsible for:
-* Ensuring the endpoint FQDN can be resolved by your DNS infrastructure
-* Ensuring the endpoint connects to the API server port on your control plane node(s), by either:
-  * pointing directly to the IP address(es) of your control plane node(s), or
-  * pointing to a load balancer that balances traffic to your control plane node(s)
+- Ensuring the endpoint FQDN can be resolved by your DNS infrastructure
+- Ensuring the endpoint connects to the API server port on your control plane node(s), by either:
+  - pointing directly to the IP address(es) of your control plane node(s), or
+  - pointing to a load balancer that balances traffic to your control plane node(s)
 
 :::warning
 
-This endpoint must exist before the cluster gets deployed, otherwise deployment will fail as components will not be able to connect to the cluster API endpoint.
+This endpoint must exist before the cluster gets deployed, otherwise deployment will fail as components will not be able
+to connect to the cluster API endpoint.
 
 :::
 
@@ -787,7 +800,8 @@ cloud:
     customEndpointPort: "6443"
 ```
 
-In order to prevent needing per-cluster profile adjustments (which can become difficult to deal with at scale), it is recommend to use a system macro to automatically populate the cluster name:
+In order to prevent needing per-cluster profile adjustments (which can become difficult to deal with at scale), it is
+recommend to use a system macro to automatically populate the cluster name:
 
 ```yaml hideClipboard {10-14}
 pack: