Skip to content

Commit cba1e24

Browse files
authored
Merge branch 'master' into docs-rel-4-8-a
2 parents 9a2472e + 1d41c8f commit cba1e24

File tree

4 files changed

+166
-1
lines changed

4 files changed

+166
-1
lines changed

README.md

Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -800,6 +800,92 @@ The snippet above will work with the example partial we have in our repository,
800800
Note that the `message` field corresponds to the `{props.message}` reference in the `_partials/_partial_example.mdx`
801801
file.
802802
803+
### Numbered Lists
804+
805+
Multi-step partials that do not begin a new procedure (start with 1) cannot be reused if the partial is written in
806+
typical MDX syntax. The example below shows a small snippet of a procedure.
807+
808+
```mdx
809+
---
810+
partial_category: clusters-aws-account-setup
811+
partial_name: example
812+
---
813+
814+
1. **Validate** your AWS credentials. A green check mark indicates valid credentials.
815+
816+
2. Toggle **Add IAM Policies** on and use the **Policies** drop-down menu to select any desired IAM policies.
817+
818+
3. Select **Confirm** to add your AWS account to Palette.
819+
```
820+
821+
This partial could be reused in several places, as there are several types of AWS accounts and authentication methods.
822+
However, the steps prior to this partial vary based on the procedure. For example, the partial may need to start at step
823+
6 for AWS Commercial cloud but step 10 for AWS Secret cloud, which makes reuse tricky. Since MDX files are generated at
824+
runtime instead of buildtime, implementing it in either of the following ways will _not_ work.
825+
826+
<!-- prettier-ignore-start -->
827+
828+
```md
829+
6. In Palette, paste the role ARN into the **ARN** field.
830+
831+
7. <PartialComponent category="clusters-aws-account-setup" name="example" />
832+
<!-- creates a nested list on step 7 that begins with step 1 -->
833+
834+
<PartialComponent category="clusters-aws-account-setup" name="example" /> <!-- creates a new list starting at 1 -->
835+
```
836+
837+
<!-- prettier-ignore-end -->
838+
839+
There are several other ways you can manipulate the partial in an attempt to fix this issue, but only _one_ works. To
840+
reuse a mid-procedure partial that contains a numbered list, create each step item _except the first step_ as an HTML
841+
list item (`<li>`).
842+
843+
```mdx
844+
---
845+
partial_category: clusters-aws-account-setup
846+
partial_name: example
847+
---
848+
849+
**Validate** your AWS credentials. A green check mark indicates valid credentials.
850+
851+
<li> Toggle **Add IAM Policies** on and use the **Policies** drop-down menu to select any desired IAM policies.</li>
852+
853+
<li>Select **Confirm** to add your AWS account to Palette.</li>
854+
```
855+
856+
When you reference the partial in a markdown file, put the partial _after_ the numbered step. Doing so establishes the
857+
step number for the first item, and the steps indicated with `<li>` are rendered with the correct subsequent numbers.
858+
859+
<!-- prettier-ignore-start -->
860+
861+
```md
862+
6. In Palette, paste the role ARN into the **ARN** field.
863+
864+
7. <PartialComponent category="clusters-aws-account-setup" name="example" />
865+
866+
8. Additional step.
867+
```
868+
869+
<!-- prettier-ignore-end -->
870+
871+
Any steps that come _after_ partial are updated with the correct values during runtime. For example, the above partial
872+
would be rended as follows.
873+
874+
<!-- prettier-ignore-start -->
875+
876+
```md
877+
6. In Palette, paste the role ARN into the **ARN** field.
878+
879+
7. **Validate** your AWS credentials. A green check mark indicates valid credentials.
880+
881+
8. Toggle **Add IAM Policies** on and use the **Policies** drop-down menu to select any desired IAM policies.
882+
883+
9. Select **Confirm** to add your AWS account to Palette.
884+
885+
10. Additional step.
886+
```
887+
<!-- prettier-ignore-end -->
888+
803889
## Palette/VerteX URLs
804890
805891
A special component has been created to handle the generation of URLs for Palette and VerteX. The component is called

docs/docs-content/integrations/edge-native-byoi.mdx

Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,78 @@ tags: ["packs", "byoos", "operating system", "edge"]
1616

1717
<Tabs queryString="parent">
1818

19+
<TabItem label="2.1.x" value="2.1.x">
20+
21+
BYOOS enables you to use a custom OS for your Edge host. The custom OS must include all the Edge artifacts and provider
22+
images required by the Edge Installer. Refer to the
23+
[Build Edge Artifacts](../clusters/edge/edgeforge-workflow/palette-canvos/palette-canvos.md) guide for steps on how to
24+
create a custom OS that includes all the required components for the Edge Installer.
25+
26+
Next, select the BYOOS pack and fill out the required parameters during the cluster profile creation process.
27+
28+
The `options.system.uri` parameter specifies the location of the BYOOS image. This parameter is required and included in your pack YAML file by default.
29+
30+
The following section provides the list of optional parameters you can customize in the pack YAML file.
31+
32+
### Customizable Optional Parameters
33+
34+
You can customize the following sections of the pack YAML file:
35+
36+
* The `drain` section is included by default and controls how nodes are drained during cluster upgrades. If you do not make any changes in this section, the default drain values are used.
37+
38+
* The `providerCredentials` section supplies the credentials for the registry that contains your provider images.
39+
40+
* The `stages` section defines the cloud-init stages that run during the node boot process. Stages defined here are processed in the same way as stages defined in a `user-data` file. Refer to the [Installer Reference Cloud Init Stages](https://docs.spectrocloud.com/clusters/edge/edge-configuration/installer-reference/#cloud-init-stages) for more information.
41+
42+
43+
The following YAML configuration file example demonstrates how these sections are used, with inline comments describing all available fields.
44+
45+
```yaml
46+
pack:
47+
content:
48+
images:
49+
- image: '{{.spectro.pack.edge-native-byoi.options.system.uri}}' # This parameter uses the value set in the options section as the image for the pack.
50+
# Uncomment the following parameters to change them. Otherwise, the pack uses the default values.
51+
#drain:
52+
#drainPods: auto # Drain pods during cluster upgrades. Set this value to false to skip draining.
53+
#podSelector: # Specify the pod selector options for draining specific pods.
54+
#cordon: true # Cordon the node before draining. This prevents new pods from being scheduled.
55+
#timeout: 60 # Maximum time, in seconds, to wait for drain to complete. Set this value to 0 for no timeout.
56+
#gracePeriod: 60 # Time, in seconds, allocated to each pod to terminate gracefully. Set this parameter to a negative value to use the pod's default time.
57+
#ignoreDaemonSets: true # Ignore DaemonSet-managed pods during drain.
58+
#deleteLocalData: true # Allow drain to proceed even if pods use emptyDir. This will delete local data.
59+
#force: true # Force drain even if there are pods without controllers.
60+
#disableEviction: false # Use delete instead of eviction, and bypass PodDisruptionBudgets. Use this parameter with caution.
61+
#skipWaitForDeleteTimeout: 60 # Skip waiting for a pod if its DeletionTimestamp is older than this value (in seconds).
62+
options:
63+
system.uri: "" # The provider image URL for appliance mode. Set this value to the appliance's image location.
64+
65+
providerCredentials:
66+
registry: example.com/spectro-images # The registry location for your provider images. This is prepended to the value in your options.system.uri setting.
67+
user: user # The username for the registry.
68+
password: "password" # The password for the registry.
69+
certificates: | # The security certificate for the registry, in PEM format.
70+
xxx
71+
72+
# Cloud init stages behave the same whether they are defined in the BYOOS pack or in user data.
73+
stages:
74+
initramfs: # Stage name, typically for early boot/initramfs operations.
75+
- name: Test stage # The name of the step within the stage.
76+
commands:
77+
- echo "hello world" # The command to execute. Prints "hello world" for testing.
78+
79+
```
80+
81+
82+
### Agent Mode
83+
84+
To enable agent mode with the BYOOS Edge OS pack, expand the **Presets** section from the YAML editor view. Toggle the
85+
**Agent Mode** switch to enable agent mode. Check out the
86+
[Install Palette Agent](../deployment-modes/agent-mode/install-agent-host.md) guide for additional guidance on
87+
installing the Palette Agent.
88+
89+
</TabItem>
90+
1991
<TabItem label="2.0.x" value="2.0.x">
2092

2193
BYOOS enables you to use a custom OS for your Edge host. The custom OS must include all the Edge artifacts and provider

docs/docs-content/introduction/introduction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ configurations but focus on the stuff that matters.
9090
### IT Operations and SREs
9191

9292
Declarative management makes life easier for IT teams, with consistency, repeatability, and all the enterprise-grade
93-
controls and governance they need - especially when moving to production
93+
controls and governance they need - especially when moving to production.
9494
[Cluster Profiles](../profiles/cluster-profiles/cluster-profiles.md) enable them to define and re-use full-stack
9595
clusters and support them across the entire lifecycle without having to write scripts, as well as integrate with
9696
existing tools and methodologies.

src/css/custom.scss

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -257,6 +257,13 @@ p img.markdown-image {
257257
line-height: 1.6em;
258258
}
259259

260+
// Properly space mdx list items
261+
262+
.markdown li {
263+
margin-top: var(--ifm-list-paragraph-margin);
264+
margin-bottom: var(--ifm-paragraph-margin-bottom);
265+
}
266+
260267
// Navbar Ask AI button
261268

262269
.navbar-ai-button {

0 commit comments

Comments
 (0)