Andrei Kvapil
Andrei Kvapil
no, single volume also has the problem: ``` --- apiVersion: v1 kind: PersistentVolumeClaim metadata: name: foo namespace: tfprod annotations: volume.kubernetes.io/selected-node: c-hv-5 spec: accessModes: - ReadWriteMany resources: requests: storage: "53687091200" storageClassName:...
yeah, they are: ``` # linstor sp l -s data +-------------------------------------------------------------------------------------------------------------+ | StoragePool | Node | Driver | PoolName | FreeCapacity | TotalCapacity | CanSnapshots | State | SharedName |...
@antgamdia thank you for your response. Currently I'm going to add dirty hack to filter out the helm repos and helm releases with specific label It seems the right place...
Yeah, I can confirm that this patch works fine: ```diff diff --git a/cmd/kubeapps-apis/plugins/fluxv2/packages/v1alpha1/release.go b/cmd/kubeapps-apis/plugins/fluxv2/packages/v1alpha1/release.go index fe7ca772d..3b46afbd1 100644 --- a/cmd/kubeapps-apis/plugins/fluxv2/packages/v1alpha1/release.go +++ b/cmd/kubeapps-apis/plugins/fluxv2/packages/v1alpha1/release.go @@ -29,8 +29,10 @@ import ( "k8s.io/apimachinery/pkg/api/errors" "k8s.io/apimachinery/pkg/api/meta" metav1...
This is still in a row
Also if you try to install helmchart using CLI: ``` --- apiVersion: helm.toolkit.fluxcd.io/v2beta1 kind: HelmRelease metadata: name: podinfo namespace: default spec: interval: 10m timeout: 5m chart: spec: chart: podinfo version:...
Okay, my turn: Disable mariadb-operator: ```bash kubectl scale deploy mariadb-operator --replicas=0 ``` Double check that `.spec.replication.primary.podIndex` is correct and points to the same pod specified in`.status.currentPrimaryPodIndex`. I had an issue...
Ideally cluster should be able to recover after executing: ``` FLUSH LOGS; PURGE BINARY LOGS BEFORE NOW(); ``` on master. Manual recovery procedure: https://github.com/mariadb-operator/mariadb-operator/issues/141#issuecomment-1804760231
Just wanted to mention that running commands via exec mechanism in Kubernetes is not intended to be reliable mechanism. However it can be simple replaced by spawning additional pod/job as...
Not stale. This is still in a row