ABOUT THE AUTHOR

Szymon Krasuski

Software Engineer

Szymon is a Software Engineer at CodiLime. On a daily basis he develops networking solutions for cloud infrastructures, usually based on Kubernetes. He’s also a huge fan of cinematography and architecture.

Szymon Krasuski

Recent posts by Szymon:

Thumbnail of an article about Deploying a Kubernetes operator in OpenShift 4.x platform
CLOUD

Deploying a Kubernetes operator in OpenShift 4.x platform

Contrail-operator is a recently released open-source Kubernetes operator that implements Tungsten Fabricas a custom resource. Tungsten Fabric is an open-source Kubernetes-compatible, network virtualization solution for providing connectivity and security for virtual, containerized or bare-metal workloads. An operator needed to be adjusted to the OpenShift 4.x platform, which introduced numerous changes to its architecture compared with previous versions. In this blog post, you’ll read about three interesting use cases and their solutions.
Szymon Krasuski

Szymon Krasuski

on Jan 20, 2021
Thumbnail of an article about Tungsten Fabric architecture — an overview
NETWORKS

Tungsten Fabric architecture — an overview

SDN or Software-Defined Networking is an approach to networking that enables the programmatic and dynamic control of a network. It is considered the next step in the evolution of network architecture. To implement this approach effectively, you will need a mature SDN Controller such as Tungsten Fabric. Read our blog post to get a comprehensive overview of Tungsten Fabric architecture. Tungsten Fabric (previously OpenContrail) is an open-source SDN controller that provides connectivity and security for virtual, containerized or bare-metal workloads.
Multiple authors

Multiple authors

on Jan 14, 2021
Thumbnail of an article about How to create a custom resource with Kubernetes Operator
NETWORKS
CLOUD

How to create a custom resource with Kubernetes Operator

While developing projects on the Kubernetes platform I came across an interesting problem. I had quite a few scripts that ran in containers and needed to be triggered only once on every node in my Kubernetes cluster. This could not be solved using default Kubernetes resources such as DaemonSet and Job. So I decided to write my own resource using Kubernetes Operator Framework. How I went about it is the subject of this blog post. When I confronted this problem, my first thought was to use a DaemonSet resource that utilizes initContainers and then starts a dummy busybox container running `tail -f /dev/null` or another command that does nothing.
Szymon Krasuski

Szymon Krasuski

on Nov 12, 2020