1_r/devopsish

1_r/devopsish

54593 bookmarks
Custom sorting
Spotlight on Kubernetes Upstream Training in Japan
Spotlight on Kubernetes Upstream Training in Japan

Spotlight on Kubernetes Upstream Training in Japan

https://kubernetes.io/blog/2024/10/28/k8s-upstream-training-japan-spotlight/

About our team

We are organizers of Kubernetes Upstream Training in Japan. Our team is composed of members who actively contribute to Kubernetes, including individuals who hold roles such as member, reviewer, approver, and chair.

Our goal is to increase the number of Kubernetes contributors and foster the growth of the community. While Kubernetes community is friendly and collaborative, newcomers may find the first step of contributing to be a bit challenging. Our training program aims to lower that barrier and create an environment where even beginners can participate smoothly.

What is Kubernetes upstream training in Japan?

Our training started in 2019 and is held 1 to 2 times a year. Initially, Kubernetes Upstream Training was conducted as a co-located event of KubeCon (Kubernetes Contributor Summit), but we launched Kubernetes Upstream Training in Japan with the aim of increasing Japanese contributors by hosting a similar event in Japan.

Before the pandemic, the training was held in person, but since 2020, it has been conducted online. The training offers the following content for those who have not yet contributed to Kubernetes:

Introduction to Kubernetes community

Overview of Kubernetes codebase and how to create your first PR

Tips and encouragement to lower participation barriers, such as language

How to set up the development environment

Hands-on session using kubernetes-sigs/contributor-playground

At the beginning of the program, we explain why contributing to Kubernetes is important and who can contribute. We emphasize that contributing to Kubernetes allows you to make a global impact and that Kubernetes community is looking forward to your contributions!

We also explain Kubernetes community, SIGs, and Working Groups. Next, we explain the roles and responsibilities of Member, Reviewer, Approver, Tech Lead, and Chair. Additionally, we introduce the communication tools we primarily use, such as Slack, GitHub, and mailing lists. Some Japanese speakers may feel that communicating in English is a barrier. Additionally, those who are new to the community need to understand where and how communication takes place. We emphasize the importance of taking that first step, which is the most important aspect we focus on in our training!

We then go over the structure of Kubernetes codebase, the main repositories, how to create a PR, and the CI/CD process using Prow. We explain in detail the process from creating a PR to getting it merged.

After several lectures, participants get to experience hands-on work using kubernetes-sigs/contributor-playground, where they can create a simple PR. The goal is for participants to get a feel for the process of contributing to Kubernetes.

At the end of the program, we also provide a detailed explanation of setting up the development environment for contributing to the kubernetes/kubernetes repository, including building code locally, running tests efficiently, and setting up clusters.

Interview with participants

We conducted interviews with those who participated in our training program. We asked them about their reasons for joining, their impressions, and their future goals.

Keita Mochizuki (NTT DATA Group Corporation)

Keita Mochizuki is a contributor who consistently contributes to Kubernetes and related projects. Keita is also a professional in container security and has recently published a book. Additionally, he has made available a Roadmap for New Contributors, which is highly beneficial for those new to contributing.

Junya: Why did you decide to participate in Kubernetes Upstream Training?

Keita: Actually, I participated twice, in 2020 and 2022. In 2020, I had just started learning about Kubernetes and wanted to try getting involved in activities outside of work, so I signed up after seeing the event on Twitter by chance. However, I didn't have much knowledge at the time, and contributing to OSS felt like something beyond my reach. As a result, my understanding after the training was shallow, and I left with more of a "hmm, okay" feeling.

In 2022, I participated again when I was at a stage where I was seriously considering starting contributions. This time, I did prior research and was able to resolve my questions during the lectures, making it a very productive experience.

Junya: How did you feel after participating?

Keita: I felt that the significance of this training greatly depends on the participant's mindset. The training itself consists of general explanations and simple hands-on exercises, but it doesn't mean that attending the training will immediately lead to contributions.

Junya: What is your purpose for contributing?

Keita: My initial motivation was to "gain a deep understanding of Kubernetes and build a track record," meaning "contributing itself was the goal." Nowadays, I also contribute to address bugs or constraints I discover during my work. Additionally, through contributing, I've become less hesitant to analyze undocumented features directly from the source code.

Junya: What has been challenging about contributing?

Keita: The most difficult part was taking the first step. Contributing to OSS requires a certain level of knowledge, and leveraging resources like this training and support from others was essential. One phrase that stuck with me was, "Once you take the first step, it becomes easier to move forward." Also, in terms of continuing contributions as part of my job, the most challenging aspect is presenting the outcomes as achievements. To keep contributing over time, it's important to align it with business goals and strategies, but upstream contributions don't always lead to immediate results that can be directly tied to performance. Therefore, it's crucial to ensure mutual understanding with managers and gain their support.

Junya: What are your future goals?

Keita: My goal is to contribute to areas with a larger impact. So far, I've mainly contributed by fixing smaller bugs as my primary focus was building a track record, but moving forward, I'd like to challenge myself with contributions that have a greater impact on Kubernetes users or that address issues related to my work. Recently, I've also been working on reflecting the changes I've made to the codebase into the official documentation, and I see this as a step toward achieving my goals.

Junya: Thank you very much!

Yoshiki Fujikane (CyberAgent, Inc.)

Yoshiki Fujikane is one of the maintainers of PipeCD, a CNCF Sandbox project. In addition to developing new features for Kubernetes support in PipeCD, Yoshiki actively participates in community management and speaks at various technical conferences.

Junya: Why did you decide to participate in the Kubernetes Upstream Training?

Yoshiki: At the time I participated, I was still a student. I had only briefly worked with EKS, but I thought Kubernetes seemed complex yet cool, and I was casually interested in it. Back then, OSS felt like something out of reach, and upstream development for Kubernetes seemed incredibly daunting. While I had always been interested in OSS, I didn't know where to start. It was during this time that I learned about the Kubernetes Upstream Training and decided to take the challenge of contributing to Kubernetes.

Junya: What were your impressions after participating?

Yoshiki: I found it extremely valuable as a way to understand what it's like to be part of an OSS community. At the time, my English skills weren't very strong, so accessing primary sources of information felt like a big hurdle for me. Kubernetes is a very large project, and I didn't have a clear understanding of the overall structure, let alone what was necessary for contributing. The upstream training provided a Japanese explanation of the community structure and allowed me to gain hands-on experience with actual contributions. Thanks to the guidance I received, I was able to learn how to approach primary sources and use them as entry points for further investigation, which was incredibly helpful. This experience made me realize the importance of organizing and reviewing primary sources, and now I often dive into GitHub issues and documentation when something piques my interest. As a result, while I am no longer contributing to Kubernetes itself, the experience has been a great foundation for contributing to other projects.

Junya: What areas are you currently contributing to, and what are the other projects you're involved in?

Yoshiki: Right now, I'm no longer working with Kubernetes, but instead, I'm a maintainer of PipeCD, a CNCF Sandbox project. PipeCD is a CD tool that supports GitOps-style deployments for various application platforms. The tool originally started as an internal project at CyberAgent. With different teams adopting different platforms, PipeCD was developed to provide a unified CD platform with a consistent user experience. Currently, it supports Kubernetes, AWS ECS, Lambda, Cloud Run, and Terraform.

Junya: What role do you play within the PipeCD team?

Yoshiki: I work full-time on improving and developing Kubernetes-related features within the team. Since we provide PipeCD as a SaaS internally, my main focus is on adding new features and improving existing ones as part of that support. In addition to code contributions, I also contribute by giving talks at various events and managing community meetings to help grow the PipeCD community.

Junya: Could you explain what kind of improvements or developments you are working on with regards to Kubernetes?

Yoshiki: PipeCD supports GitOps and Progressive Delivery for Kubernetes, so I'm involved in the development of those features. Recently, I've been working on features that streamline deployments across multiple clusters.

Junya: Have you encountered any challenges while contributing to OSS?

Yoshiki: One challenge is developin

·kubernetes.io·
Spotlight on Kubernetes Upstream Training in Japan
Blog: Spotlight on Kubernetes Upstream Training in Japan
Blog: Spotlight on Kubernetes Upstream Training in Japan

Blog: Spotlight on Kubernetes Upstream Training in Japan

https://www.kubernetes.dev/blog/2024/10/28/k8s-upstream-training-japan-spotlight/

About our team

We are organizers of Kubernetes Upstream Training in Japan. Our team is composed of members who actively contribute to Kubernetes, including individuals who hold roles such as member, reviewer, approver, and chair.

Our goal is to increase the number of Kubernetes contributors and foster the growth of the community. While Kubernetes community is friendly and collaborative, newcomers may find the first step of contributing to be a bit challenging. Our training program aims to lower that barrier and create an environment where even beginners can participate smoothly.

What is Kubernetes upstream training in Japan?

Our training started in 2019 and is held 1 to 2 times a year. Initially, Kubernetes Upstream Training was conducted as a co-located event of KubeCon (Kubernetes Contributor Summit), but we launched Kubernetes Upstream Training in Japan with the aim of increasing Japanese contributors by hosting a similar event in Japan.

Before the pandemic, the training was held in person, but since 2020, it has been conducted online. The training offers the following content for those who have not yet contributed to Kubernetes:

Introduction to Kubernetes community

Overview of Kubernetes codebase and how to create your first PR

Tips and encouragement to lower participation barriers, such as language

How to set up the development environment

Hands-on session using kubernetes-sigs/contributor-playground

At the beginning of the program, we explain why contributing to Kubernetes is important and who can contribute. We emphasize that contributing to Kubernetes allows you to make a global impact and that Kubernetes community is looking forward to your contributions!

We also explain Kubernetes community, SIGs, and Working Groups. Next, we explain the roles and responsibilities of Member, Reviewer, Approver, Tech Lead, and Chair. Additionally, we introduce the communication tools we primarily use, such as Slack, GitHub, and mailing lists. Some Japanese speakers may feel that communicating in English is a barrier. Additionally, those who are new to the community need to understand where and how communication takes place. We emphasize the importance of taking that first step, which is the most important aspect we focus on in our training!

We then go over the structure of Kubernetes codebase, the main repositories, how to create a PR, and the CI/CD process using Prow. We explain in detail the process from creating a PR to getting it merged.

After several lectures, participants get to experience hands-on work using kubernetes-sigs/contributor-playground, where they can create a simple PR. The goal is for participants to get a feel for the process of contributing to Kubernetes.

At the end of the program, we also provide a detailed explanation of setting up the development environment for contributing to the kubernetes/kubernetes repository, including building code locally, running tests efficiently, and setting up clusters.

Interview with participants

We conducted interviews with those who participated in our training program. We asked them about their reasons for joining, their impressions, and their future goals.

Keita Mochizuki (NTT DATA Group Corporation)

Keita Mochizuki is a contributor who consistently contributes to Kubernetes and related projects. Keita is also a professional in container security and has recently published a book. Additionally, he has made available a Roadmap for New Contributors, which is highly beneficial for those new to contributing.

Junya: Why did you decide to participate in Kubernetes Upstream Training?

Keita: Actually, I participated twice, in 2020 and 2022. In 2020, I had just started learning about Kubernetes and wanted to try getting involved in activities outside of work, so I signed up after seeing the event on Twitter by chance. However, I didn’t have much knowledge at the time, and contributing to OSS felt like something beyond my reach. As a result, my understanding after the training was shallow, and I left with more of a “hmm, okay” feeling.

In 2022, I participated again when I was at a stage where I was seriously considering starting contributions. This time, I did prior research and was able to resolve my questions during the lectures, making it a very productive experience.

Junya: How did you feel after participating?

Keita: I felt that the significance of this training greatly depends on the participant’s mindset. The training itself consists of general explanations and simple hands-on exercises, but it doesn’t mean that attending the training will immediately lead to contributions.

Junya: What is your purpose for contributing?

Keita: My initial motivation was to “gain a deep understanding of Kubernetes and build a track record,” meaning “contributing itself was the goal.” Nowadays, I also contribute to address bugs or constraints I discover during my work. Additionally, through contributing, I’ve become less hesitant to analyze undocumented features directly from the source code.

Junya: What has been challenging about contributing?

Keita: The most difficult part was taking the first step. Contributing to OSS requires a certain level of knowledge, and leveraging resources like this training and support from others was essential. One phrase that stuck with me was, “Once you take the first step, it becomes easier to move forward.” Also, in terms of continuing contributions as part of my job, the most challenging aspect is presenting the outcomes as achievements. To keep contributing over time, it’s important to align it with business goals and strategies, but upstream contributions don’t always lead to immediate results that can be directly tied to performance. Therefore, it’s crucial to ensure mutual understanding with managers and gain their support.

Junya: What are your future goals?

Keita: My goal is to contribute to areas with a larger impact. So far, I’ve mainly contributed by fixing smaller bugs as my primary focus was building a track record, but moving forward, I’d like to challenge myself with contributions that have a greater impact on Kubernetes users or that address issues related to my work. Recently, I’ve also been working on reflecting the changes I’ve made to the codebase into the official documentation, and I see this as a step toward achieving my goals.

Junya: Thank you very much!

Yoshiki Fujikane (CyberAgent, Inc.)

Yoshiki Fujikane is one of the maintainers of PipeCD, a CNCF Sandbox project. In addition to developing new features for Kubernetes support in PipeCD, Yoshiki actively participates in community management and speaks at various technical conferences.

Junya: Why did you decide to participate in the Kubernetes Upstream Training?

Yoshiki: At the time I participated, I was still a student. I had only briefly worked with EKS, but I thought Kubernetes seemed complex yet cool, and I was casually interested in it. Back then, OSS felt like something out of reach, and upstream development for Kubernetes seemed incredibly daunting. While I had always been interested in OSS, I didn’t know where to start. It was during this time that I learned about the Kubernetes Upstream Training and decided to take the challenge of contributing to Kubernetes.

Junya: What were your impressions after participating?

Yoshiki: I found it extremely valuable as a way to understand what it’s like to be part of an OSS community. At the time, my English skills weren’t very strong, so accessing primary sources of information felt like a big hurdle for me. Kubernetes is a very large project, and I didn’t have a clear understanding of the overall structure, let alone what was necessary for contributing. The upstream training provided a Japanese explanation of the community structure and allowed me to gain hands-on experience with actual contributions. Thanks to the guidance I received, I was able to learn how to approach primary sources and use them as entry points for further investigation, which was incredibly helpful. This experience made me realize the importance of organizing and reviewing primary sources, and now I often dive into GitHub issues and documentation when something piques my interest. As a result, while I am no longer contributing to Kubernetes itself, the experience has been a great foundation for contributing to other projects.

Junya: What areas are you currently contributing to, and what are the other projects you’re involved in?

Yoshiki: Right now, I’m no longer working with Kubernetes, but instead, I’m a maintainer of PipeCD, a CNCF Sandbox project. PipeCD is a CD tool that supports GitOps-style deployments for various application platforms. The tool originally started as an internal project at CyberAgent. With different teams adopting different platforms, PipeCD was developed to provide a unified CD platform with a consistent user experience. Currently, it supports Kubernetes, AWS ECS, Lambda, Cloud Run, and Terraform.

Junya: What role do you play within the PipeCD team?

Yoshiki: I work full-time on improving and developing Kubernetes-related features within the team. Since we provide PipeCD as a SaaS internally, my main focus is on adding new features and improving existing ones as part of that support. In addition to code contributions, I also contribute by giving talks at various events and managing community meetings to help grow the PipeCD community.

Junya: Could you explain what kind of improvements or developments you are working on with regards to Kubernetes?

Yoshiki: PipeCD supports GitOps and Progressive Delivery for Kubernetes, so I’m involved in the development of those features. Recently, I’ve been working on features that streamline deployments across multiple clusters.

Junya: Have you encountered any challenges while contributing to OSS?

Yoshiki: One challenge i

·kubernetes.dev·
Blog: Spotlight on Kubernetes Upstream Training in Japan
DevOps Toolkit - Service Mesh - Feat. Cilium Istio Linkerd and Kuma (You Choose! Ch. 04 Ep. 08) - https://www.youtube.com/watch?v=g-tHbIcFYTM
DevOps Toolkit - Service Mesh - Feat. Cilium Istio Linkerd and Kuma (You Choose! Ch. 04 Ep. 08) - https://www.youtube.com/watch?v=g-tHbIcFYTM

Service Mesh - Feat. Cilium, Istio, Linkerd, and Kuma (You Choose!, Ch. 04, Ep. 08)

Service Mesh - Choose Your Own Adventure: The Observability Odyssey

In this episode, we'll go through networking and service mesh observability. The contestants are Cilium, Istio, Linkerd, and Kuma.

Vote for your choice of a tool for signing artifacts at https://cloud-native.slack.com/archives/C05M2NFNVRN. If you have not already joined CNCF Slack, you can do so from https://slack.cncf.io.

This and all other episodes are available at https://www.youtube.com/playlist?list=PLyicRj904Z9-FzCPvGpVHgRQVYJpVmx3Z.

More information about the "Choose Your Own Adventure" project including the source code and links to all the videos can be found at https://github.com/vfarcic/cncf-demo.

٩( ᐛ )و Whitney's YouTube Channel → https://www.youtube.com/@wiggitywhitney

cilium #istio #linkerd #kuma

▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬ 🔗 Service Mesh: https://github.com/vfarcic/cncf-demo/tree/main/manuscript/service-mesh/README.md

via YouTube https://www.youtube.com/watch?v=g-tHbIcFYTM

·youtube.com·
DevOps Toolkit - Service Mesh - Feat. Cilium Istio Linkerd and Kuma (You Choose! Ch. 04 Ep. 08) - https://www.youtube.com/watch?v=g-tHbIcFYTM
MQTT turns 25 heres how it has endured
MQTT turns 25 heres how it has endured

MQTT turns 25 – here’s how it has endured

It’s October 2024 and I’m sitting here in my creative maker studio, wearing a bright t-shirt that excitedly bellows “MQTT 25”! To my left is a top-end Bambu Lab…

October 25, 2024 at 12:26PM

via Instapaper

·andypiper.co.uk·
MQTT turns 25 heres how it has endured
Location tracking of phones is out of control. Heres how to fight back.
Location tracking of phones is out of control. Heres how to fight back.

Location tracking of phones is out of control. Here’s how to fight back.

I KNOW WHAT YOU DID LAST SUMMER Location tracking of phones is out of control. Here’s how to fight back. Unique IDs assigned to Android and iOS devices threaten…

October 25, 2024 at 10:33AM

via Instapaper

·arstechnica.com·
Location tracking of phones is out of control. Heres how to fight back.
Everything I built with Claude Artifacts this week
Everything I built with Claude Artifacts this week
I’m a huge fan of Claude’s Artifacts feature, which lets you prompt Claude to create an interactive Single Page App (using HTML, CSS and JavaScript) and then view the result …
·simonwillison.net·
Everything I built with Claude Artifacts this week
The enterprise verdict on AI models: Why open source will win
The enterprise verdict on AI models: Why open source will win

The enterprise verdict on AI models: Why open source will win

Image Credit: VentureBeat via StableDiffusion The enterprise world is rapidly growing its usage of open source large language models (LLMs), driven by companies…

October 24, 2024 at 02:09PM

via Instapaper

·venturebeat.com·
The enterprise verdict on AI models: Why open source will win
Promoting Apps to Production: How To Ensure That a Change Only Deploys to Lower Environments?
Promoting Apps to Production: How To Ensure That a Change Only Deploys to Lower Environments?

Promoting Apps to Production: How To Ensure That a Change Only Deploys to Lower Environments?

Today, we dive into ensuring changes deploy only to lower environments before hitting production. We'll explore two methods: GitOps with pull request reviews and automated policies using Kyverno or OPA Gatekeeper. Discover how signed images and Kubernetes Admission Controllers can help automate and secure your deployment pipeline, ensuring only tested and approved changes reach production. Join us as we answer @Mvvement's question on promoting applications safely. Don't forget to comment your questions below and consider joining the channel for priority responses!

DevOps #Kubernetes #GitOps #DeploymentSecurity

Consider joining the channel: https://www.youtube.com/c/devopstoolkit/join

▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬ 🔗 N/A: N/A

▬▬▬▬▬▬ 💰 Sponsorships 💰 ▬▬▬▬▬▬ If you are interested in sponsoring this channel, please visit https://devopstoolkit.live/sponsor for more information. Alternatively, feel free to contact me over Twitter or LinkedIn (see below).

▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬ ➡ Twitter: https://twitter.com/vfarcic ➡ LinkedIn: https://www.linkedin.com/in/viktorfarcic/

▬▬▬▬▬▬ 🚀 Other Channels 🚀 ▬▬▬▬▬▬ 🎤 Podcast: https://www.devopsparadox.com/ 💬 Live streams: https://www.youtube.com/c/DevOpsParadox

via YouTube https://www.youtube.com/watch?v=8WkFgLDCQg8

·youtube.com·
Promoting Apps to Production: How To Ensure That a Change Only Deploys to Lower Environments?
- YouTube
- YouTube
  • YouTube

October 24, 2024 at 11:02AM

via Instapaper

·youtube.com·
- YouTube
Linus Torvalds Comments On The Russian Linux Maintainers Being Delisted
Linus Torvalds Comments On The Russian Linux Maintainers Being Delisted
Following yesterday's news first featured on Phoronix of several Linux driver maintainers being de-listed from their maintainer positions within the mainline Linux kernel over their connections to Russia, Linus Torvalds has today commented on the matter.
·phoronix.com·
Linus Torvalds Comments On The Russian Linux Maintainers Being Delisted
Last Week in Kubernetes Development - Week Ending October 20 2024
Last Week in Kubernetes Development - Week Ending October 20 2024

Week Ending October 20, 2024

https://lwkd.info/2024/20241022

Developer News

Join other members of your SIG for the Kubernetes SIG Meet & Greet & Lunch & Learn at Kubecon on Nov 14th. Sign up to table for your SIG.

If you are a SIG lead, please also add callouts for the Summit opening session to find new contributors for your SIG.

The Summit Social will be at Flanker and will have the usual fun & games. Unusually, due to Utah law, you will be required to bring an ID/passport. Also, the Summit is still looking for volunteers to help staff.

Release Schedule

Next Deadline: Docs placeholder PRs deadline, October 24

We are now in Enhancements Freeze, and Alpha2 has been released. For those working on 1.32 enhancements and documentation updates, now’s the time to open your PR against dev-1.32 on the kubernetes/website repo. It would be awesome if full docs are ready, but a placeholder PR will keep your contribution on track. Final exceptions for missed Enhancements are due on Monday.

October patch releases were delayed due to Go update issues. They are available now for v1.28.15, v1.29.10, v1.30.6, and v1.31.2.

KEP of the Week

KEP 784: Kube Proxy component configuration graduation

This KEP proposes a plan to graduate kube-proxy’s component configuration to beta, addressing its current complexity. Originally configured via command-line flags, kube-proxy’s config became difficult to manage as new features were added, staying in v1alpha1. The current format is hard to use, with poorly grouped options and inconsistencies, making restructuring and stabilization necessary.

This KEP is tracked for alpha release in the ongoing v1.32 cycle.

Other Merges

scheduler_perf test cases added for NodeUpdate event handling

Apply fsGroup policy for ReadWriteOncePod volumes

Fix AssignedPodUpdated in scheduler to check if the incoming events are scale down events

Removed legacy cloud provider integration code from kube-controller-manager

Fix for 1.31 regression that can crash kube-controller-manager’s service-lb-controller loop

Clarification for API validation error for toleration if operator is Exists and value is not empty

Fix for kubelet wrongly dropping the QOSClass field of the Pod’s status when it rejects a Pod

Image pull error used in messages during back-off

Fix for failing storage e2e test

Improvements to CSILimits plugin accuracy by using VolumeAttachments

Added kubelet support for systemd watchdog integration

More fine-grained QHints for podtopologyspread plugin

Add e2e test for custom profile in kubectl debug

container_aligned_compute_resources_count metric added to kubelet to report containers getting aligned compute resources

corev1.Binding deprecation message removed

kubeadm removes preflight check for existence of conntrack binary

e2e tests added for ClusterTrustBundle to prepare promotion to beta

Fixed issue in the kubelet that showed when writeable layers and read-only layers were at different paths within the same mount

Fine-grained kubelet API authorization checks added for kubelet /configz, /healthz and /pods API

CRI adds field to support CPU affinity on Windows

Refactor for node shutdown manager

Promotions

StructuredAuthorizationConfiguration to GA

ServiceAccountTokenJTI, ServiceAccountTokenPodNodeInfo and ServiceAccountTokenNodeBindingValidation to GA

AuthorizeNodeWithSelectors and AuthorizeWithSelectors to beta

RelaxedEnvironmentVariableValidation to beta

Deprecated

PostStartHookContext.StopCh removed

Version Updates

publishing-bot rules updated to Go 1.22.8

via Last Week in Kubernetes Development https://lwkd.info/

October 22, 2024 at 12:30PM

·lwkd.info·
Last Week in Kubernetes Development - Week Ending October 20 2024
Rustls Outperforms OpenSSL and BoringSSL
Rustls Outperforms OpenSSL and BoringSSL
ISRG has been investing heavily in the Rustls TLS library over the past few years. Our goal is to create a library that is both memory safe and a leader in performance. Back in January of this year we published a post about the start of our performance journey. We've come a long way since then and we're excited to share an update on Rustls performance today. What is Rustls? Rustls is a memory safe TLS implementation with a focus on performance.
·memorysafety.org·
Rustls Outperforms OpenSSL and BoringSSL
Several Linux Kernel Driver Maintainers Removed Due To Their Association To Russia
Several Linux Kernel Driver Maintainers Removed Due To Their Association To Russia
Quietly merged into this week's Linux 6.12-rc4 kernel was a patch that removes a number of kernel maintainers from being noted in the official MAINTAINERS file that recognizes all of the driver and subsystem maintainers.
·phoronix.com·
Several Linux Kernel Driver Maintainers Removed Due To Their Association To Russia
Initial explorations of Anthropic’s new Computer Use capability
Initial explorations of Anthropic’s new Computer Use capability
Two big announcements from Anthropic today: a new Claude 3.5 Sonnet model and a new API mode that they are calling computer use. (They also pre-announced 3.5 Haiku, but that’s …
·simonwillison.net·
Initial explorations of Anthropic’s new Computer Use capability