Kubernetes offers a powerful rollback feature for container versions, facilitating easy reversion by modifying the manifest file and applying changes. However, the automatic execution of rollbacks raises questions about feasibility and advisability.

Many containerized applications leverage relational databases for data storage, as transitioning from relational to NoSQL databases entails significant costs and time investments. Rollback attempts with relational databases pose inherent risks of data loss or corruption.

This session explores effective strategies for mitigating rollback risks in applications reliant on relational databases. We will explore a comprehensive database change strategy supporting multiple application versions. Furthermore, we will examine how Kubernetes empowers the adoption of advanced deployment patterns, enabling thorough testing of changes in Production environments before user accessibility.

Key Learning Points for Attendees:

- Streamline rollback processes by omitting database-specific steps in deployment procedures.
- Implement the expand/contract pattern to decouple database alterations from application updates.
- Embrace Blue/Green or "Staging" deployment methodologies to test changes in Production before end-user interaction rigorously.

By the end of this talk, attendees will gain valuable insights into fortifying their deployment pipelines and enhancing the resilience of relational database rollbacks within Kubernetes environments.

This session is designed for developers, operations, or DBAs who have at least 1 to 3 years of experience and are looking to adopt a rollback strategy.