feat: add NetworkPolicy to allow runner pod ingress#70
Merged
Conversation
Add NetworkPolicy to deploy templates allowing ingress traffic from
runner pods to backend-api. This resolves connectivity issues where
runner pods in user namespaces cannot reach backend-service due to
default-deny NetworkPolicies.
The NetworkPolicy:
- Targets backend-api pods specifically (vs. all pods)
- Allows ingress from ambient-code-runner pods across all namespaces
- Uses ${NAMESPACE} template parameter for proper scoping
Based on upstream PR: ambient-code#1553
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
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
1 participant
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.
Summary
Add NetworkPolicy to deploy templates allowing ingress traffic from runner pods to backend-api. This resolves connectivity issues where runner pods in user namespaces cannot reach backend-service due to default-deny NetworkPolicies.
Changes
template-operator.yamlbackend-apipods specifically (more restrictive than upstream)ambient-code-runnerpods across all namespaces${NAMESPACE}template parameter for proper scopingBased on upstream PR
This implements the fix from ambient-code/platform#1553 with improvements:
app: backend-apipods instead of all pods in the namespace${NAMESPACE}for consistency with OpenShift template patternsTesting
./validate.sh)Fixes
Resolves
INITIAL_PROMPT TimeoutErrorduring session startup when runner pods in user namespaces cannot reach backend-service.🤖 Generated with Claude Code
Co-Authored-By: Claude noreply@anthropic.com