Tim
Tim
this in addition to #10842 would be great for various B2B use-cases. Is this feature on the pipeline?
having option 4 would be great. [Mayastor](https://mayastor.gitbook.io/introduction/quickstart/preparing-the-cluster) is a popular storage solution for high IOPS workloads such as postgresql but requires hugepages. For the default postgres image to work, resources...
~~No, it seems like the hugepage limits need to be set on the container level (see the blog article). Even with hugepages enabled on the cluster, postgres fails to start....
+1 for high availability for volume targets, this would be really great to have!
this issue is still present in `v2.39.1`
similar to https://github.com/hasura/graphql-engine/issues/9393 we had to downgrade nodejs on our cardano-graphql server to major version 18 to fix the issue (before we were running 20 and 22).
OpenEBS had a component called ndm [(node-disk-manager)](https://github.com/openebs-archive/node-disk-manager) that was quite handy to manage block-devices. HostPath and OS disks could be excluded with filters, e.g.: ```yaml filterconfigs: - key: os-disk-exclude-filter name:...
Thanks @Szpadel for reporting this, I've observed the same kernel panic on talos 1.3.5 with kernel 5.15.94 just now.
Unfortunately I did not have kernel log delivery set up so I only see the last couple of lines via IPMI (see below) since talos afaik does not keep dmesg...
In my case it happened during the night and I was not expecting it to happen otherwise I would have logged dmesg. I'd like to do some further testing with...