piraeus-operator icon indicating copy to clipboard operation
piraeus-operator copied to clipboard

The Piraeus Operator manages LINSTOR clusters in Kubernetes.

Results 85 piraeus-operator issues
Sort by recently updated
recently updated
newest added

@WanzenBug in flowing to discussion in https://github.com/piraeusdatastore/piraeus-operator/issues/180#issuecomment-1050698412 I think I found an alternative way to add customizations to the generated manifests. KubeVirt project has `customizeComponents` option, which is working the...

Not sure if this is a bug or feature, so let's consider this first. The piraeus-operator does not share drbd configuration between the satellite pod and node, thus even if...

The csi-nodes, ha-controller and csi-controller are unable to connect to the piraeus-op-cs service. My helm command is: ``` helm install -f storage-pools.yaml \ piraeus-op piraeus-operator/charts/piraeus --create-namespace -n linstor ``` I...

Hi, We've been following the [current documentation](https://github.com/piraeusdatastore/piraeus-operator#terminating-helm-deployment) on how to uninstall the piraeus helm chart. We have noticed there was a few additional steps to remove any finalizers from the...

documentation
good first issue

If node come offline for 2 hours then return back it stays `EVICTED` even when linstor-satellite succefully started. Shouldn't we recover such nodes automatically by piraeus-operrator?

bug

Hi, Extra easy question, https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#_installing_the_linstor_gui mentions a built-in UI. Is this UI something that is available on Piraeus? Thank you.

Sooner or later resources get out of sync - often without notice. This is especially critical for databases and other StatefulSets. To avoid unexpected dataloss/corruption during node draining or restarts...

enhancement

CSI plugin can't mount DRBD volume to pod with error `Device or resource busy while setting up superblock`. After this happening, k8s controller (job in my case), creates new pod,...

bug

The version of piraeus-operator must be set and updated together with the helm chart itself. https://github.com/piraeusdatastore/piraeus-operator/blob/52eb3454f0036e50694b5e5c4378e25d3907f26c/charts/piraeus/values.yaml#L58 Otherwise you have risk on running old operator version with new helm-chart, which is...

Follows up https://github.com/piraeusdatastore/piraeus-operator/pull/219#issuecomment-1027282815 Yeah, now I understand why you decided to get rid of stork. It's quite huge, slow, contains a lot of complex controllers and requires ultimate permissions on...