Together with our good friends in Cloud Native Bergen meetup we are gathering to celebrate Kubernetes 10 year birthday with some exciting evening where we are going to talk about kubernetes and the hole ecosystem around. We are so luck that we have some awesome speakers with us this time

Abdelfettah Sghiouar

Abdel Sghiouar is a senior Cloud Developer Advocate @Google Cloud. A co-host of the Kubernetes Podcast by Google and a CNCF Ambassador. His focused areas are GKE/Kubernetes, Service Mesh, and Serverless. Abdel started his career in data centers and infrastructure in Morocco, where he is originally from, before moving to Google's largest EU data center in Belgium. Then in Sweden, he joined Google Cloud Professional Services and spent five years working with Google Cloud customers on architecting and designing large-scale distributed systems before turning to advocacy and community work.

Hans Kristian Flaatten

Platform Engineering at the Norwegian Labour and Welfare Administration (NAV) working on NAIS a platform built to increase development speed by providing the best experience to build, run and operate applications. Previously Principal Consultant at TietoEVRY with focus on large enterprises in public government, telecom, banking and insurance sectors. Organiser of Cloud Native and GDG meetups in Norway. Regular speaker at national and international conferences on all things cloud native.

Abstracts

Proxies, Gateways, and Service Mesh. why are words so confusing? - Abdelfettah Sghiouar

Can you tell the difference between an API Gateway, the API Gateway, and a Gateway? What are Nginx or HAProxy anyway, are they proxies? controllers? CRD’s? resources?

Sometimes it feels like things are named in a certain way to confuse us on purpose. But don’t worry this talk is made for you, to make things simple, we will go back to square zero. We will look at the history of all of these things, where they came from, and what purpose they serve. We will then fast forward into the Cloud Native modern world and you will not be surprised that nothing is new, we are just reusing stuff people used 10, 15, or 20 years ago.

Back to Basics is the other title I could have given this session. You don’t need to have a long experience, you just need to join me and we will reminisce and look into the future.

Why we standardized on OpenTelemetry -Hans Kristian Flaatten

Monitoring systems has always been fragmented, and vendor lock-in is a real issue. This is the story about how the largest branch of the Norwegian Government (NAV) is standardizing on OpenTelemetry to unlock observability data for everyone.

In 2016 NAV started adopting Kubernetes and microservices oriented architecture. This was a big change for the organization, and it was a challenge to monitor the new systems. Prometheus and Grafana were soon after chosen as the preferred monitoring stack, in addition to traditional logging of course. Fast forward to 2023, and NAV has close to 2000 microservices.

At this point NAV does not have a unified way of monitoring systems and it lacks standardization of metrics and logs. The third pillar of observability, Distributed tracing, is completely absent. This makes it hard for developers to understand the flow of requests through the system, and troubleshoot performance issues.

OpenTelemetry is a CNCF project that provides a standard for collecting telemetry data (metrics, logs, and traces) from applications. It has SDKs for all major programming languages, and is a vendor-neutral project supported by all major providers.