fix/k8s-port-mappings-v5 #994
Open
AFDudley
wants to merge 4 commits from
fix/k8s-port-mappings-v5 into main
pull from: fix/k8s-port-mappings-v5
merge into: :main
:main
:afd-dumpster-local-testing
:merge-multi-http-proxy
:fix/kind-mount-propagation
:add/local-test-runner
:fix/k8s-port-mappings-v5
:fix/k8s-port-mappings-hostnetwork
:feature/secrets-support
:fix-etcd-drop-stale-acme
:multi-http-proxy
:fix-sidecar-localhost
:feat-namespace-per-deployment
:fix-down-cleanup-by-label
:fix-kind-relative-volume-paths
:fix-init-volumes-merge
:caddy-pvc-persistence
:roysc/deployment-create-sync
:multi-port-service
:helm-charts-with-caddy
:afd
:feat/trashscan-explorer-stack
:helm-charts-support
:vaasl-deploy
:roysc/deploy-create-extra-args
:zach/atom-payments
:zramsay-patch-1
:roysc/deploy-create-pass-cluster
:zach/update-url
:telackey/defaultplatform
:telackey/924
:telackey/laconicdv1
:zach/pin-cli-version
:telackey/wagit
:add-vega-stack
:blast-stack
:lotus-stack
:roysc/fix-eth-stacks
:telackey/na
:telackey/fqdn
:zach/snowdocs
:zach/fixturenet-2d
:telackey/wild
:dboreham/mobymask-v3-demo-test
:zach/fix-for-mars
:ci-test
:optimism-fix
:telackey/envsubst
:dboreham/laconicd-k8s
:zach/birbit
:osmosis
:iskay/update-optimism
:iskay/plugeth-test-update
:iskay/fixturenet-payments-test
:iskay/fixturenet-laconicd-test
:iskay/fixturenet-eth-test
:new-gitea-test
:erc20-fix
:update-uniswap
:tel/1.20
:telackey/systest
:ng-deny-multiaddr
:publish-test
:telackey/datanet
No Reviewers
Labels
Clear labels
K8s
bug
documentation
duplicate
enhancement
feature
good first issue
help wanted
in progress
invalid
question
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Something isn't working
Improvements or additions to documentation
This issue or pull request already exists
New feature or request
Good for newcomers
Extra attention is needed
This doesn't seem right
Further information is requested
This will not be worked on
An issue or PR manually copied from GitHub.
Breaking change that won't be backward compatible
Something is not working
Documentation changes
Improve existing functionality
New functionality
This is security issue
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
No due date set.
Dependencies
No dependencies set.
Reference: cerc-io/stack-orchestrator#994
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When kind-mount-root is set in spec.yml, emit a single extraMount mapping the root to /mnt instead of per-volume mounts. This allows adding new volumes without recreating the kind cluster. Volumes whose host path is under the root are skipped for individual extraMounts and their PV paths resolve to /mnt/{relative_path}. Volumes outside the root keep individual extraMounts as before. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>pods_in_deployment() and containers_in_pod() were hardcoded to search the "default" namespace, but deployments are created in a per-deployment namespace (laconic-{name}). This caused logs() to report "Pods not running" even when pods were healthy. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>