PREV: Setup <==> NEXT: Deploy a Fabric Network
With cloud-native Fabric, all the components can run directly on your development workstation. In this exercise, you will configure:
-
A local kind cluster, running Kubernetes in Docker.
-
A local Ingress controller, routing traffic into the cluster at the
*.localho.stvirtual DNS domain. -
A local Container Registry, allowing you to upload chaincode Docker images to the cluster.
just check-setup
- Set the cluster ingress domain and target k8s namespace. The
localho.stdomain is a public DNS wildcard resolver mapping*.localho.stto 127.0.0.1.
export WORKSHOP_INGRESS_DOMAIN=localho.st
export WORKSHOP_NAMESPACE=test-network
- Create a kind cluster, Nginx ingress, and local container registry:
just kind
- Open a new terminal window and observe the target namespace:
# KIND will set the current kubectl context in ~/.kube/config
kubectl cluster-info
k9s -n test-network
- Run KIND on a multipass VM on your local system
- Run KIND on an EC2 instance at AWS
- Run the workshop on an IKS or EKS or DOKS Cloud Kubernetes cluster.
- Run the workshop on an AWS VM, using your AWS account and an EC2 #cloud-config.