Implementation
With the GatewayClass and Gateway resources of your respective proxy setup, let's create the fabric resources like CA, peer and orderer.
Note that this setup is similiar to the original setup given in the docs where we are using coredns to resolve the ip addresses. The gateway api implementation also works externally by making the gateway-api service a LoadBalancer.
The first step is to get the address of the gateway which needs to be resolved for the fabric resources.
For istio:
For traefik, the ingress host is the ClusterIP of the traefik-service which is deployed earlier in the setup
#
SetupWatch out for the following configuration:
--gateway-api-hosts : The hosts that are configured to be used with gateway-api --gateway-api-name : The name of the gateway (Name of the 'Gateway' Resource created earlier) --gateway-api-namespace : The namespace where the 'Gateway' resource is deployed
#
Create CAMake sure the CA is reachable and gives a response
#
Create PeersMake sure the Peer is reachable and gives a response
#
Create Ordering NodeMake sure the Orderer is reachable and gives a response