The Complete Guide on Hyperledger Fabric v2.x on Kubernetes

What you'll learn
Design Hyperledger Fabric Network
Working with Kubernetes
Hyperledger Fabric on Kubernetes
Requirements
Basics of Hyperledger Fabric
Basic understanding of kubernetes
Description
In this course, you will learn to design and deploy Hyperledger Fabric applications on Kubernetes. This course is specifically designed for those seeking to learn hyperledger fabric deployment on Kubernetes. By the end of the course, you will be able to design, develop and deploy your hyperledger fabric network on any cloud, since we have used the cloud-agnostic approach. This course is completely hands-on and we will be focusing more on the practical approach rather than the theoretical.What you will learn from this courseBy the end of the course, you will be able to design, develop and deploy your hyperledger fabric application on Kubernetes. You will learn the following thingsCreating Kubernetes clusterSetting up NFS ServerStarting up Fabric CA ServerGenerating certificates for peers and orderersCreating artifacts like genesis block, channel transaction, and anchor peersCreating application channel Joining application channelConfiguring peers to use external chaincode builderStarting up peer nodesPackaging chaincode as per external chaincode builder settingsStarting up chaincode as service in KubernetesApproving chaincodeCommitting chaincodeInvoking and querying transactions.Setting up REST API ServerSetting up Frontend Application build over AngularHyperledger Explorer IntegrationEnabling Hyperledger Fabric Monitoring using Prometheus and GrafanaSetting up an ingress controller and domain configuration.Enabling SSL on Kubernetes with the help of cert-manager and Let's encryptVarious Ways for Hyperledger Fabric DeploymentAs Hyperledger Fabric components are deployed as containers, everything works fine when running in the localhost. When they are running in different hosts, we need to find a way to make these containers talk to one another.Static IP By specifying the host IP where a container is running, containers can communicate with each other. Those host IPs are specified using extra_hosts in docker-compose files, and after a container is running, these entries are seen in, etc/hosts. The downside is that things are statically configured, and there are challenges when one needs to add or change the configuration.Docker Swarm Docker Swarm is a container orchestration tool natively in the Docker environment. In a nutshell, It provides an overlay network for containers across multiple hosts. Those containers on this overlay network can communicate to one another as if they were on a large host. Obviously, the good side is that the original configuration can be used with minimal modification, and no static information such as IP is coded in the configuration.Kubernetes (k8s) K8s by far is the most popular container orchestration tool. The mechanism is similar to Docker Swarm. The implementation of this approach is much more challenging than the previous two mechanisms but this approach is much more scalable and recommended by the Hyperledger Fabric team.
Who this course is for
Blockchain Developer
Blockchain Architect
Devops Enginner
Blockchain Consultants
Homepage

https://www.udemy.com/course/hyperledger-fabric-on-kubernetes-complete-guide/