Both resource quotas and a custom controller can help prevent resource contention. Resource quotas limit the resources each service can consume, preventing one service from monopolizing resources- A custom controller can monitor resource usage across all services and make coordinated scaling decisions to avoid over-provisioning and resource exhaustion.

The most common and recommended approaches for managing dependencies in AWS Lambda are to include them in the deployment package (C) and to use AWS Lambda Layers (E). Layers allow you to organize and share dependencies across multiple Lambda functions, promoting code reusability and reducing deployment size. Docker containers (A) are not directly supported for Lambda function deployments- CodeDeploy (B) is primarily for managing deployments, not dependencies themselves. Installing dependencies directly on the Lambda execution environment (D) is not possible and can lead to conflicts.

Pod Disruption Budgets (PDB) are a Kubernetes feature that helps maintain the availability of your application by limiting the number of pods that can be deleted at any given time. This ensures that at least a minimum number of healthy pods remain running, even during updates or maintenance.

The 'PodSpec' allows you to define resources for each container within the pod- You can specify 'requests' and 'limits' for CPU and memory resources, ensuring that each container receives the appropriate resources- ResourceQuota and LimitRange are used for enforcing resource usage limits across multiple pods, not within a single.

Flux is a GitOps operator that continuously monitors your Git repository for changes and applies those changes to your Kubernetes cluster. It is specifically designed for GitOps workflows, ensuring your cluster's state reflects the desired configuration in your Git repository.