We use Kubernetes for workload standardization, portability across environments.
We use Kubernetes for workload standardization, portability across environments, and to meet strict air-gapped requirements that cloud-native PaaS solutions can’t satisfy.
EXPOSE and containerPort fields serve documentation and integration purposes but do not enforce network policies.
EXPOSE and containerPort fields serve documentation and integration purposes but do not enforce network policies; actual port exposure depends on container runtime and service configurations.
Developers must meet basic Kubernetes readiness criteria before deploying to production clusters.
Developers must meet basic Kubernetes readiness criteria before deploying to production clusters.
Use environment variables and Kubernetes Secrets to inject sensitive data into your application.
Use environment variables and Kubernetes Secrets to inject sensitive data into your application, keeping ConfigMaps safe for version control.
Reducing CPU limits can lead to Go thread explosions; here's how to diagnose, mitigate, and prevent them in production.
Reducing CPU limits can lead to Go thread explosions; here’s how to diagnose, mitigate, and prevent them in production.
Preventative maintenance, routine care, and repairs for Kubernetes & OpenShift clusters
I’m a Red Hatter working as a Solutions Architect, formerly a Senior Cloud Success Architect, with a focus on and passion for OpenShift and Ansible. Previous life? Cloud Advanced Technology Lead & Big Data Engineer for Lockheed Martin Space, IT/IS Data Center Manager for Lockheed Martin IS&GS, and Senior Infrastructure Designer/Administrator for the City of Gainesville & City of Alachua.
Learn More
Share this post
Twitter
Google+
Facebook
Reddit
LinkedIn
StumbleUpon
Pinterest
Email