Search
8 results for “timstoop”
-
Considering a true multi-cloud #Kubernetes cluster, how would you solve the storage? Is there a solution that allows you to use a single #StorageClass that maybe selects the appropriate StorageClass based on the location of the Pod? Like, if I build a Kubernetes cluster using both GCE and AWS, can I create a single StorageClass that I can use in both locations and it will choose the correct backing storage? How do others solve that issue?
-
I dislike how so many tools add magic without a good opt-out mechanism or even an indication where the magic is added. Ie. using clusterapi and capt (tinkerbell) your control plane nodes get the label "node.kubernetes.io/exclude-from-external-load-balancers", but I have no idea which component adds the label nor how to disable it, as I don't want it for my particular setup.
-
After over 25 years on Linux, learning proves challenging. Most online texts rehash what I know or offer basic refreshers. I seek a resource bridging the gap between basic docs and source code, providing detailed insights without skipping low-level steps, catering to non-programmers like myself. I find myself reading code more often, but I don't _like_ reading code. #LinuxLearning #TechInsights #TechJourney #SkillDevelopment #OnlineLearning
-
Just found out that the #Percona MySQL #Operator, which deploys a Percona XtraDB/Galera Cluster on #Kubernetes quite nicely and sets up #ProxySQL to be able to split traffic between read and write queries, does not, actually, loadbalance over the nodes. There's a bug open since May 2021 which just disables this feature by providing incorrect config in ProxySQL. So this killer feature, which is still advertised in the docs, simply does not work at all. And there's no way to fix it manually.
-
Just found out that the #Percona MySQL #Operator, which deploys a Percona XtraDB/Galera Cluster on #Kubernetes quite nicely and sets up #ProxySQL to be able to split traffic between read and write queries, does not, actually, loadbalance over the nodes. There's a bug open since May 2021 which just disables this feature by providing incorrect config in ProxySQL. So this killer feature, which is still advertised in the docs, simply does not work at all. And there's no way to fix it manually.
-
Just found out that the #Percona MySQL #Operator, which deploys a Percona XtraDB/Galera Cluster on #Kubernetes quite nicely and sets up #ProxySQL to be able to split traffic between read and write queries, does not, actually, loadbalance over the nodes. There's a bug open since May 2021 which just disables this feature by providing incorrect config in ProxySQL. So this killer feature, which is still advertised in the docs, simply does not work at all. And there's no way to fix it manually.
-
Just found out that the #Percona MySQL #Operator, which deploys a Percona XtraDB/Galera Cluster on #Kubernetes quite nicely and sets up #ProxySQL to be able to split traffic between read and write queries, does not, actually, loadbalance over the nodes. There's a bug open since May 2021 which just disables this feature by providing incorrect config in ProxySQL. So this killer feature, which is still advertised in the docs, simply does not work at all. And there's no way to fix it manually.
-
Just found out that the #Percona MySQL #Operator, which deploys a Percona XtraDB/Galera Cluster on #Kubernetes quite nicely and sets up #ProxySQL to be able to split traffic between read and write queries, does not, actually, loadbalance over the nodes. There's a bug open since May 2021 which just disables this feature by providing incorrect config in ProxySQL. So this killer feature, which is still advertised in the docs, simply does not work at all. And there's no way to fix it manually.