Connected Infra

It is possible to connect an external infrastructure to the Crafting system so that developers can work with that infrastructure during development. This is particularly powerful when the application being developed targets a specific infrastructure environment such as a Kubernetes cluster.

Currently, the supported infrastructure type is Kubernetes clusters.

Kubernetes Cluster

An existing Kubernetes cluster can be connected to the Crafting system to enable the full suite of Kubernetes Development Experience features, including:

• Virtual Workload Replacement by Traffic Interception: Intercept incoming traffic from a running pod in the cluster and reroute it to a workload inside the sandbox, effectively replacing the deployed service with the in-development version.
• Workload Environment and Filesystem Mirroring: Mirror the root filesystem and environment variables from a running pod into the sandbox workspace, enabling developers to run their service under the same conditions as the cluster.
• Direct In-cluster Network/DNS Access (Network Bridging): Bridge the Kubernetes cluster's internal network into the sandbox's private network, allowing direct access to pod IPs and Kubernetes Services from workspace.
• Expose Crafting Workload as Kubernetes Service: Make a workload running inside a sandbox visible as a Kubernetes Service within the connected cluster.
• Dynamic Sidecar Attachment: Dynamically attach sidecar containers to a running pod in the connected cluster.

For full details on these capabilities, see Kubernetes Development Experience.

See Also

• Kubernetes Development Experience — detailed feature reference
• Sandbox Networking — the Service Gateway and how in-cluster DNS is bridged
• Org and User — connected infrastructure is managed at the org level by admins