You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Containers deployed on Akash have no way to know their own external hostnames and port mappings. This makes it impossible for applications to self-register or configure themselves properly without manual intervention. For example, when running database clusters, or monitoring, each node needs to know its own external endpoint to register with the cluster's configuration system.
Describe the solution you'd like
Add environment variables to all containers that provide:
The container's ingress hostname: AKASH_INGRESS_HOSTNAME
Any custom hostnames: AKASH_INGRESS_CUSTOM_HOSTNAME_{PORT}{INDEX}
External port mappings: AKASH_EXTERNAL_PORT{PORT}
This would allow containers to programmatically access their own network information and use it for self-configuration, registration with service discovery, or sharing connection details with other systems.
Describe alternatives you've considered
no good alternatives
Search
I did search for other open and closed issues before opening this
Hey @pcfreak30 !
Thanks for raising this issue.
So far, all deployments using IP lease have been limited to restarting the container with the IP_ADDRESS variable set, but this is certainly not the right solution. We need to make sure that when the environment starts, the container knows the IP assigned to it.
The same applies to ports, as you described.
So far, all deployments using IP lease have been limited to restarting the container with the IP_ADDRESS variable set that cant even technically happen as you would need a manifest update to even do that.
And that doesnt work when you need the node port which only the k8 daemon knows. its impossible to know that info by accessing ipchicken or similar.
Is your feature request related to a problem? Please describe.
Containers deployed on Akash have no way to know their own external hostnames and port mappings. This makes it impossible for applications to self-register or configure themselves properly without manual intervention. For example, when running database clusters, or monitoring, each node needs to know its own external endpoint to register with the cluster's configuration system.
Describe the solution you'd like
Add environment variables to all containers that provide:
The container's ingress hostname: AKASH_INGRESS_HOSTNAME
Any custom hostnames: AKASH_INGRESS_CUSTOM_HOSTNAME_{PORT}{INDEX}
External port mappings: AKASH_EXTERNAL_PORT{PORT}
This would allow containers to programmatically access their own network information and use it for self-configuration, registration with service discovery, or sharing connection details with other systems.
Describe alternatives you've considered
no good alternatives
Search
Code of Conduct
Additional context
See draft PR akash-network/provider#259
The text was updated successfully, but these errors were encountered: