K8s Anti-Design Pattern Series

Introduction

Anti-Patterns helps you identify the problems and point out bad-practices in the implementation. we make sure to constantly link each anti-pattern with the appropriate solution. You will be able to truly check your own deployment procedure and correct any problems without having to hunt down additional information using this method.

To prevent these issues, a fundamental understanding of Kubernetes’ architecture and operation is required. In this blog-series, we’ll take a look at some of the more typical blunders made during Kubernetes installations, explain how they occur, and offer some advice for how to correct them or avoid them in the first place.

1. Putting the configuration into the images of the containers
2. Unnecessarily linking applications to Kubernetes features/services
3. Mixing infrastructure and application deployment
4. Deploying without memory and CPU limits
5. Using health probes wrongly
6. The absence of Helm (and not understanding what Helm brings to the table)
7. Being unable to comprehend the application’s performance due to a lack of deployment metrics
8. being unprepared for secret situations; handling secrets on an as-needed basis
9. Looking to commit fully to Kubernetes (even with databases and stateful loads)
10. Manual kubectl edit/patch deployments
11. Kubernetes deployments with latest-tagged containers
12. Kubectl debugging
13. Misunderstanding Kubernetes network concepts
14. Utilizing fixed staging environments rather than dynamic environments.
15. Combining clusters of production and non-production