Skip to content

atunnel: ingress CONNECT support - #993

Open
Keith Mattix II (keithmattix) wants to merge 5 commits into
agent-substrate:mainfrom
keithmattix:atunnel-ingress-connect
Open

atunnel: ingress CONNECT support#993
Keith Mattix II (keithmattix) wants to merge 5 commits into
agent-substrate:mainfrom
keithmattix:atunnel-ingress-connect

Conversation

@keithmattix

Copy link
Copy Markdown
Collaborator

Finishes up the vision from #715 to have atunnel serve CONNECT on the ingress path. This will give us the option to hit actors on other ports besides 80

Signed-off-by: Keith Mattix II <keithmattix2@gmail.com>
Signed-off-by: Keith Mattix II <keithmattix2@gmail.com>
Signed-off-by: Keith Mattix II <keithmattix2@gmail.com>
Signed-off-by: Keith Mattix II <keithmattix2@gmail.com>
Signed-off-by: Keith Mattix II <keithmattix2@gmail.com>
@@ -78,6 +78,7 @@ func buildDeploymentApplyConfig(wp *atev1alpha1.WorkerPool, otel ateomOTelSettin
WithArgs(
"--pod-uid=$(POD_UID)",
"--atunnel-listen-address=0.0.0.0:443",

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we even need another listen address? Can't we serve everything here?

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.

2 participants