Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/kubernetes/committee-security-response below:

kubernetes/committee-security-response: Kubernetes Security Process and Security Committee docs

Kubernetes Security Release Process and Security Committee documentation.

To report a vulnerability, please refer to https://kubernetes.io/security.

The Security Response Committee (SRC) is responsible for triaging and handling the security issues for Kubernetes. Following are the current Security Response Committee members:

• Adolfo García Veytia (@puerco) <adolfo.garcia@uservers.net>
• CJ Cullen (@cjcullen) <cjcullen@google.com>
• Craig Ingram (@cji) <cjingram@google.com>
• Joel Smith (@joelsmith) <joelsmith@redhat.com> [4096R/0x1688ADC79BECDDAF]
• Micah Hausler (@micahhausler) <mhausler@amazon.com>
• Mo Khan (@enj) <i@monis.app>
• Rita Zhang (@ritazh) <ritazh@microsoft.com>
• Nathan Herz (@natherz97) <nathan.herz97@gmail.com>
• Sri Saran Balaji (@SaranBalaji90) <srajakum@amazon.com>
• Tabitha Sable (@tabbysable) <tabitha.c.sable@gmail.com>
• Vyom Yadav (@Vyom-Yadav) <vyom.yadav@canonical.com>

There are a number of contact points for the SRC and release managers in charge of security releases. Please use the correct forum for the best and fastest response.

Learn how to engage with the Kubernetes community on the community page.

Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4