Why Every Kubernetes Deployment Needs a Standardized Ops Playbook

Kubernetes has become the industry standard and a must‑have for operations. In interviews, companies that don’t list Kubernetes as a required skill are often not worth considering (unless they pay a lot).

Standardization

Although Kubernetes is a standard, its implementation lacks a unified approach, leading to countless variations and problems. Below are four areas of personal standards derived from real‑world practice.

Infrastructure Standards

With cloud capabilities improving, many internet companies no longer care about low‑level hardware details. When selecting infrastructure, focus on the following points (example uses Alibaba Cloud):

ECS type : Choose instances consistently to avoid obscure issues caused by mixed shared and dedicated instances.

OS version : Standardize the operating system (e.g., stick to CentOS if that’s familiar) to simplify maintenance and reduce risk.

Kernel version : Use a stable kernel across all servers, as Kubernetes and Docker have specific kernel requirements.

Security group configuration : Keep security groups uniform to ease management and hand‑over.

Network segmentation : Divide networks by business unit (e.g., A: 192.168.1.0/24, B: 192.168.2.0/24, C: 192.168.3.0/24) to enable multiple NAT gateways and better traffic isolation.

Application Standards

Operations often lack influence, so gaining authority requires proactive involvement throughout the application lifecycle and establishing clear standards.

Packaging method : Standardize the build tool (e.g., all Java services use Gradle) to simplify CI templates.

Application directory layout :

- deployment directory /app
- cache directory /app/cache
- log directory /app/logs
- temporary directory /app/tmp

Application logs : Define a uniform log format and output to the console for easy collection. 日志不规范，运维两行泪 Runtime parameters : Standardize ports (e.g., 8080) and JVM options. Example JVM configuration:

-server
-XX:+UseG1GC
-XX:MaxGCPauseMillis=50
-Xms1G -Xmx1G
-XX:MetaspaceSize=128m JAVA_MAXMETA_SIZE="512m"
-XX:LargePageSizeInBytes=128m
-XX:+ParallelRefProcEnabled
-XX:+PrintAdaptiveSizePolicy
-XX:+UseFastAccessorMethods
-XX:+TieredCompilation
-XX:+ExplicitGCInvokesConcurrent
-XX:AutoBoxCacheMax=20000
-XX:+UnlockExperimentalVMOptions
-XX:+UseCGroupMemoryLimitForHeap
-XX:+PerfDisableSharedMem
-verbosegc -XX:+PrintGCDateStamps -XX:+PrintGCDetails -Xloggc:/app/logs/gc.log
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/app/logs/oom-`date +%Y%m%d%H%M%S`.hprof

Artifact Standards

Use a unified base image to simplify upgrades and vulnerability fixes.

Keep image layers minimal.

Run containers as non‑root users and avoid privileged mode.

Do not install unnecessary command‑line tools.

CI/CD Standards

Companies adopt various CI/CD tools; open‑source solutions like GitLab CI, Jenkins, Argo Workflows, etc., are common in China.

Consider the tool’s historical usage, strengths, and weaknesses before switching.

Assess organizational structure and team readiness, as CI/CD impacts developers, testers, and ops.

Prefer tools familiar to the team to reduce reliance on external search.

When a tool is chosen, implementation matters. For example, using Jenkins:

Leverage Jenkins shared libraries to abstract repetitive code.

Unify Jenkinsfile syntax across front‑end and back‑end projects.

Standardize variable names for fixed and variable parameters.

Manage multi‑environment releases with proper classification and permission control.

Prefer a single deployment method (Helm chart or plain Deployment) to avoid mixed approaches.

标准很重要，标准却没有标准。

Continuous Accumulation

Technology evolves rapidly; regular knowledge accumulation and organized archiving (e.g., using Yuque) enable quick retrieval when needed.

Frequent Sharing

Sharing knowledge outward—through community posts or internal talks—requires clear, beginner‑friendly explanations and avoidance of excessive jargon.

Continuous Learning

Learning is lifelong; reading books across technical, parenting, and personal growth topics sustains growth regardless of age or position.

Conclusion

Adopt standards first, then expand around them, while maintaining a growth mindset through learning, accumulation, and sharing. Turning these habits into natural behavior drives continuous personal and professional advancement.