Balazs Zachar

Maybe relevant and could help a bit in planning (id is not generated at install time): In RHEL9, the `/etc/iscsi/initiatorname.iscsi` file (which contains the id like InitiatorName=iqn.1994-05.com.redhat:a5a8dd56f673 ) gets created...

@zmrow well, let me collect what I am aware of: * for iSCSI, when the daemonset starts, it tries to read the initiator ID from the /etc/iscsi/initiatorname.iscsi file. For each...

The lack of the possibility to use persistent storage is one of the major limitations (and the only blocker in our case with EKS-A BM) of using bottlerocket on bare...

Hi @etungsten, Thank you for the update, it seems to be a very interesting approach. Looking forward to test ot when it is ready. I must say, I don't really...

There seems to be an official variant called metal-k8s-VERSION. From the Readme: > The following variants are designed to be Kubernetes worker nodes on bare metal I wonder how would...

@enneitex , just to clarify for everyone: is putting the operator to the control plane nodes the recommended setup? If yes is this documented somewhere?

@heatherezell , any update? We defined an alert in prometheus for vault_raft_peers and we realized that the metric is simply gone... This is pretty dangerous and if this is the...

We would be interested in a "nicer" solution as we are about to upgrade our clusters as well. According to [this comment](https://github.com/kubernetes/kubernetes/issues/127316#issuecomment-2355560226) this should be fixed in cluster api so,...

Here is another use case that is common in platform teams: * Run a playbook to gather information/input for the next playbook * Use the output from the first playbook...