AWS Cloud Developer: Kubernetes for production

Question 1

Kubernetes configuration for reducing cost

Answer 1

reduce number of replicas

reduce and tune resources

Question 2

Kubernetes configuration for security

Answer 2

Configure who has access to the Kubernetes pods and services.

Secure traffic for least-privilege

Question 3

What are some additional considerations for production ready applications

Answer 3

Restrict Access
Follow properties of least-privilege to secure our application.

Scale
Be able to handle the number and size of user requests.

Availability
Ensure that the application is responsive and able to be used when needed.

Question 4

Load Testing

Answer 4

Load testing is a common way to simulate a large number of requests to our application. By doing so, we are essentially stress-testing it to preview when it will fail. This helps us set a baseline understanding of the limits of our application.

Question 5

Reverse Proxy

Answer 5

A single interface that forwards requests on behalf of the client and appears to the client as the origin of the responses.

Useful for abstracting multiple microservices to appear as a single resource.

Question 6

API Gateway

Answer 6

A form of a reverse proxy that serves as an abstraction of the interface to other services.

Question 7

Ingress

Answer 7

Inbound web traffic

Question 8

Egress

Answer 8

Outbound web traffic

Question 9

Self-healing

Answer 9

Kubernetes deployments can be set up to recover from failure.

Health checks - an HTTP endpoint that must return a 200 response for a healthy status. Kubernetes will periodically ping this endpoint.
Replicas - Kubernetes will attempt to maintain the number of desired replicas. If a pod is terminated, it will automatically recreate the pod.

Question 10

Horizontal Pod Autoscaler

Answer 10

Horizontal Pod Autoscaler

A deployment feature that allows additional pods to be created when a CPU usage threshold is reached.

Question 11

CMD: Create HPA

Answer 11

kubectl autoscale deployment –cpu-percent= –min=
–max=

Question 12

CMD: View HPA

Answer 12

kubectl get hpa

Question 13

Liveness Probe

Answer 13

A monitoring activity that occurs at scheduled intervals to ping a health check API endpoint to validate that the application is in a healthy state.

Question 14

Resilience

Answer 14

The property of an application to handle and recover from failures.

Question 15

Why do we choose to use horizontal scaling over vertical scaling with our microservices?

Answer 15

Horizontal scaling is more cost-effective?

Question 16

Logging strategies

Answer 16

Use timestamps to know when the activity occurred

Set a consistent style of logging to make it easier to parse log output

Use process IDs to trace an activity

Rotate logs so they don’t fill up your storage

Include stack traces in your logs

Look at the delta in message timestamps to measure execution time