Support disabling HTTP traffic between Ingress and activator
Open
kind/feature
lifecycle/frozen
triage/accepted
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 1.2k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 2
Description
Support disabling HTTP traffic between Ingress and activator
As described in [the feature docs](https://docs.google.com/document/d/1XE7UzgQlVVtAb7ULSqOyKCaIHtm8zMF35ainp1JmwyY/edit?resourcekey=0-e1MXRxQaalq-EHW46ZCCWg#):
> it will similarly want an ENCRYPTED_ONLY variable (or file) to disable the non-encrypted paths.
the future release should support to disable the non-encrypted paths.
Contributor guide
Research direction
Start with the linked feature documentation to understand the proposed ENCRYPTED_ONLY variable or file and the Ingress-to-activator paths it should affect. Map those non-encrypted paths in the repository and define done as preventing HTTP traffic between Ingress and activator while preserving encrypted traffic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100