1. Business Background Once an enterprise reaches a certain scale, relying entirely on public cloud infrastructure makes IT costs very high. The cost of purchasing physical machines can be amortized over the next 3 to 5 years, and afterwards the machines are not scrapped; instead they continue to serve beyond their planned lifespan.

1. HPA VS KEDA HPA also provides: Elasticity based on custom metrics Scale to Zero Compared with KEDA, these are no longer disadvantages. The real difference is that HPA can only scale using monitoring data, whereas KEDA can scale using many more data sources — queue messages, databases, Redis, and so on, including monitoring data as well.

1. A Constrained Build Environment Cannot Meet Build Requirements Tekton is a CICD engine based on a Kubernetes cluster, and it is more cloud-native than Jenkins. In plain terms, that means it is easier to develop plugins for, easier to scale, easier to observe, and more fun. Because code can only be stored on the company intranet, the build cluster can only be deployed on the office intranet.

1. After Turning Off affinity-assistant In an earlier post, by turning off affinity-assistant and using NFS storage, I saved nearly 30 seconds on average per pipeline execution.[1] The impact of affinity-assistant Before turning it off, the sequence diagram for creating a Pod looked like this: Because affinity-assistant was on, every pipeline was bound to a single node for execution.

1. What Documentation as Tooling Means “Documentation as tooling, tooling as a product” is a slogan I have repeated many times in my previous blog posts. A good document is no match for a tool that is pleasant to use. A script or a single command is more direct than reading documentation and can solve the problem faster.