Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(proto-config): Add http protocol configuration #13661

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

sfleen
Copy link
Contributor

@sfleen sfleen commented Feb 14, 2025

This adds "http" and "kubernetes.io/h2c" as a valid values for service port appProtocol. Continuation of #13660.

@sfleen sfleen requested a review from a team as a code owner February 14, 2025 21:05
@sfleen sfleen force-pushed the protocol-detect-http1 branch 2 times, most recently from a24351b to 59a33b5 Compare February 17, 2025 14:39
Currently, we store whether or not a port in a parent is opaque with a simple boolean. This works, but is somewhat restrictive if we want to specifiy different port protocols in the resource definition.

This converts it to a proper `AppProtocol` enum, which will allow us to use different protocol specifications for ports in the future.

Signed-off-by: Scott Fleener <[email protected]>
This allows specifying that a service port is opaque via `"linkerd.io/opaque"` in the `appProtocol` field.

This also includes a fair amount of tests and test infrastructure for future `appProtocol` values.

Signed-off-by: Scott Fleener <[email protected]>
This adds `"http"` and `"kubernetes.io/h2c"` as a valid values for service port `appProtocol`.

Signed-off-by: Scott Fleener <[email protected]>
@sfleen sfleen force-pushed the protocol-detect-http1 branch from 59a33b5 to c8bbd55 Compare February 17, 2025 14:56
@olix0r olix0r marked this pull request as draft February 17, 2025 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant