Support to encrypt metadata traffic
Open
kind/feature
lifecycle/active
triage/accepted
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 1.2k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 2
Description
As described in [the feature docs](https://docs.google.com/document/d/1XE7UzgQlVVtAb7ULSqOyKCaIHtm8zMF35ainp1JmwyY/edit?resourcekey=0-e1MXRxQaalq-EHW46ZCCWg#):
> NOT IN SCOPE:
> Scaling metadata (not request data) user pods <-> autoscaler, activator <-> autoscaler.
the alpha release does not support the encrypted traffic for metadata but we should support it in the future.
Contributor guide
Research direction
Start with the linked feature document and compare its metadata-traffic scope with the issue's excluded autoscaler paths. Identify the relevant implementation and tests for metadata traffic, then define done as supporting encrypted metadata traffic for the in-scope paths and adding coverage for that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100