From Kubernetes documentation:
The selector field defines how the Deployment finds which Pods to manage.
But, when creating deployment, I already specify the pod template as part of the deployment. So, why will I need the selectors as well?
Is it supposed to be used like services, where pods are already being started separately, but later brought under the umbrella of Deployment to be managed together?
Since Kubernetes 1.8, it seems I need to disable swap on my nodes (or set --fail-swap-on to false).
I cannot find the technical reason why Kubernetes insists on the swap being disabled. Is this for performance reasons? Security reasons? Why is the reason for this not documented?
Currently I'm working on a small hobby project which I'll make open source once it's ready. This service is running on Google Container Engine. I chose GCE to avoid configuration hassle, the costs are affordable and to learn new stuff.
My pods are running fine and I created a service with type LoadBalancer to expose the service on port 80 and 443. This works perfectly.
However, I discovered that for each LoadBalancer service, a new Google Compute Engine load balancer is created. This load balancer pretty expensive and really over done for a hobby project on a single instance.
To cut the costs I'm looking for a way to expose the ports without the load balancer.
What i've tried so far:
Deploy a NodePort service. Unfortunately it's disallowed to expose a
port below 30000.
Deploy an Ingress but this also creates a load balancer.
Tried to disable HttpLoadBalancing (https://cloud.google.com/container-engine/reference/rest/v1/projects.zones.clusters#HttpLoadBalancing) but it still creates a load balancer.
Is there a way to expose port 80 and 443 for a single instance on Google Container Engine without a load balancer?
A pod in my Kubernetes cluster is stuck on "ContainerCreating" after running a create. How do I see logs for this operation in order to diagnose why it is stuck? kubectl logs doesn't seem to work since the container needs to be in a non-pending state.
I have a single node kubernetes cluster in google container engine to play around with.
Twice now, a small personal website I host in it has gone offline for a couple minutes. When I view the logs of the container, I see the normal startup sequence recently completed, so I assume a container died (or was killed?) and restarted.
How can I figure out the how & why of this happening?
Is there a way to get an alert whenever a container starts/stops unexpectedly?