Skip to content

Commit 0ce23a5

Browse files
Linus-SpectroCloudLinus-SpectroCloud
committed
Merge branch 'master' of github.com:spectrocloud/librarium into feat/doc-2047-edge-phase-2
2 parents 6fef728 + d9eb376 commit 0ce23a5

File tree

7 files changed

+399
-295
lines changed

7 files changed

+399
-295
lines changed

‎docs/docs-content/clusters/edge/site-deployment/deploy-custom-registries/upload-images-to-registry.md‎

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -128,6 +128,25 @@ Palette Edge CLI to download the images and upload them to the external registry
128128
palette content push --file <path-to-content-bundle> --registry <registry-address>
129129
```
130130

131+
<!-- https://spectrocloud.atlassian.net/browse/PLT-1840 -->
132+
133+
:::info
134+
135+
[Amazon Elastic Container Registry (ECR)](https://docs.aws.amazon.com/ecr/) now allows repository path creation on
136+
the fly. You must create a repository creation template in ECR to enable this for your registry before uploading
137+
your content bundle images. Refer to the
138+
[Creating a repository creation template in Amazon ECR](https://docs.aws.amazon.com/AmazonECR/latest/userguide/repository-creation-templates-create.html)
139+
guide for further information.
140+
141+
For example, you can create a template for your registry using the AWS CLI by issuing the following command. You can
142+
then push bundle content at the `<registry-url>/<prefix>` path.
143+
144+
```shell
145+
aws ecr create-repository-creation-template --prefix <prefix> --applied-for CREATE_ON_PUSH --description "Auto-create repos on push"
146+
```
147+
148+
:::
149+
131150
</TabItem>
132151

133152
<TabItem value="Palette Edge CLI" label="Palette Edge CLI">

‎docs/docs-content/integrations/piraeus-csi.mdx‎

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
sidebar_label: "Piraeus CSI"
3+
title: "Piraeus CSI"
4+
description: "Piraeus CSI integration in Spectro Cloud"
5+
type: "integration"
6+
hide_table_of_contents: true
7+
category: ["storage", "amd64"]
8+
sidebar_class_name: "hide-from-sidebar"
9+
tags: ["packs", "piraeus-csi", "storage"]
10+
---
11+
12+
<RedirectPackPage packName="piraeus-csi" />
13+
14+
## Versions Supported
15+
16+
<Tabs queryString="parent">
17+
<TabItem label="2.8.x" value="2.8.0">
18+
19+
For Palette or Palette VerteX deployments that use Piraeus/LINSTOR-backed storage, and where the `drbd-loader` init container is configured with `LB_HOW=compile`, the container image must include the appropriate Linux kernel headers.
20+
21+
The `drbd-loader` dynamically compiles the DRBD kernel module at runtime on the target node when `LB_HOW=compile` is set. This compilation process requires access to the kernel headers and related build tooling that match the running kernel on the host.
22+
23+
If the required kernel headers are missing or do not match the running kernel version, the module compilation fails, and the DRBD kernel module does not load.
24+
25+
Therefore, when using `LB_HOW=compile`, ensure that you follow these guidelines.
26+
27+
1. Ensure that you include kernel headers that match the Palette or Palette VerteX host kernel version in the container image used by the `drbd-loader` init container.
28+
29+
<TabItem label="Palette" value="palette">
30+
31+
For Palette deployments, add the following line to the Dockerfile or build configuration of the `drbd-loader` image.
32+
33+
```dockerfile
34+
apt-get update && apt-get install --assume-yes linux-headers-$(uname --kernel-release)
35+
```
36+
37+
</TabItem>
38+
39+
<TabItem label="Palette VerteX" value="vertex">
40+
For Palette VerteX deployments, add the following line to the Dockerfile or build configuration of the `drbd-loader` image.
41+
42+
```dockerfile
43+
kernel=$(ls /lib/modules/ | grep fips | head -1)
44+
apt-get update && apt-get install --assume-yes linux-headers-${kernel}
45+
```
46+
</TabItem>
47+
2. Your nodes must have internet access at runtime to download the DRBD source code from the LINBIT repositories for the compilation process to succeed.
48+
49+
If your nodes do not have internet access, such as in airgapped environments, you need to use precompiled modules by setting `LB_HOW=shipped_modules` to use prebuilt DRBD modules instead of compiling dynamically.
50+
51+
</TabItem>
52+
</Tabs>

‎docs/docs-content/release-notes/known-issues.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ The following table lists all known issues that are currently active and affecti
1616

1717
| Description | Workaround | Publish Date | Product Component |
1818
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ---------------------------- |
19-
| <!-- https://spectrocloud.atlassian.net/browse/DOC-2594 --> [EKS clusters](../clusters/public-cloud/aws/eks.md) deployed with the <VersionedLink text="AWS Cluster Autoscaler" url="/integrations/packs/?pack=aws-cluster-autoscaler" /> pack fail to upgrade the Kubernetes version of their worker node groups or `MachinePools`. | Refer to [Scenario - EKS Worker Nodes Configured with Autoscaler Fail to Upgrade](../troubleshooting/cluster-deployment.md#scenario---eks-worker-nodes-configured-with-autoscaler-fail-to-upgrade) for the workaround. | February 21, 2026 | Packs, Clusters |
19+
| <!-- https://spectrocloud.atlassian.net/browse/DOC-2602 --> When global DNS values are configured through user data, [Local UI](../clusters/edge/local-ui/local-ui.md) displays the Edge host's local stub resolver address from `/etc/resolv.conf`, 127.0.0.53, instead of the upstream DNS server addresses. DNS resolution is not affected. | No workaround available. | March 5, 2026 | Edge |
2020
| <!-- https://spectrocloud.atlassian.net/browse/PAC-3669 --> Clusters configured with <VersionedLink text="Palette eXtended Kubernetes Edge (PXK-E)" url="/integrations/packs/?pack=edge-k8s" /> pack version 1.33.6 and an OIDC provider fail to deploy successfully. | Upgrade to newer Palette eXtended Kubernetes Edge (PXK-E) pack versions. Alternatively, if remaining on PXK-E version 1.33.6, refer to [Scenario - Configure OIDC for Palette eXtended Kubernetes Edge (PXK-E) 1.33.6](../troubleshooting/pack-issues.md#scenario---configure-oidc-for-palette-extended-kubernetes-edge-pxk-e-1336) for the workaround. | February 6, 2026 | Packs, Clusters |
2121
| <!-- https://spectrocloud.atlassian.net/browse/DOC-2504 --> Existing EKS clusters configured with mismatched Classless Inter-Domain Routing (CIDR) values and NodePool customization using AWS Launch Templates have nodes with incorrect `kubelet` CIDR and `clusterDNS` values. The fix introduced in Palette 4.8.25 applies only to newly created nodes and does not remediate existing nodes. As a result, pods scheduled on the affected nodes may be unable to reach `clusterDNS`. | Restart the pods scheduled on affected nodes so that they are rescheduled onto a healthy node. Normal operation is restored pods are scheduled on nodes with the correct `kubelet` CIDR configurations. | January 30, 2026 | Clusters |
2222
| <!-- https://spectrocloud.atlassian.net/browse/DOC-2490 --> The `spectrocloud_registry_oci` resource or data source continuously detects changes and repeatedly reconciles when created or imported using the Crossplane provider with `is_synchronization` enabled. The Terraform `plan` operation and audit logs also incorrectly report changes. This affects [Spectro Cloud Terraform provider](https://registry.terraform.io/providers/spectrocloud/spectrocloud/latest/docs) and [Spectro Cloud Crossplane provider](https://marketplace.upbound.io/providers/crossplane-contrib/provider-palette) version 0.27.0 or later. | No workaround available. | January 30, 2026 | Terraform, Crossplane |
@@ -147,6 +147,7 @@ for information on the fix version and the date the issue was resolved.
147147

148148
| Description | Publish Date | Product Component | Fix Version |
149149
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ | ---------------------------- | ----------- |
150+
| <!-- https://spectrocloud.atlassian.net/browse/PCP-6089 --> [EKS clusters](../clusters/public-cloud/aws/eks.md) deployed with the <VersionedLink text="AWS Cluster Autoscaler" url="/integrations/packs/?pack=aws-cluster-autoscaler" /> pack fail to upgrade the Kubernetes version of their worker node groups or `MachinePools`. Refer to [Scenario - EKS Worker Nodes Configured with Autoscaler Fail to Upgrade](../troubleshooting/cluster-deployment.md#scenario---eks-worker-nodes-configured-with-autoscaler-fail-to-upgrade) for the workaround. | February 21, 2026 | Packs, Clusters | 4.8.37 |
150151
| <!-- https://spectrocloud.atlassian.net/browse/DOC-2587 --> [Virtual Machine Orchestrator](../vm-management/vm-management.md) Day-2 operations, such as VM start, stop, restart, and migrate, do not complete when triggered using the [Palette API](/api/introduction) on environments using 4.8.33. | February 24, 2026 | Virtual Machine Orchestrator | 4.8.35 |
151152
| On Edge clusters whose hosts run Ubuntu 24.04 with a Unified Kernel Image (UKI), CoreDNS pods may enter the `CrashLoopBackOff` state with logs showing `[FATAL] plugin/loop: Loop (127.0.0.1:<ephemeral-port> -> :53) detected for zone "."`. This happens because `/etc/resolv.conf` is symlinked to `/run/systemd/resolve/stub-resolv.conf`, which lacks real DNS server entries. As a result, CoreDNS forwards DNS queries to itself, creating a recursive loop. Refer to [Troubleshooting - Edge](../troubleshooting/edge/edge.md#scenario---coredns-pods-stuck-in-crashloopbackoff-due-to-dns-loop) for the workaround. | October 7, 2025 | Edge | 4.8.21 |
152153
| [Agent mode](../deployment-modes/agent-mode/agent-mode.md) Edge cluster nodes configured with Agent version 4.8.1 may lose pre-existing `systemd-networkd` configurations (VLANs, bonds, and bridges) after a reboot. This occurs because the cleanup logic intended to remove stale VLAN configurations inadvertently deletes valid, pre-existing configurations not created through user data. | December 5, 2025 | Edge | 4.8.12 |

0 commit comments

Comments
 (0)