anti-design-patterns
Summary Since we’re already discussing kubectl’s shortcomings, let’s talk about its second largest one. You shouldn’t try to use Kubectl as if it were a debugging utility. Inevitably, the “10-questions-game” with kubectl will arise for any business that has begun implementing Kubernetes. The first thing you should not do if there is a serious issue […]
Summary This should not be shocking to anyone who has worked with containers. Since “latest” is simply the word of the tag and not an indication of when the image was created, labeling Docker images with the “latest” tag is a poor practice in and of itself. If a tag is not specified when referring […]
Summary The days when a singular load balancer could handle all of your application’s needs are long gone. It is your responsibility to study and understand the fundamental concepts of Kubernetes’ new networking model. Learn the basics of load balancers, clusterIPs, nodeports, and entry at the very least (and how they differ). We’ve seen companies […]
Introduction: For the time being, Helm is the only option for managing Kubernetes packages. Helm can be compared to the popular package management tools apt and rpm. The powers of Helm are often overstated, leading people to reject it in favour of a less effective “alternative.” If you’re looking for a package manager with templating […]
Summary: Even though Kubernetes was built from the ground up to orchestrate clusters, you shouldn’t make the mistake of using a monolithic cluster for everything. Two clusters are required at the very least: one for actual production and one for testing and development. If you’re short on supplies, a bad idea would be to switch […]
Summary A software team usually has numerous predefined test environments for virtual machines and bare metal servers to test an application before it goes into production. At least three environments (QA/staging/production) are usual, but larger companies may have more. The “integration environment” setting collects all developer features after they are merged to the mainline branch. […]
Summary The issue of configuration dispersion predates Kubernetes and has been around for a long time. It occurs when two or more identical environments no longer share the same setup due to ad hoc deployments or adjustments.This issue becomes more pressing over time, to the point where it may become necessary to reverse-engineer a running […]
Summary Kubernetes, like every other technological advancement before it, is a specialised tool for handling a particular issue. Adopting Kubernetes, which is a well-designed and maintained clustering solution, can significantly simplify your workflow if you’re already dealing with these issues. However, before implementing Kubernetes, it’s crucial to weigh the advantages and disadvantages. Kubernetes is best […]
Introduction If you’re already using a dynamic service for managing configuration changes, it makes sense to use the same (or a comparable) service for managing secrets as well. Containers should have their secrets communicated to them in real time. Simple storing, git (encrypted), and comprehensive secret solutions like Hashicorp vault are just a few examples. […]
Introduction Metrics have been brought up several times in the preceding bad practises. When we say “stats,” we’re really talking about these three things: logs – records that can be analyzed to learn more about what happened and what was requested (usually post-incident) Tracing means to investigate thoroughly the path taken by a single request […]