0.0.5 for early adopters

changelog:

• self signed certificates will be used for mTLS for peer to peer communication (@slintes )
• peer to peer payload moved to grpc (@slintes )
• config CR is now automatically created on boot time, which leads to immediate installation of the poison pill daemonset without any user interaction (@rgolangh )
• software reboot command is now done with double --force argument to avoid graceful reboot
• bug fix - nodes no longer reboot if there's an api-server failure (https://bugzilla.redhat.com/show_bug.cgi?id=1975789)
• lower bound for timeout to delete a node is now automatically calculated. any lower value given in the configuration will be ignored
• poison pill operator will now monitor changes made to the daemonset and re-create it if needed

0.0.4 for early adopters

Changes:

• if poison pill config CR didn't provide any values, some default values will be enforced by the operator
• api-server connectivity check is now done against the /readyz endpoint rather than listing all nodes, this should be more efficient for the api-server and poison-pill pods
• nodes details are updated once in 15 minutes instead of once in 15 seconds
• bug fix which prevented a successful peer to peer communication

0.0.3 for early adopters

The only change in this release is no memory limit on the DS pod, and increase memory request.

0.0.2 for early adopters

super early version for those who are keen to play with poison pill. not for production.