Yaro

Also you can check your containerd package Unpacking containerd.io (1.5.11-1) over (1.4.3-1) ... After this step everything working fine

@benashz Thanks for your answer. It can be useful for some cases in my view. For now databases with custom plugins can be created through `vault_generic_endpoint` resource. Something like this:...

5.18.0-0.deb11.4-cloud-arm64 ec2 r6gd.4xlarge 13k IOPS and 100%util `sysbench oltp_read_only --tables=10 --table_size=10000000 --mysql-socket=/var/run/mysqld/mysqld.sock --mysql-user=root --mysql-password=test --mysql-db=sbtest --threads=50 --time=600 run` ``` Device r/s rkB/s rrqm/s %rrqm r_await rareq-sz w/s wkB/s wrqm/s %wrqm...

@paulfantom As example, when you want to collect big amount of data, but your infrastructure not contain enough memory. Im using prometheus as local collector for further remote_write into victoria...

https://github.com/prometheus-operator/prometheus-operator/issues/3989

I think it still actual for big clusters, when you collect big amount of metrics. Or like my case: I have 3 small clusters and 5GB of memory not enough...

It makes this library partially unusable

As a workaround, you can create an additional security group for the node group, set all necessary IPs into it and attach them to the node group as the primary...

As i understand this plugin support only gcp