Automate mTLS communication with GoPay partners with Istio Vijay Dhama, Gojek Zufar Dhiyaulhaq, Gojek Agenda ● GoPay & Istio ● Before mutual TLS ● Implementing mutual TLS ○ Centralized Certificate ● Central certificate management manage our certificate lifecycle for HTTPS and mutual TLS communication. ● Renew & sync to our Kubernetes cluster, also support syncing to VM with an agent installed automatically to mutual TLS by sidecar. Challenge & Future Works Challenge ● Client egress communication sometime got 503 error (Istio #26990). This is fixed by adding retry mechanism in the Virtual

via peer node P1. A1, P1 and O4 are all joined to channel C1, i.e. they can all make use of the communication facilities provided by that channel. In the next stage of network development, we can see that connect to both peer node P1 and orderer node O4. Again, see how channels are central to the communication between network and organization components. Just like peers and orderers, a client application anchor peers defined for it, and an anchor peer can help with many different cross-organization communication scenarios. Note that a peer can be a committing peer, endorsing peer, leader peer and anchor

via peer node P1. A1, P1 and O4 are all joined to channel C1, i.e. they can all make use of the communication facilities provided by that channel. In the next stage of network development, we can see that connect to both peer node P1 and orderer node O4. Again, see how channels are central to the communication between network and organization components. Just like peers and orderers, a client application anchor peers defined for it, and an anchor peer can help with many different cross-organization communication scenarios. Note that a peer can be a committing peer, endorsing peer, leader peer and anchor

via peer node P1. A1, P1 and O4 are all joined to channel C1, i.e. they can all make use of the communication facilities provided by that channel. In the next stage of network development, we can see that connect to both peer node P1 and orderer node O4. Again, see how channels are central to the communication between network and organization components. Just like peers and orderers, a client application anchor peers defined for it, and an anchor peer can help with many different cross-organization communication scenarios. Note that a peer can be a committing peer, endorsing peer, leader peer and anchor

via peer node P1. A1, P1 and O4 are all joined to channel C1, i.e. they can all make use of the communication facilities provided by that channel. In the next stage of network development, we can see that connect to both peer node P1 and orderer node O4. Again, see how channels are central to the communication between network and organization components. Just like peers and orderers, a client application anchor peers defined for it, and an anchor peer can help with many different cross-organization communication scenarios. Note that a peer can be a committing peer, endorsing peer, leader peer and anchor

via peer node P1. A1, P1 and O4 are all joined to channel C1, i.e. they can all make use of the communication facilities provided by that channel. In the next stage of network development, we can see that connect to both peer node P1 and orderer node O4. Again, see how channels are central to the communication between network and organization components. Just like peers and orderers, a client application anchor peers defined for it, and an anchor peer can help with many different cross-organization communication scenarios. Note that a peer can be a committing peer, endorsing peer, leader peer and anchor

via peer node P1. A1, P1 and O4 are all joined to channel C1, i.e. they can all make use of the communication facilities provided by that channel. In the next stage of network development, we can see that connect to both peer node P1 and orderer node O4. Again, see how channels are central to the communication between network and organization components. Just like peers and orderers, a client application anchor peers defined for it, and an anchor peer can help with many different cross-organization communication scenarios. Note that a peer can be a committing peer, endorsing peer, leader peer and anchor

via peer node P1. A1, P1 and O4 are all joined to channel C1, i.e. they can all make use of the communication facilities provided by that channel. In the next stage of network development, we can see that connect to both peer node P1 and orderer node O4. Again, see how channels are central to the communication between network and organization components. Just like peers and orderers, a client application anchor peers defined for it, and an anchor peer can help with many different cross-organization communication scenarios. Note that a peer can be a committing peer, endorsing peer, leader peer and anchor

via peer node P1. A1, P1 and O4 are all joined to channel C1, i.e. they can all make use of the communication facilities provided by that channel. In the next stage of network development, we can see that connect to both peer node P1 and orderer node O4. Again, see how channels are central to the communication between network and organization components. Just like peers and orderers, a client application anchor peers defined for it, and an anchor peer can help with many different cross-organization communication scenarios. Note that a peer can be a committing peer, endorsing peer, leader peer and anchor

via peer node P1. A1, P1 and O4 are all joined to channel C1, i.e. they can all make use of the communication facilities provided by that channel. In the next stage of network development, we can see that connect to both peer node P1 and orderer node O4. Again, see how channels are central to the communication between network and organization components. Just like peers and orderers, a client application anchor peers defined for it, and an anchor peer can help with many different cross-organization communication scenarios. Note that a peer can be a committing peer, endorsing peer, leader peer and anchor