IfNotPresent Can Hide Image Changes During Testing
How pull policy interacts with mutable image tags and node caches.
kubernetes
Why I Later Exposed Voiceware on NodePort 30080
The practical reason for adding a simple external access path while validating the web deployment.
Why the First Voiceware Web Service Used ClusterIP
Why internal reachability was the safer default during the first deployment slice.
When I Would Replace NodePort With Ingress or a Load Balancer
The conditions that justify moving from direct node exposure to a richer edge abstraction.
The Production Hardening Pass I Would Apply to Voiceware
A prioritized list of reliability controls to layer onto the validated deployment foundation.
Why docker.io/library/voiceware-web-app Is More Explicit Than voiceware-web-app
How a fully qualified-ish image path reduces ambiguity for the runtime.
Why I Would Still Start a Voiceware Migration With One Workload Today
The repeatable migration strategy that survived the real project.
Internal Services vs External Services in Voiceware
How I separate east-west service communication from user-facing exposure.
Service Port Mismatches: The Quiet Networking Failure
Why I verify listener, container port, Service port, and targetPort as one chain.
Why I Kept Audio, Workers, Redis, Nginx, and the Web App Separate
The operational reasons for not collapsing supporting services into one large deployment.
Local Images and Cluster Images Are Different Problems
Why “it exists on my machine” is irrelevant unless the node runtime can resolve the same artifact.
My Voiceware-to-Kubernetes Migration Checklist
A practical sequence for moving a service without losing track of runtime assumptions.
The Trade-Off of Deploying Voiceware Into the default Namespace
What the current ArgoCD destination implies and what I would revisit as environments grow.
Celery Beat Is Not “Just Another Worker”
Why scheduled task orchestration deserves different lifecycle thinking from queue consumers.
A Single Redis Replica Is a Design Choice, Not a Default Truth
How I interpret the current one-replica values and what changes when availability requirements grow.
The audio-fork Service Deserved Its Own Deployment Boundary
Why audio-related processing should not be forced into the lifecycle of the web process.
Why Chart.Name Was a Useful Naming Primitive
Using the Helm chart identity to keep Deployment, labels, and Services aligned.
Voiceware Started With One Deployable Service, Not a “Platform”
Why I validated the delivery path with the web application before expanding to the rest of the stack.
The Real Architecture Work Was Finding Voiceware’s Runtime Boundaries
How I treated process boundaries as deployment boundaries instead of forcing the application into one monolithic unit.
What the Early Voiceware Manifests Do Not Yet Prove
Being precise about the difference between a working deployment model and production hardening.
Redis in Voiceware: Small Manifest, Central Dependency
Why an internal Redis service deserves explicit operational attention.
What an ArgoCD Application Actually Did for Voiceware
Breaking down repository source, chart path, destination cluster, namespace, and sync policy.
Kubernetes Gateway API Is Not Just a New Ingress YAML
Gateway API changes who owns the network boundary, how routes attach, and what a migration has to prove. Treating it as an Ingress syntax upgrade misses the important part.
The ESL Service as an Explicit Integration Boundary
Why I prefer to see integration adapters represented directly in the deployment graph.
Why Voiceware Needed More Than Docker Compose Thinking
The conceptual shift from “start these containers” to declaring desired state and independent service lifecycles.
Container Ports Are Documentation and a Runtime Contract
How service ports made Voiceware component boundaries visible.
My Layered Debugging Model for Voiceware on Kubernetes
A repeatable order for diagnosing delivery, scheduling, networking, dependencies, and application behavior.
What replicaCount Really Means in a Voiceware Helm Chart
Why a single integer represents an operational scaling decision rather than a cosmetic value.
A Kubernetes Service Can Be Healthy While the App Is Broken
A layered method for checking pods, endpoints, ports, and application behavior separately.
Labels and Selectors: The Tiny Contract That Can Break an Entire Service
Why the app label shared by a Deployment and Service matters more than it looks.
Why I Put Voiceware Runtime Knobs in values.yaml
Separating reusable Kubernetes structure from service-specific image, replica, and port settings.
Helm Render Errors Are Not Kubernetes Errors
Why nil-pointer failures should be solved before looking at pods or cluster networking.
Deployment vs Service: The Two Kubernetes Objects Voiceware Needed First
The separation between process lifecycle and network reachability.
Why Nginx Was Its Own Voiceware Application
The operational value of separating edge/proxy concerns from the application container.