community.kubernetes VS keydb-operator

It's hard to say. I don't see too much point in running Ansible inside Terraform or Terraform inside Ansible (yes, you can go either way). Ansible lagged for years on its support of kubernetes and helm (it had it, but it didn't work). Now (like in the last 12 months) got good support for both, but it might be too late. Terraform has the majority of mind share when it comes to Kubernetes support.

If you're only doing AWS or Google Cloud, Ansible can do that. Whether it does it better or worse than Terraform is all dependent on your use case.

If you're doing anything on premise, or outside of GCP/AWS, Ansible can do that as well. From the using OOB management (HP iLO/Dell iDRAC) to install the OS, to configuring vmware clusters to deploying k8s to declaring resources within k8s. Got network switches and firewalls at your office? You can manage that with Ansible. If you have a bunch of edge compute, Ansible can manage that as well.

What it comes down to is if you've got teams working with anything outside of AWS/GCP. They'll probably be using Ansible, and since you've already go Ansible knowledge across your organization, it would make sense to leverage that expertise and Ansible's cloud integrations.

All of that said - Terraform is much more popular when it comes to the major cloud platforms. If all you have is cloud, then you'll probably start with Terraform and stay there.

https://github.com/ansible-collections/community.kubernetes

https://registry.terraform.io/providers/hashicorp/kubernetes/latest https://github.com/ansible-collections/community.kubernetes

I would like to use Ansible only for deployment. This is save to use it https://github.com/ansible-collections/community.kubernetes right?

Originally, my goal with a Single Board Computer (SBC) was to unwind and take a break from the usual work routine. I opted for an opi5 in the way. However, lo and behold, here I am, enabling virtualization, almost like it's a rarity in my line of work over at Krestomatio! It's been a fun experience, nonetheless.

KeyDB is a multithreading, drop-in alternative to Redis. Keydb-operator easily creates a standalone (1 replica) or a multimaster (3 replicas) KeyDB in-memory database. When KeyDB is in multimaster mode, it is possible to have more than one master, allowing read/write operations to all them. That helps for high availability and fault tolerance.