ABOUT THE AUTHOR

Piotr Skamruk

Senior Software Engineer

Piotr is a long-time GNU/Linux and Forth language enthusiast, sys administrator and sys developer. He has worked on kernel sources, backend apps and even on frontends in a wide variety of languages. He worked on CoreOS RKT and was also a member of Virtlet Team, writing a Kubernetes runtime that made it possible to run VM workloads. At CodiLime, he’s working on networking solutions for Kubernetes.

Piotr Skamruk

Recent posts by Piotr:

Thumbnail of an article about Kubernetes workloads — using multiple networks
NETWORKS

Kubernetes workloads — using multiple networks

Since there is no separate networking object among Kubernetes objects enabling the running of multiple networks, a workaround is required. Using a Container Network Interface (CNI) is a good place to start. Read this blog post to learn how you can use it to get multiple networks for Kubernetes workloads. I also describe my proposal for changes in source code that will enable native handling of multiple networks in Kubernetes. This blog post is based on the presentation which Doug Smith from Red Hat and I gave at the KubeCon+CloudNativeCon North America 2019 conference.
Thumbnail of an article about Uncontainerizable VNFs in a CNF environment
NETWORKS

Uncontainerizable VNFs in a CNF environment

Cloud-native network functions (CNFs, for short) are a hot topic in network architecture. CNFs use containers as the base for network functions and thus would replace today’s most widely used standard, Virtual Network Functions (VNFs). In such a scenario, a container orchestration platform--Kubernetes, say--could be responsible not only for orchestrating the containers, but also for directing network traffic to proper pods. While this remains an area under research, it has aroused considerable interest among industry leaders.