-
Notifications
You must be signed in to change notification settings - Fork 13
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
Support setting HTTP trigger listen address in env var #138
Support setting HTTP trigger listen address in env var #138
Conversation
Signed-off-by: Kate Goldenring <kate.goldenring@fermyon.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
LGTM :) |
@radu-matei @jsturtevant @Mossaka @devigned it would be great to get this merged before the next release if possible. There are two commented LGTMs but a review would be appreciated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 lgtm.
One thing to consider for future, but might be hard to change at this point, is that the default port is 80
. Perhaps, we may want to consider a higher port range default.
Also, it might be nice to represent the informational container spec field of ports.containerPorts
with the value of the SPIN_HTTP_LISTEN_ADDR_ENV
via the Spin operator when creating the SpinApp
, so it's more clear to folks.
@devigned, to clarify, are you suggesting adding a |
@kate-goldenring hmm... not necessarily adding apiVersion: ...
kind: SpinApp
metadata:
name: my-app
spec:
httpListeningPort: 3000 # this drives configuration of the pod / container spec and informs the pod.spec.ports.containerPort
otherStuff: ...
---
apiVersion: v1
kind: Pod
metadata:
name: my-app
spec:
containers:
- name: spin-app
ports:
- containerPort: 3000 # this is only for information |
Enables setting the shim's HTTP trigger listen address in
SPIN_HTTP_LISTEN_ADDR
(same naming scheme as Spin CLI). This can now be set in a container spec, which follows the approach of configuring the Spin runtime via container environment variables that is laid out in this draft SKIP.closes #52
related #128