True. This can also be written as 100m.
True. This may be done for security reason, such as this example: https://kubernetes.io/docs/concepts/configuration/secret/#use-case-secret-visible-to-one-container-in-a-pod
-Cluster IP
(Expose the service on a cluster-internal IP, not exposed to anything external to Kubernetes cluster)
-NodePort
(Expose the service on each Node’s IP at a static port. External callers can call the service)
-LoadBalancer
(Provision an external IP to act as a load balancer for the service. Exposes a service to external callers)
-ExternalName
(Maps a service to a DNS name. The service doesn’t change IP addresses, but it routes traffic to an external service that does have a dynamic IP)
kubectl describe pod my-nginx
Deployments support
zero-downtime updates by creating and destroying replica
provide rollback functionality
awsElasticBlockStore
kubectl scale deployment my-deployement –replicas=3
persistentVolumeReclaimPolicy: Retain
Queries for a template with the specified label in order to use that pod template
kubectl create configmap [configmap-name] –from-env-file=[path-to-file]
A LimitRange specifies min and max limits on cpu and memory for pods in a namespace. This prevents pods from not being given a limit and consuming too much memory, thus causing other pods to fail on a node.
-ReadWriteOnce
It spins up new pods and routes traffic to them, then subsequently destroys the old pods that no longer have traffic
kubectl port-forward service/[service-name] 8080
Blue-Green and Canary deployments, among others
Liveness and readiness
It gives details of the resource’s configurations.
This allows changes to be made to a Pod using kubectl apply
A StatefulSet manages the following of a set of pods
1) deployment and
2) scaling
It remains in the PENDING state.
It is dependent on the host. If the host dies, the data is inaccessible and potentially lost.
kubectl get all
tmpfs
It will remove and recreate if there is an active deployment
True