REQUEST: New membership for viktoriaas #5764
Description
GitHub Username
viktoriaas
Organization you are requesting membership in
kubernetes
Requirements
- I have reviewed the community membership guidelines
- I have enabled 2FA on my GitHub account
- I have subscribed to the kubernetes dev e-mail list
- I am actively contributing to 1 or more Kubernetes subprojects
- I have two sponsors that meet the sponsor requirements listed in the community membership guidelines
- I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application
- I have verified that my sponsors are from different member companies
- I have verified that my sponsors are a reviewer or an approver in at least one OWNERS file within one of the Kubernetes GitHub organizations (excluding the contributor-playground)
- SUGGESTED: Ensure your affiliation in gitdm is up to date (gitdm is used by devstats to track affiliation)
- SUGGESTED: Ensure your affiliation in openprofile.dev is up to date (used by LFX Insights to track affiliation, will replace gitdm in the future)
- SUGGESTED: I have taken the Inclusive Open Source Community Orientation course
Sponsor 1
Sponsor 2
List of contributions to the Kubernetes project
I would like to request membership in the K8s organization to be able to be involved with Checkponit/Restore WG.
I have been working with Radostin Stoyanov and Adrian Reber on improving checkpoint/restore functionality in K8s and presenting this work at conferences or in papers:
- Kubernetes Environment and Checkpoint Restore, LPC 2024
- Optimizing Resource Utilization for Interactive GPU Workloads with Transparent Container Checkpointing, FOSDEM 2025
- Efficient Transparent Checkpointing of AI/ML Workloads in Kubernetes, KubeCon 2025
- Kubernetes Scheduling with Checkpoint/Restore: Challenges and Open Problems, JSSPP 2025
Apart form this efforts, I have been working with K8s as an admin since 2020 and k8s v1.17. Currently I’m an IT architect at centre CERIT-SC, we are providing large public and sensitive Kubernetes clusters as part of national e-infrastructure in Czech Republic, docs, blog. Since I have been working with k8s every day, I have extensive knowledge about the Kubernetes itself, day-to-day operations, user support, architecting solutions, coding - webhooks, operators, CRDs, CSI drivers, helm charts, automation - and other aspects of functional Kubernetes infrastructure, its support and what is possible with it.
I have a couple of paper and talks that are all in Kubernetes environment, I focus on HPC in Kubernetes, resource management, scheduling:
- Using Kubernetes in Academic Environment: Problems and Approaches, JSSPP 2022
- A Kubernetes ‘Bridge’ Operator between Cloud and External Resources, ICCCBDA 2023
- Implementation Challenges: From HPC to Containers in the Academy, KubeCon 2022
- In the Container Era: A Coup in Reliable Computing Over Unreliable Infrastructure, my PhD thesis proposal
- Nextflow in Bioinformatics: Executors Performance Comparison Using Genomics Data, FGCS 2023
- Managed Kubernetes — Next Gen Academic Infrastructure, KubeCon 2023
- Efficient Transparent Checkpointing of AI/ML Workloads in Kubernetes, KubeCon 2025
- Kubernetes Scheduling with Checkpoint/Restore: Challenges & Open Problems, JSSPP 2025
Apart from technical work I have been continuously evangelising about K8s and cloud-native in the e-infra CZ. Majority of people are trained in traditional HPC and are not so keen on adopting newer technologies thus I have been leading workshops, had informal talks at universities or at casual Linux conferences (On the Edge of Tomorrow: Checkpoint/Restore in Containers, LinuxDays in Prague 2024 or Czech conference on Containers in Practice). I’ve been teaching at university lectures on K8s and supervising theses, e.g., Improving Checkpoint/Restore Functionality in Kubernetes related to Checkpoint/Restore in 2025. I am also attending WG-node-lifecycle meetings.
EDIT
I am requesting membership in order to co-lead Checkponit/Restore WG together with Radostin Stoyanov and Adrian Reber. Community membership is required to co-lead as per WG governance doc. Checkpoint/Restore functionality has become interesting for various people who have reached out so we decided to create documents necessary for forming WG and hope to serve as a central point for further discussions and sharing re checkpoint/restore.