Development teams wanting to adopt Kubernetes and containers Operations teams that run cloud native infrastructure Companies migrating to the cloud Teams wanting to implement DevOps and CI/CD We adapt the Journey to the team’s starting level and specific objectives.

Cloud Native Journey for your team

Four phasesTraining on the jobCKA, CKAD, CKS trainers

Bring your team to containers, Kubernetes, Terraform and CI/CD, working on your code with our engineers. The journey has four phases, and each one ends with a deliverable your team keeps.

The phases Tell us about your project

Cloud native is learned by doing it, on your code.

The Cloud Native Journey is a cloud native adoption program: containers, Kubernetes, Infrastructure as Code and CI/CD become part of your team’s work, with our engineers alongside. SparkFabrik is an AI Native Engineering company that has led the Cloud Native Journey of clients such as Deltatre and Unguess.

Whether you are modernizing a legacy system, running new infrastructure or building a pipeline on GitLab, you need the right decisions to reduce costs and unknowns.

A course teaches the concepts. But if the everyday work stays the same, the team goes back to its old habits.

You need an experienced guide who does the work together with your team and leaves the team with all the knowledge.

A trained team and the right infrastructure.

At the end the job is done just right, and your own team did it.

Training on the job
Theory and practice on your code, through to a complete cloud native transition.
Working code
Containers, infrastructure and pipelines working on your stack, from which the team carries on by itself.
A well-defined process
Clear phases and written deliverables, to work with DevOps and cloud native architectures.

Four phases in sequence and two optional modules.

Every phase closes with something that stays with your team.

01Assessment & Kick-offWe know where the team starts and where the architecture has to get to.
02Docker Deep DiveThe application runs in containers, on every developer’s machine too.
03Cloud Native InfrastructureInfrastructure becomes code, and the team runs Kubernetes on its own.
04CI/CDEvery change reaches production through the same pipeline.

The optional modules “Cost Analysis” and “Security and DevSecOps” are added when needed.

The phases in detail

The phases in detail.

For each phase you find what we do and what stays with your team.

Phase 1

Assessment & Kick-off

We know where the team starts and where the architecture has to get to.

We collect the materials, interview the team and analyze the application and infrastructure stack: maturity, current situation and goals.

What we do

Collection of resources
Team interviews
Analysis of the application and infrastructure stack

What stays with the team

Executive summary on the target architecture
Recommendations for improving documentation and processes
Activity planning

Phase 2

Docker Deep Dive

The application runs in containers, on every developer’s machine too.

From the container architecture to writing a Dockerfile, all the way to multi-container applications with Docker Compose.

What we do

Containerization
Docker images, networking & compose

What stays with the team

Dockerfile and Docker Compose of the stack
Local development environment on Docker
2 days of deep training

Phase 3

Cloud Native Infrastructure

Infrastructure becomes code, and the team runs Kubernetes on its own.

Infrastructure as Code with Terraform and a managed Kubernetes cluster on the chosen cloud provider, from the theoretical foundations to the implementation.

What we do

IaC on Terraform
Managed Kubernetes cluster on public cloud provider

What stays with the team

Cloud infrastructure in Terraform, in CI/CD
Kubernetes cluster for development and deployment
2 days of deep training

Phase 4

CI/CD

Every change reaches production through the same pipeline.

A pipeline on the chosen tool manages the entire application lifecycle: automated QA, artifacts and, when needed, automated deployment.

What we do

CI/CD deployment
Automated CI/CD pipelines
GitOps workflow

What stays with the team

Multi-environment CI/CD pipeline for QA and delivery
2 days of deep training

Optional module

Cost Analysis

Choose the cloud provider knowing how much it will cost.

Based on existing data, we estimate the cost of the infrastructure on two cloud vendors chosen with you.

What we do

Cloud infrastructure analysis
Application stack and consumption
Cost comparison on 2 cloud vendors

What stays with the team

Infrastructure cost report on 2 vendors
Projected cost per instance, in case of PaaS architecture

Optional module

Security and DevSecOps

Security enters the pipeline, from the first container.

Security threats and best practices in cloud native: from containers to infrastructure, all the way to the services running in the cloud.

What we do

Cloud Native security fundamentals
Docker container security
Automated Docker image scanning
Kubernetes security best practice

What stays with the team

Securely written Dockerfiles
Vulnerability scanning on images and code
Cloud native security standards
RBAC, security context, network policy, OPA

Your team, autonomous at the end.

We transfer knowledge, tools and methods and keep supporting you afterwards, so that your team becomes autonomous and does not depend on us.

Weekly meetings
Every week with the team: progress, questions, next step.
Working implementations
The value lies in what is delivered, not in the slides.
Dedicated contact person
Theory, operations and support have a first and a last name.

The process matters as much as the result.

It starts from phase 1.

Tell us about your project

The proof

The journey in practice.

The case shows where we started, what we did and what changed.

Frequently asked questions.

About the Cloud Native Journey.

What is the Cloud Native Journey?

An on-the-job training and mentoring program that transfers cloud native skills to your team. We work together with the team on its own code and projects.

Who is it for?

Development teams wanting to adopt Kubernetes and containers
Operations teams that run cloud native infrastructure
Companies migrating to the cloud
Teams wanting to implement DevOps and CI/CD

We adapt the Journey to the team’s starting level and specific objectives.

How long does it take?

It depends on the team and on the code it starts from. The four mandatory phases are planned at the end of phase 1, Assessment & Kick-off. The optional Cost Analysis and Security and DevSecOps modules are added when needed.

Is SparkFabrik certified for Kubernetes training?

Yes. SparkFabrik is a CNCF Kubernetes Training Partner (KTP) and a Kubernetes Certified Service Provider, and the trainers are CKA, CKAD and CKS certified.

Who provides Cloud Native training in Europe?

SparkFabrik is a CNCF Kubernetes Training Partner (KTP). It offers the official Kubernetes courses (CKA, CKAD, CKS) and cloud native training paths for Italian and European enterprise companies, such as the Cloud Native Journey, which combines theory with work on your team’s own code.

What skills are transferred?

Kubernetes: deployment, networking, storage, security
Docker and containerization
CI/CD with GitLab and GitHub Actions
Infrastructure as Code with Terraform and Helm
Observability: monitoring, logging, tracing
Best practices: GitOps, 12-factor app, microservices

Does the Cloud Native Journey include security?

Yes, with the optional Security and DevSecOps module: cloud native security fundamentals, Docker container security, automated scanning of images and code, Kubernetes security with RBAC, security context, network policy and OPA. It is the module to add when the company has strict compliance requirements.

What stays with the team at the end?

Working code, documentation and an autonomous team: Dockerfile and Compose of the stack, local environment on Docker, infrastructure in Terraform, Kubernetes cluster and multi-environment CI/CD pipeline.