Anastasiia Gubska
Lead Software Engineer
Actions
Anastasiia Gubska is the first Deaf CNCF Ambassador and Lead Software Engineer at Chase UK, focusing on cloud native ecosystems and software delivery best practices.
Anastasiia enjoys sharing practical insights on Argo and advocating for accessibility and inclusion in open source. She actively contributes to the CNCF Deaf and Hard of Hearing Working Group (DHHWG) and leads Deaf in Cloud Native, a global community that supports Deaf signing technologists through collaboration, knowledge sharing, and visibility.
Badges
Area of Expertise
Topics
Panel: From Signals to Safety Nets: Self-Healing Progressive Delivery with Argo Rollouts
What if your deployment pipeline could sense failure and heal itself before users notice?
In this session, we show how to build self-healing progressive delivery pipelines using Argo Rollouts powered by real-time observability signals. Integrating Prometheus, OpenTelemetry, and Linkerd, we transform rollouts from time-based experiments into signal-driven systems that auto-react to performance degradation.
See how:
- A canary detects rising latency and auto-rolls back early before wider exposure
- Error spikes trigger KEDA-based scaling and pause Rollouts until stable
- Service-mesh insights feed AnalysisTemplates for closed-loop remediation
While we use specific tools, the patterns are universal: any mesh, any metrics stack, any automation framework. You’ll take home templates, blueprints, and decision frameworks that make Argo Rollouts the control plane for resilience, ushering in the next phase of progressive delivery: Automated Resilience Engineering.
Decoupling canary deployments from DBs with Argo Rollouts
Argo Rollouts offers well-known strategies for stateless applications, but what about deploying stateful applications that use databases? How can teams ensure safe, consistent, and reversible database updates when rolling out new application versions? This talk answers by showing how to decouple database migrations from application deployments through backward compatible schema changes to the database that allow both old and new application versions to operate simultaneously during the rollouts. We’ll also explore practical strategies for common database refactoring scenarios, including adding new columns, renaming columns and tables, and introducing new data types gracefully.
Autoscaling and Progressive Delivery - a match made in heaven
Argo Rollouts is a Kubernetes controller for Progressive Delivery deployments. In the most basic scenario, Argo Rollouts supports advanced Kubernetes deployments such as blue/green and canaries. While this is great, the main selling point of a Kubernetes cluster is the autoscaling facilities it offers. Can you use canary deployments while still taking advantage of Horizontal (and Vertical) autoscalers?
The answer is yes! In this talk, we will see how you can combine these two worlds - progressive delivery and autoscaling - and explain how to perform advanced deployments even in the presence of autoscalers.
Stop deploying blind! Using Observability and Argo Rollouts to Light the Way
Are you tired of looking at metrics and logs after each deployment? Do you learn about failed deployments from unhappy customers? Did you always want to deploy on Friday afternoon and go straight to the pub?
Many teams perform “blind” deployments without any real insight into what will be affected by the new application version. Consequently, they don’t have enough data to understand the blast radius of a release and whether to decide if it was successful or not.
Even companies that have several metrics in place, don’t always use them in an automated manner. Wouldn’t it be great if you could see user behavior with new features in real time and identify performance bottlenecks before a full release?
In this talk, we will focus on common scenarios regarding Argo Rollouts and observability metrics, we will explain:
- Minimum requirements in terms of tools and metrics/traces/logs
- Well-known observability use cases
- Common automation pitfalls
- RED/USE metrics tradeoffs
Why Allyship Matters and Your Role in Creating a More Diverse Cloud Native Community
Despite many DEI initiatives, diversity in open source is still lacking. That's not only bad for underrepresented groups, it's also bad for OSS (studies have shown time and again that diverse teams produce better outcomes). While there isn't much you can do about the industry's hiring practices, you can help make a difference!
As companies scale back on DEI efforts, community-driven change becomes essential—and that’s where allies come in. Minorities are, by definition, in the minority, and their advocacy alone has limits. Allies have the power to amplify underrepresented voices, raise awareness among peers, and advocate for change. When allies take a stand for inclusivity, accessibility, and ethical responsibility, they hold the power to influence the industry's values and priorities.
Join this panel with CNCF Deaf and Hard of Hearing WG members to learn how you can drive meaningful change and contribute to a more diverse, inclusive, and innovative open-source community.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top