{"id":7830,"date":"2024-04-15T14:55:05","date_gmt":"2024-04-15T12:55:05","guid":{"rendered":"https:\/\/www.credativ.de\/?p=7830"},"modified":"2024-04-15T14:04:03","modified_gmt":"2024-04-15T12:04:03","slug":"kubecon-cloudnativecon-europe-2024","status":"publish","type":"post","link":"https:\/\/www.credativ.de\/en\/blog\/events-en\/kubecon-cloudnativecon-europe-2024\/","title":{"rendered":"KubeCon \/ CloudNativeCon Europe 2024"},"content":{"rendered":"
\"\"<\/div>\n

<\/h2>\n

Once again a KubeCon has come to an end<\/h2>\n

This year, the CNCF<\/a> hosted the meeting in the French capital. In the south of Paris at the PARIS EXPO PORTE DE VERSAILLES, over 12,000 participants came together again this year.<\/p>\n

In addition to various talks and unconferences, there was also a wide range of Contribfests slots, which made it easier for interested parties to get involved in various projects. The thematic focus this year was clearly on Artificial Intelligence and Machine Learning.<\/p>\n

Wednesday morning started at 9 am. All keynotes had one thing in common: the topic of AI\/ML! Here are a few titles: “Accelerating AI Workloads with GPUs in Kubernetes”, “Build an Open Source Platform for AI\/ML” or “Optimizing Performance and Sustainability for AI”. In addition to the keynotes, participants were also offered plenty of talks on the topic of AI and ML. Anyone interested in this topic could find what they were looking for at any time during the three days in the “Paris” room. The new white paper<\/a> on “Cloud Native AI” was also announced during the keynotes.<\/p>\n

Location<\/h2>\n

\"\" \"\"\"\"<\/p>\n

Anyone wishing to enter the conference first had to pass through security, consisting of metal detectors and possible bag checks.<\/p>\n

Unfortunately, there was again the problem of overcrowded rooms this year. Several times during the day it was necessary to reschedule spontaneously, as the selected talk was unfortunately already overcrowded and admission was no longer possible. Unfortunately, this also applied to some keynotes in the morning.<\/p>\n

A few impressions<\/h2>\n

\"\"<\/p>\n

The CNCF Storage TAG and the Storage SIG reported on current developments in the storage sector and mentioned various white papers (“CNCF Storage Whitepaper, Performance and Benchmarking whitepaper, Cloud Native Disaster Recovery whitepaper, and the Data on Kubernetes whitepaper.”). Among other things, it was shown how “PersistendVolumeAttributes” can be used to adjust PersistentVolume attributes, for example to adjust the number of IOPS for a volume during operation.<\/p>\n

In the Contribfest slot on Metal3<\/a> (Metal Kubed), the maintainers of the project gave a first insight and showed how a development environment can be set up. Among other things, Metal3 offers a ClusterAPI (CAPI) implementation that can be used to manage bare-metal systems. Ironic, which originates from the OpenStack project, is used in the background.<\/p>\n

At the “From UI to Storage” talk Thanos<\/a> maintainers gave an insight into the current implementation and potential future improvements.<\/p>\n

In the “CRI-O Odyssey”, the CRI-O<\/a> maintainers talked about innovations within the Container Runtime. This included the topic of “Confidential Containers” and “Podman-in-Kubernetes”. The topic of WASM integration was also on the agenda.<\/p>\n

The maintainers of Fink reported on “Fink on Kubernetes” and how the system is used to classify objects like astroids or supernovas in the field of astronomy.<\/p>\n

In the talk “eBPF: Abilities and Limitations”, not only general misconceptions were clarified, but also ways to work around existing limitations were pointed out. In addition, the question of whether eBPF<\/a> touring is complete was raised and a version of Conway’s “Game of Life<\/a>” in eBPF was presented.<\/p>\n

Those who have always wanted to know how Istio<\/a> mTLS can be implemented in multi-cluster environments with the help of SPIRE found what they were looking for in room D. After a short introduction to SPIFFE<\/a> and SPIRE, it was shown how Istio components can be connected to the SPIRE agent.<\/p>\n

Maintainers of operator-sdk<\/a> talked about current innovations in operator-SDK and OLM V1<\/a>. Particularly interesting were the changes in the Operator Lifecycle Manger that have been introduced in version 1 (previously version 0). Among other things, OLM v1 is now able to manage packaged operators via Helm, even without prior preparation by the operator maintainers.<\/p>\n

Conclusion<\/h2>\n

In addition to many interesting talks, there were plenty of opportunities for lively discussions with other conference attendees and exchanges with exhibitors or project maintainers.<\/p>\n

We are already looking forward to KubeCon 2025 in London<\/a>!<\/p>\n\n\t\t