[Local] Allow disabling port publishing on host network #3127
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently we do not have an option for local (docker) environments to disable publishing the function container port on the host network. The only options are to select a specific port or a a random port.
This can cause possible security issues for users who do not want to expose their function on external URLs.
In this PR I've added to option to avoid publishing the function on the host network using the trigger attributes, which can be set in the function spec as follows:
Until this feature will be enabled in the GUI as well, this can also be set via trigger annotations, with the followin annotation:
Note - this is already supported in a Kubernetes environment.
Resolves #2468