Pregunta de Container Orchestration #019e3a4f

Kubernetes provides automated rollouts and rollbacks as a core feature for managing containerized applications. This allows you to declaratively update your application to a new version (rollout) and automatically revert to a previous version if the update fails (rollback).

How it Works:
Kubernetes uses controllers like Deployments to manage the desired state of your application. When you update the Pod template in a Deployment (e.g., changing the container image), Kubernetes gradually replaces old Pods with new ones according to a rolling update strategy. If the new Pods become unhealthy (e.g., crash loop), Kubernetes automatically rolls back to the previous revision. This is configured via the spec.revisionHistoryLimit and spec.rollbackTo fields (though rollback is often triggered manually via kubectl rollout undo).

Why the correct value is right:
Automated rollouts and rollbacks are a fundamental feature of Kubernetes, enabling zero-downtime deployments and self-healing. The kubectl rollout command manages this process, and the Deployment controller ensures the cluster converges to the desired state.

Why the incorrect values are wrong:

• A portable operating system: Kubernetes does not provide an OS; it runs on top of an OS (like Linux) and orchestrates containers that share the host kernel.
• File system redundancy: Kubernetes does not inherently provide file system redundancy. That is typically handled by storage solutions (e.g., cloud volumes, NFS, or distributed file systems) integrated via PersistentVolumes.
• A container image registry: Kubernetes does not include a built-in image registry. It relies on external registries (e.g., Docker Hub, Google Container Registry, or private registries) to store and retrieve container images.