Andrei Kvapil
Andrei Kvapil
Ahh the last report was wrong due to missing connectivity between the nodes, I was confused by states `UpToDate` on both of them
Is there any option to disable such verification mechanism for all resources in argocd?
Hey, sorry, for insufficient description to this PR. I'm solving the issue of using LVM over shared storage (DAS). Eg. when you have shared LUN connected to multiple nodes in...
I'm thinking about additional level, something like this: ```yaml storage: resizeInUseVolumes: true additionalOptionHere: true volume: # OneOf emptyDir: {} volumeClaimTemplate: {} ``` What is your ideas?
```yaml storage: resizeInUseVolumes: true additionalOptionHere: true emptyDir: {} volumeClaimTemplate: {} ```
Hi, I'd like to mention that MetalLB currently uses a consistent hashing algorithm. It calculates the hash from nodeName + serviceIP for each endpoint, sorts the results, and selects the...
I think we need to introduce a new resource to track the process of updates: ```yaml apiVersion: cozystack.io/v1alpha1 kind: TalosNode metadata: name: srv1 ownerReferences: - apiVersion: v1 kind: Node name:...
> You have created a new MariaDB, are you also using the previous PVCs How to recover a new cluster from previous PVCs?
Okay I fixed it by two commands: ``` kubectl exec my-db-1 -ti -- sh -c "printf '%s\n' '[galera]' 'wsrep_new_cluster=\"ON\"' > /etc/mysql/mariadb.conf.d/1-bootstrap.cnf" kubectl exec my-db-1 -ti -- sed -i 's/safe_to_bootstrap: 0/safe_to_bootstrap:...
Agree, I have the same issue on latest version