Overview
Gardenlinux Software Engineer – On behalf of our general client
Start : ASAP
Location : Remote
Scope of Work
- Configuration, deployment, and maintenance
- Troubleshooting OS-level, kernel, and package-related issues
- Debugging of custom image builds and runtime behavior
- Recommendations for performance tuning and hardening
B. KVM Virtualization Stack (Cloud Hypervisor, QEMU, and Libvirt)
- Configuration and integration of KVM-based virtualization environments
- Analysis and resolution of hypervisor or VM-level issues
- Performance optimization for compute, networking, and storage layers
- Debugging and tuning Cloud Hypervisor and Libvirt configurations
- Troubleshooting Gardener control plane and shoot cluster incidents
- Root cause analysis for provisioning, scaling, and upgrade failures
- Configuration review and optimization
- Integration support between Gardener, Gardenlinux, and KVM-based nodes
Skills Requirements for Engineers
Engineers assigned to Gardenlinux-related support must possess:
- In-depth knowledge of Debian-based Linux systems and kernel configuration
- Experience with Gardenlinux image customization and build pipelines
- Strong skills in package management, systemd, and OS hardening
- Proficiency in debugging performance, boot, and kernel-level issues
- Familiarity with CI/CD integration for OS image deployment and maintenance
B. KVM / Virtualization Expertise
Engineers providing KVM and virtualization support must have:
- Advanced understanding of KVM, QEMU, and Libvirt architecture
- Experience configuring and troubleshooting Cloud Hypervisor environments
- Deep understanding of virtualization networking (bridges, VLANs, SDN) and storage (NFS)
- Knowledge of hardware virtualization and NUMA alignment
- Scripting skills for automation (Golang, Python, Bash)
- Experience with host performance tuning and low-level debugging
- Hands-on experience with Gardener architecture, shoot and seed cluster management
- Familiarity with cluster lifecycle management, upgrades, and node troubleshooting
- Strong knowledge of observability tools (Prometheus, Perses)
- Ability to conduct root cause analysis and contribute to post-mortem reviews
- Incident Troubleshooting Reports: Detailed technical documentation per incident
- Root Cause Analysis (RCA) Reports: Formal RCA for P1/P2 incidents
- Configuration Reviews and Recommendations
- Best Practices Documentation
- Knowledge Transfer Sessions
#J-18808-Ljbffr