# Channels

Similar to Hyperledger Fabric, channel serve as private communication “subnets” connecting two or more designated network participants to facilitate confidential transactions. A channel is composed of member organizations, anchor peers for each member, a shared ledger, chaincode applications, and ordering service nodes. In Angus, we differentiate two types of channels:

Integration Channels: an internal communication channel used for managing the integration between Angus and other HLF or system components.
Application Channels: an external communication channel used for housing the customers business logics within Angus.

# Integration Channels

apiVersion: integrator.angusnext.io/v1
kind: AngusIntegrationChannel
metadata:
  name: default
  namespace: space02
  annotations:
    angusnext.io/networkConfig: "default"
    angusnext.io/channelConfig: "v2.5"
spec:
  orderer: orderer
  consortium_members:

Annotation name	Description
angusnext.io/networkConfig	Currently only: default
angusnext.io/channelconfig	Currently only: default

# Properties

key	Description
orderer	Name of your orderer cluster (AngusOrderer)
consortium_members	Default this is empty! AngusServer will be add content for this field, when you add an org to the channel

# Application Channels

apiVersion: integrator.angusnext.io/v1
kind: AngusCustomerChannel
metadata:
  name: default
  namespace: space01
  annotations:
    angusnext.io/networkConfig: 'default'
    angusnext.io/channelconfig: 'default'
spec:
  orderer_fqdn: orderer0.space02.svc.cluster.local:7050
  orderer_catls_secret_name: integrationcatls
  peers:
    - peer01

Annotation name	Description
angusnext.io/networkConfig	Currently only: default
angusnext.io/channelconfig	Currently only: default

# Properties

key	Description
orderer_fqdn	Orderer cluster FQDN address (for multi-cluster usage)
orderer_catls_secret_name	The orderer certification name in the customer ns
peers	Which peer will be part of this channel from the customer channel