kubernetes VS consul

Kubernetes and Helm for deployment

3 .Learn about containerization and orchestration tools such as kubernetes and docker

It is cross-platform and therefore able to be installed on any of Windows / Mac / Linux. This must be one of their advantages. Supposed that some files defining a virtual machine or a pod (of Kubernetes) for grouping ones are delievered, we can develop on the same virtual enviroment with defferent workstations.

Docker is a DevOps containerization service that separates your code from the infrastructure it depends on. Docker is often coupled with Kubernetes, which helps you rapidly deploy, scale and manage your containers. Together, they administer rapid software delivery and take care of its scaling.

Kubernetes is an Open Source container orchestration system. Kubernetes' API provides a uniform control layer for managing containerized services. There is a lot of great material available that explains what Kubernetes is. See Further Reading at the end for some suggestions.

If it's not something you can figure out from kubernetes.io, then its not something that you have to worry about being on the test.

Intermediate knowledge of Flux, Kustomize and K8s

There's been a highly annoying kubectl port-forward heisenbug open for several years which smells an awful lot like one of these dark Go network layer corners. You get a good connection establish and some data flows, but at some random point it decides to drop. It's not annoying enough for any wizards to fix.

https://github.com/kubernetes/kubernetes/issues/74551

Well, like I said, I'm building a harvester/k8s cluster. So, the idea being that if one of the machines is busy or goes down, an other part of the cluster can pick up the slack. Basically, the 'Voltron' of computing, many pcs come together to form a more 'powerful' system. I can do this with any pc, but minis are good for homelabbing because they're cheap, don't take that much space, aren't that power hungry, and they still are powerful enough to run 90% of anything I throw at it, that isn't graphic intensive.

Changed the service discovery to Consul, since this is the default in JHipster 8.

In another effort to standardize development and operations, Lob has just wrapped up our container orchestration migration from Convox to HashiCorp’s Nomad, led by Senior Platform Engineer Elijah Voigt. In this new ecosystem, one feature available to us is Consul Service Mesh (a feature of Consul, which is part of our Lob Nomad stack).

Service registry and discovery etcd, consul, nacos

The underlying tool Consul is very powerful, and Consul Connect service mesh on top of this tool is quite robust and extremely flexible where you can swap out the default CA for other solutions, like Vault CA, and swap out the Envoy proxy for another solution, like NGINX or HAProxy. For ingress into the cluster, you can use Consul API Gateway, or another API Gateway or an ingress controller.

I'd like to also mention hashicorp nomad + consul. They're worth evaluating.

Out of the number of service mesh solutions that exist, the most popular open source ones are: Linkerd, Istio, and Consul. Here at Koyeb, we are using Kuma.

Consul

A service mesh provides features to help with common distributed microservice challenges. Like service discovery, routing, load balancing, and so on. Today we will be using Istio, one of the most popular service mesh solutions available. Istio is tailored for distributed application architectures, especially those you might run in Kubernetes. Istio plays nicely with Kubernetes, so nicely that you might think that it's part of the Kubernetes platform itself. Istio isn't the only service mesh around; we also have platforms like Linkerd and Consul, which are also quite popular.

We knew that we needed a way, at runtime, to start and stop these queue consumers. Although we could have reached for other configuration management tools like Hashicorp Consul or AWS AppConfig, we already use LaunchDarkly at Knock to control the runtime behavior of our frontend and backend applications. LaunchDarkly feature flags seemed like a great way to control this starting and stopping process without adding new dependencies or complexity to our stack.

Since all of your apps are in the same environment, one possibility is to use a service registry like Consul or etcd. As a container comes up it registers itself by making a REST call to declare “I’m the Rabbit server!”. Then other apps call out to etcd with a REST query to ask “Where’s the Rabbit server?” and get the name of the Rabbit container. If you decide to start playing with HA or clustering, this can be extended so the service registry returns the name of the current primary node, or spreads traffic across multiple nodes by returning different responses based on rules you set up.