Add inbound hosts to network isolation profile #2030
Merged
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.
Fix #2023
Add support for configuring inbound hostnames in network isolation profiles.
Network isolation previously blocked container-to-container communication because the ingress proxy only allows traffic from the container's own hostname, localhost, and 127.0.0.1.
Added
inbound.allow_host
configuration to network permissions profiles.Example configuration:
Backward compatibility
For the sake of backward compatibility, if no inbound network permission profile exists, it falls back to the default which allows only the container's own hostname, localhost, and 127.0.0.1.
This is different from the default behaviour of the outbound network permissions.