Deploying CDP Flip
This section provides detailed instructions on how to deploy CDP Flip using the Devtron in the AWS.
Prerequisites
Make sure to create cdp-flip secret in the AWS Secret Manager before deploying CDP Flip.
To create CDP Flip secret in the AWS secret Manager, follow the steps below:
- Create a cdp-flip secret sample key and value, and update the actual values as shown
below.
{ "CUSTOMIZATION_AERO_CLUSTER": "", "DB_USERNAME": "", "DB_PASSWORD": "", "DB_URL": "", "KafkaConsumerConfig": "", "KAFKA_CONSUMER_PREFIX": "flip", "KAFKA_TOPIC_LIST": "dmp_rt_segments" } - Create separate service account cdp-dev-app-sa with appropriate roles and permissions, and update ConfigMaps data with actual values.
- Create required Kafka topics before deployment.
Deploy CDP Flip
- Navigate to the Devtron Chart Store, and select the cdp-flip chart to
deploy.
- Now, configure and deploy the cdp-flip charts.
- In the YAML section, update the ConfigMap using the below details and deploy the chart.
AERO_CUSTOMIZATION_NS: "<AERO_CUSTOMIZATION_NAMESPACE>" AERO_CUSTOMIZATION_TIMEOUT: "<AERO_CUSTOMIZATION_TIMEOUT>" AERO_RTS_CACHE_EXPIRY: "<AERO_RTS_CACHE_EXPIRY>" MYSQL_DBDRIVER: "<MYSQL_DB_DRIVER>" MYSQL_REFRESH_DBREFRESHTIMEMIN: "<MYSQL_REFRESH_INTERVAL_MIN>" MT_PROPERTIES_FLIP_EXECUTOR_SERVICE_MIN_THREADS: "<FLIP_EXECUTOR_MIN_THREADS>" MT_PROPERTIES_FLIP_EXECUTOR_SERVICE_MAX_THREADS: "<FLIP_EXECUTOR_MAX_THREADS>" MT_PROPERTIES_FLIP_EXECUTOR_SERVICE_THREAD_TTL: "<FLIP_EXECUTOR_THREAD_TTL>" MT_PROPERTIES_FLIP_EXECUTOR_SERVICE_QUEUSE_SIZE: "<FLIP_EXECUTOR_QUEUE_SIZE>" KAFKA_CONSUMER_GROUP_ID: "<KAFKA_CONSUMER_GROUP_ID>" KAFKA_CONSUMER_GROUP_PREFIX: "<KAFKA_CONSUMER_GROUP_PREFIX>" KAFKA_REBALANCE_MAX_RETRIES: "<KAFKA_REBALANCE_MAX_RETRIES>" KAFKA_CONSUMER_TOPIC_LIST: "<KAFKA_CONSUMER_TOPIC_LIST>" KAFKA_CONSUMER_TOPIC_CONSUMERS: "<KAFKA_CONSUMER_TOPIC_CONSUMERS>" KAFKA_CONSUMER_TOPIC_CONSUMER_BATCH_SIZE: "<KAFKA_CONSUMER_BATCH_SIZE>" KAFKA_CONSUMER_TOPIC_CONSUMER_DEFAULT_BATCH_TIMEOUT_MS: "<KAFKA_CONSUMER_BATCH_TIMEOUT_MS>" KAFKA_CONSUMER_TOPIC_CONSUMER_DEFAULT_BATCH_TIMEOUT_TRIGGER: "<KAFKA_CONSUMER_BATCH_TIMEOUT_TRIGGER>" KAFKA_CONSUMER_EVENT_MAX_EVENT_BATACH_LAG: "<KAFKA_MAX_EVENT_BATCH_LAG>" KAFKA_CONSUMER_EVENT_SR_MAX_EVENT_BATCH_LAG: "<KAFKA_SR_MAX_EVENT_BATCH_LAG>" KAFKA_CONSUMER_EVENT_MAX_BATCH_EXECUTE_RETRIES: "<KAFKA_MAX_BATCH_EXECUTE_RETRIES>" KAFKA_PRODUCER_METADATA_BROKER_LIST: "<KAFKA_BROKER_LIST>" KAFKA_PRODUCER_SERIALIZER_CLASS: "<KAFKA_PRODUCER_SERIALIZER_CLASS>" KAFKA_PRODUCER_ID: "<KAFKA_PRODUCER_ID>" KAFKA_PRODUCER_REQUIRED_ACKS: "<KAFKA_REQUIRED_ACKS>" KAFKA_PRODUCER_REQUIRED_TIMEOUT: "<KAFKA_REQUIRED_TIMEOUT>" KAFKA_PRODUCER_TYPE: "<KAFKA_PRODUCER_TYPE>" KAFKA_PRODUCER_COMPRESSION_CODEC: "<KAFKA_COMPRESSION_CODEC>" KAFKA_PRODUCER_MAX_RETRIES: "<KAFKA_PRODUCER_MAX_RETRIES>" KAFKA_PRODUCER_RETRY_BACKOFF: "<KAFKA_PRODUCER_RETRY_BACKOFF>" KAFKA_PRODUCER_NC_EVENT_TYPE: "<KAFKA_NC_EVENT_TYPE>" KAFKA_PRODUCER_HOSTNAME: "<KAFKA_PRODUCER_HOSTNAME>" KAFKA_PRODUCER_POOL_SIZE: "<KAFKA_PRODUCER_POOL_SIZE>" KAFKA_PRODUCER_NOTIFTOPIC: "<KAFKA_PRODUCER_NOTIFICATION_TOPIC>" LOG_TSDB_METRIC_LOGGING_FREQUENCY_MS: "<TSDB_METRIC_LOG_FREQUENCY_MS>" LOG_TSDB_MAX_WAIT_FOR_CONNECTION_REESTABLISH: "<TSDB_MAX_WAIT_RECONNECT>" LOG_TSDB_SERVER_ADDRESS: "<TSDB_SERVER_ADDRESS>" LOG_TSDB_SERVER_PORT: "<TSDB_SERVER_PORT>" LOG_TSDB_HOSTNAME: "<TSDB_HOSTNAME>" LOG_GANGLIA_GMOND_COLLECTORS: "<GANGLIA_GMOND_COLLECTORS>" LOG_GANGLIA_GMOND_PORT: "<GANGLIA_GMOND_PORT>" LOG_GANGLIA_HOSTNAME_OVERRIDE: "<GANGLIA_HOSTNAME_OVERRIDE>" LOG_GANGLIA_METRIC_PREFIX: "<GANGLIA_METRIC_PREFIX>" AERO_KEYS_ORDER: "<AERO_KEYS_ORDER>" AERO_METADATA_ITEMS: "<AERO_METADATA_ITEMS>" APP_LOG_LEVEL: "<APP_LOG_LEVEL>" KAFKA_BATCH_SIZE: "<KAFKA_BATCH_SIZE>" MAX_EVENT_BATCH_LAG: "<MAX_EVENT_BATCH_LAG>" BATCH_TIMEOUT_MS: "<BATCH_TIMEOUT_MS>" BATCH_TIMEOUT_TRIGGER: "<BATCH_TIMEOUT_TRIGGER>" KAFKA_TOPIC_CONSUMERS: "<KAFKA_TOPIC_CONSUMERS>" FLATTEN_ARRAY_IN_MACRO: "<BOOLEAN>"
- On successful deployment, validate the deployment as shown below.