Skip to content

fix(dev): use kind container's gateway IP instead of NC's proxy IP#98

Open
kyteinsky wants to merge 2 commits intomainfrom
fix/dev/redeploy-host-k8s-fixes
Open

fix(dev): use kind container's gateway IP instead of NC's proxy IP#98
kyteinsky wants to merge 2 commits intomainfrom
fix/dev/redeploy-host-k8s-fixes

Conversation

@kyteinsky
Copy link
Copy Markdown
Contributor

No description provided.

Signed-off-by: Anupam Kumar <kyteinsky@gmail.com>
This skips the addition of master_default (NC's network) to the kind
container and uses the host network for pod -> NC communication.
All other communication takes place in host so it would be consistent,
and make development easier.

Signed-off-by: Anupam Kumar <kyteinsky@gmail.com>
@kyteinsky kyteinsky requested a review from oleksandr-nc as a code owner April 14, 2026 11:20
@kyteinsky
Copy link
Copy Markdown
Contributor Author

not completely sure if they make sense in all other setups but might make development easier.

Copy link
Copy Markdown
Contributor

@oleksandr-nc oleksandr-nc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Direction looks good!

A few notes:

  1. Do the NC_DOCKER_NETWORK="master_default" in the config block is now unused?
  2. Is KIND_NODE="${KIND_CLUSTER}-control-plane" defined but the new docker inspectcall hardcodesnc-exapps-control-plane? Should we use "$KIND_NODE"so the two stay in sync if someone changesKIND_CLUSTER` ?
  3. The failure branch still prints WARNING: Could not detect proxy IP. - should we change that to Could not detect kind gateway IP ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants