https://rook.io/

The most secure and recommended approach is to use a service account with appropriate permissions to connect to Cloud SQL from Cloud Functions. This method provides granular control over access and ensures that Cloud Functions only have the necessary permissions to interact with the database. Option A is not a standard feature. Option B is an alternative but adds complexity. Option C introduces extra infrastructure and potential security risks. Option D, while important for overall security, doesnt specifically address database connections.

kube-proxy is a critical component in Kubernetes' networking model. Its primary role is to act as a network load balancer for Kubernetes services. It listens on the node's IP address and forwards traffic to the corresponding pods based on service rules. This allows for load balancing, service discovery and efficient communication between pods and external clients. Options A, C, D, and E are incorrect. While kube-proxy contributes to external connectivity its core responsibility is internal load balancing. Communication within a namespace relies on the pod network, not kube-proxy. DNS resolution is handled by CoreDNS in Kubernetes, not kube-proxy. Security features like NetworkPolicies are implemented separately.

The "resources" section in the Deployment manifest defines the minimum (requests) and maximum (limits) resource requirements for the container This helps Kubernetes schedule pods effectively and prevents resource starvation or excessive resource consumption by individual pods.

https://prometheus.io/