Machines created by CAPD should use Kind's default network #3832
Labels
area/testing
Issues or PRs related to testing
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/active
Indicates that an issue or PR is actively being worked on by a contributor.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone
User Story
As a developer I would like to change the network for machines created by CAPD to simplify the development workflow.
Detailed Description
Currently, machines created by CAPD use the
bridge
network and, as of v0.8.0, Kind uses thekind
network. We should change the network to match Kind, this will remove the need to setKIND_EXPERIMENTAL_DOCKER_NETWORK
tobridge
when running local clusters or E2E tests.Anything else you would like to add:
See #3815 (comment).
/kind feature
The text was updated successfully, but these errors were encountered: