cnb
3191110276/cnb/kubernetes
Terraform module for deploying the Cisco Kubernetes Demo application The Cisco Kubernetes demo application consists of multiple building blocks that interact. During your setup of this application you might decide to set up one, a few, or all of the components. You can also set up different components on different clusters and connect them with each other. This documentation will first explain the high-level design of the application before diving into each sub-component and explaining the customization and adaptation options for each of them. High-level application design The application consists of six main building blocks that can be seen in the image below. !High-level application design As you can see, the application has already been created with a specific use case in mind, but all
| Name | Type | Description | Default |
|---|---|---|---|
| appd_browserapp_key | string | Key for the AppDynamics EUM application. | required |
| appd_account_name | string | Account name of the AppDynamics account. | required |
| procexternal_replicas | number | The number of replicas that should initially be deployed for the ProcurementExte | 2 |
| procedgeagg_cpu_request | string | The ProcurementEdgeAgg value for requests.cpu. | "100m" |
| extprod_cpu_limit | string | The ExtProd value for limits.cpu. | "400m" |
| payment_replicas | number | The number of replicas that should initially be deployed for the Payment compone | 2 |
| deploy_procurement | bool | Determines if the Procurement component will be deployed. | true |
| procurement_app_name | string | The name of the procurement application. | "cnb-procurement" |
| prodrequest_appd | string | The name of the ProdRequest application component. Changing this value will chan | "ProdRequest" |
| orderprocessing_cpu_request | string | The OrderProcessing value for requests.cpu. | "20m" |
| orderfile_cpu_limit | string | The OrderFile value for limits.cpu. | "50m" |
| procportal_cpu_limit | string | The ProcurementPortal value for limits.cpu. | "200m" |
| procedge_memory_limit | string | The ProcurementEdge value for limits.memory. | "900Mi" |
| notification_cpu_request | string | The Notification value for requests.cpu. | "20m" |
| payment_memory_limit | string | The Payment value for limits.memory. | "256Mi" |
| notification_memory_limit | string | The Notification value for limits.memory. | "280Mi" |
| orderfile_memory_limit | string | The OrderFile value for limits.memory. | "32Mi" |
| trafficgen_min_random_delay | number | 0 | |
| trafficgen_namespace | string | Namespace used for deploying the TrafficGen application component. This namespac | "trafficgen" |
| fulfilment_name | string | The name of the Fulfilment application component. Changing this value will chang | "fulfilment" |
| extprod_memory_request | string | The ExtProd value for requests.memory. | "128Mi" |
| extprod_job_max_delay | string | The maximum processing time requests to ExtProd. | "360" |
| … and 10 more inputs | |||