CAMEL Gateway Pod Configuration

CAMEL Gateway pod property values are auto-generated based on the configuration set in the Helm values file.

To enable this configuration CAMEL Gateway must be enabled in the Helm values file as follows:
camel-gateway:
  enabled: true
This auto-generates the following create_config.info configuration and auto-generates values for the CAMEL Gateway pod properties based on CAMEL Gateway values configured in Helm:
Camel Gateway: Will CAMEL gateway be used in cloud native mode (on separate pods from the processing pods) (y/n)?y
CAMEL Gateway and Engine Pod Properties describes properties in create_config.info for deploying cloud native CAMEL Gateway on separate pods to MATRIXX Engine processing pods.
Table 1. CAMEL Gateway and Engine Pod Properties
Property Description
Use Cloud Native Mode Defaults to n. In default mode, CAMEL Gateway runs on the processing servers and the answers to the following CAMEL Gateway server questions are not set.

Answer y to deploy CAMEL Gateway on separate pods in a cloud native environment.

create_config.info question: Camel Gateway: Will CAMEL gateway be used in cloud native mode (on separate pods from the processing pods) (y/n)?

If you answer y, the following additional questions are asked.
Number of CAMEL Gateway Pods Specifies the total number of separate CAMEL Gateway pods to deploy. Include all CAMEL Gateway pods on all sub-domains. Example value: 2

create_config.info question: Camel Gateway: How many Camel gateways do you have?
MDC Access Address List A comma separated list of the MDC access addresses on processing pods. Example values: proc-m3ua-s1e1-1.matrixx.svc.cluster.local,proc-m3ua-s1e2-1.matrixx.svc.cluster.local

create_config.info question: Camel Gateway: What are the MDC access addresses?
MDC HTTP2 Access Port Specifies the MDC HTTP2 access port. Default value: 24062

create_config.info question: Camel Gateway: What is the MDC access HTTP2 port?
CAMEL Gateway HTTP2 Port Specifies the CAMEL Gateway HTTP2 port. Default value: 7071

create_config.info question: Camel Gateway: What is the Camel Gateway HTTP2 port?
Use Secured HTTP2 BetweenCAMEL Gateway Clients and the Engine Specifies whether secured HTTP2 is used between clients on CAMEL Gateway and the engine. Default value: y.

create_config.info question: Camel Gateway: Will secured HTTP2 be used between clients on CAMEL Gateway and the engine (y/n)?
Secured HTTP2 Client Certificate Location Specifies the location of the CAMEL Gateway HTTP2 client certificate file if secured HTTP2 is used. Default value: cert/client.cer

create_config.info question: Camel Gateway: What is the location of the CAMEL_Gateway HTTP2 client certificate file?

Note: You must ensure that certificate and key files are placed in correct locations in the engine and CAMEL Gateway pods.
Secured HTTP2 Client Key Location Specifies the location of the CAMEL Gateway HTTP2 client key file if secured HTTP2 is used. Default value: cert/client.key

create_config.info question: Camel Gateway: What is the location of the CAMEL_Gateway HTTP2 client key file?

Note: You must ensure that certificate and key files are placed in correct locations in the engine and CAMEL Gateway pods.
Use Secured HTTP2 Between Engine Clients and CAMEL Gateway Server Specifies whether secured HTTP2 is used between clients on the engine and a server in CAMEL Gateway. Default value: y.

create_config.info question: Will secured HTTP2 be used between clients on the engine and a server in CAMEL Gateway (y/n)?
Secured HTTP2 Server Certificate Location Specifies the location of the CAMEL Gateway HTTP2 server certificate file if secured HTTP2 is used. Default value: cert/server2.cer

create_config.info question: What is the location of the CAMEL_Gateway HTTP2 server certificate file?

Note: You must ensure that certificate and key files are placed in correct locations in the engine and CAMEL Gateway pods.
Secured HTTP2 Server Key Location Specifies the location of the CAMEL Gateway HTTP2 server key file if secured HTTP2 is used. Default value: cert/server2.key

create_config.info question: What is the location of the CAMEL_Gateway HTTP2 server key file?

Note: You must ensure that certificate and key files are placed in correct locations in the engine and CAMEL Gateway pods.
Secured HTTP2 Engine Client Certificate Location Specifies the location of the engine HTTP2 client certificate file if secured HTTP2 is used. Default value: cert/client2.cer. This property is used for transporter task client connections.

create_config.info question: What is the location of the engine HTTP2 client certificate file?

Note: You must ensure that certificate and key files are placed in correct locations in the engine and CAMEL Gateway pods.
Secured HTTP2 Engine Client Key Location Specifies the location of the engine HTTP2 client key file if secured HTTP2 is used. Default value: cert/client2.key. This property is used for transporter task client connections.

create_config.info question: What is the location of the engine_Gateway HTTP2 client key file?

Note: You must ensure that certificate and key files are placed in correct locations in the engine and CAMEL Gateway pods.
M3UA IP Addresses Lists the M3UA IP addresses for the CAMEL Gateway pod. This question is asked per CAMEL Gateway pod. Example value: cgw-ag1-1.cgw-ag1.matrixx.svc.cluster.local.

create_config.info question: Camel Gateway:Instance 1: What are the M3UA IP addresses?
Internal M3UA IP Addresses Lists the internal M3UA IP addresses for the CAMEL Gateway pod. This question is asked per CAMEL Gateway pod. Example value: cgw-ag1-1

create_config.info question: Camel Gateway:Instance 1: What are the internal M3UA IP addresses?
M3UA Point Code Specifies the M3UA point code. This question is asked per CAMEL Gateway pod. Example value: 402

create_config.info question: Camel Gateway:Instance 1: What is the M3UA point-code?
Sub-Domain ID Specifies the ID of the sub-domain the CAMEL Gateway pod connects to. This question is asked per CAMEL Gateway pod. Example value: 1

create_config.info question: Camel Gateway:Instance 1: What is the sub-domain Id?