We offer private, instructor-led training for developers who deploy through Azure App Service and need to operate suitable applications on Kubernetes.
Your team knows application settings, managed hosting, and its release workflow. Kubernetes makes workload health and platform integration explicit, including image delivery, traffic routes, and Azure service access.
LearnKube connects these changes through a sample web application and an Azure dependency. Your engineers will practice controlled releases and trace failures across the application and platform.
Hands-on learning and the skills engineers take back to work.
Preview: course-wide figures are not yet available.
App Service can provide deployment slots that keep application versions live and switch their routing. A Kubernetes Deployment update replaces Pods according to a rollout strategy. It does not create a separate staging endpoint or duplicate the surrounding Azure configuration. The team must make release validation, readiness, and dependency access explicit on the destination.
I separate a successful container start from a release that is ready for users. Slot warm-up and a Pod readiness probe need deliberate comparison, because the destination must verify the behavior the application actually requires.
— Daniele Polencic, LearnKube founder and Kubernetes instructor
| Current task or requirement | New concept or decision | Practice |
|---|---|---|
| Publish the application | Images and Deployments | Deploy a versioned image |
| Validate a new release | Probes and rollout strategy | Introduce an unready version |
| Supply application settings | ConfigMaps and Secrets | Diagnose missing configuration |
| Reach an Azure service | Destination identity integration | Inspect dependency access |
We propose a workshop around one application and its release process. If your team uses deployment slots, their validation and routing behavior provides a concrete comparison for the destination design.
The exercises follow a request through the application, its public route, and an Azure dependency. Identity and network examples use the selected destination's integrations rather than assume that every Kubernetes platform supplies the same Azure features.
This proposed agenda makes the responsibilities behind a managed application deployment visible. It connects container fundamentals to release control and service access.
Day 1
We explain image packaging and connect runtime requirements to Pods, Deployments, and Services. You will compare startup and readiness probes with the checks used before an App Service release.
Hands-on exercises
Day 2
You will use Helm and compare Kustomize to separate common resources from environment values. We explain the control plane, nodes, and controllers through the replacement of an application instance.
Hands-on exercises
Day 3
We connect custom domains and TLS expectations to ingress controllers, Services, and DNS. You will examine network policies, service mesh use cases, placement, and connections to services outside the cluster.
Hands-on exercises
Day 4
You will examine secrets, persistent storage, and the destination's Azure identity integration. We cover HPA metrics, authentication, and RBAC to distinguish workload credentials from developer permissions.
Hands-on exercises
Your App Service release workflow, Azure dependencies, and platform responsibilities can shape the agenda. Get in touch to tailor the workshop to your App-Service-to-Kubernetes transition.
When an engineer sees a running container and expects the release to be usable, the instructor can introduce a missing configuration value. Your team can inspect why startup, readiness, routing, and dependency access need separate evidence.
Asked what he liked most about the course, Kieran singled out one kind of lab:
The labs, especially the capture the flag ones.
— Kieran, Platform Engineer at Youi.
Tell us how you deploy through App Service, which Azure services the application needs, and who will manage the destination. We will recommend exercises for those changes.