Add Network Policy to allow traffic from the HeLx infra (resty/nginx, ambassador, appstore-sockets) pods to the appstore pod#115
Merged
pj-linebaugh merged 4 commits intodevelopfrom May 8, 2025
Conversation
…e. this will need tweeks in all helx charts if the helx parent chart is not used to deploy.
…s to communicate with appstore pod. Done a little differently so the release name is not used. This is a new feature to restrict helx app pod traffic.
pj-linebaugh
requested review from
cnbennett3,
frostyfan109,
joshua-seals and
waTeim
joshua-seals
approved these changes
May 8, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
There is already a network policy to allow traffic from the Ambassador pod(s) to the HeLx app pods. If the HeLx app pods need to communicate with other pods (gitea? grader-api?) then a network policy will need to be made to allow for that traffic. To get this to work I removed the line "- podSelector: {}" from the existing ingress.from section of the "default-namespace-isolation" networkpolicy that is added to all our namespaces. This was tested in my own namespace and I was able to create/delete HeLx app pods and see their status in the web UI. Traffic between the HeLx app pods was not allowed. This should also work for when there are multiple HeLx helm chart releases within the same namespace, but would allow for traffic between the infra pods in one release to communicate with the appstore pod in the other release.