Skip to content

Author

Peter Jausovec

Peter Jausovec is a software architect at Solo.io with over 18 years of experience in software development, QA, and engineering leadership. A recognized expert in cloud-native technologies, he specializes in Kubernetes, Istio, and AI infrastructure. Peter maintains the kagent project and has been at the forefront of AI gateway and agent development at Solo. His recent work bridges traditional cloud-native architectures with emerging AI workloads, helping organizations navigate the intersection of service mesh, API management, and artificial intelligence.

Articles

67 articles by Peter Jausovec

Local development with coding agents on Kubernetes using Signadot
AI

Local development with coding agents on Kubernetes using Signadot

Coding agents are quite good at writing code now. Any of the agents can easily add a function, wire up an endpoint, or open a pull request for you. But there's a gap that you run into in practice. They write code that looks perfectly correct in a single-service context, and then it breaks as soon as it touches real dependencies; either another microservice, a database, a message queue. The agent has no way to know, and honestly, neither do you, until something fails downstream.

cuenv: one typed file for your whole project
Tooling

cuenv: one typed file for your whole project

Most projects don't have a configuration system — they have a pile: a .env file, a Makefile, a CI workflow, and secrets in a fourth place, none of it validated and all of it slowly drifting apart. cuenv replaces that pile with a single typed env.cue written in CUE. In this overview I'll show you how it validates your config before anything runs, resolves secrets at runtime, runs your tasks as a cached DAG, and generates your CI from the same definitions.

Rapid microservices development with Signadot
Service mesh

Rapid microservices development with Signadot

While developing microservices locally is possible, running and testing them in a production-like Kubernetes environment is complex. A typical development workflow while developing service in Kubernetes can significantly slow you down - from building a Docker image, pushing it, restarting the deployments, and testing the changes in a shared cluster. In this article, I'll look at a tool called Signadot. Signadot introduces a concept of sandboxes that allow you to considerably shorten your developer workflow and go from minutes to mere seconds!

Beginners guide to Docker
Docker

Beginners guide to Docker

Understanding concepts around Docker images and containers is crucial for anyone starting in cloud-native. Regardless if you're in development, DevOps or program management (or any other technical role :). Once you grasp the basics of Docker it will be so much easier for you to understand things like Kubernetes, service meshes and pretty much any other cloud-native tool works. You can think of this guide as the first practical guide to learning about cloud-native.

Master the Kubernetes CLI (kubectl) - Cheatsheet
Kubernetes

Master the Kubernetes CLI (kubectl) - Cheatsheet

This Kubernetes CLI (kubectl) cheatsheet contains the most common commands you will use when working with Kubernetes clusters and Kubernetes resources. If you're working with Kubernetes on daily basis or if you're just learning about Kubernetes you will run into a set of commands that are used often than the other commands. The ones used more often are also usually easy to remember (especially if you're typing them out multiple times a day).

What are sticky sessions and how to configure them with Istio?
Service Mesh

What are sticky sessions and how to configure them with Istio?

The idea behind sticky sessions is to route the requests for a particular session to the same endpoint that served the first request. That way to can associate a service instance with the caller, based on HTTP headers or cookies. You might want to use sticky sessions if your service is doing an expensive operation on first request, but later caching the value. That way, if the same user makes the request, the expensive operation will not be performed and value from the cache will be used.

;