envoyproxy/envoy

k8s TLS secret credential provider

Open

#35,729 opened on Aug 16, 2024

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/sdsenhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

On k8s (and other environments) secrets have an independent pipeline, e.g. k8s Secrets API. Secrets must be served independently from the rest of Envoy configuration because of the higher security expectations for credentials in-transit and at-rest over the regular xDS. Currently, this requires running an agent next to Envoy to convert from the platform secrets API to SDS, which adds a runtime overhead per instance. The feature request is to integrate with those platform APIs directly via the new credential provider functionality, bypassing SDS.

Contributor guide

Research direction
Examine the existing credential provider interface in Envoy and the Kubernetes API for secret access. Understand the SDS pipeline and how to bypass it.
Tech stack
None
Domain
infrastructurecloudsecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
KubernetesC++Envoy
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20