Configuration changes for Kafka Addition
To make use of Kafka for internal communication among ISD services, please follow the steps given below:
Ensure that ISD consumes events from Spinnaker via webhook and not rabbitMQ.
If auto topic creation is not enabled then create the following topics in kafka-cluster.
Topic Name
Publisher
Consumer
Type of events
echo-events-preview-saas-audit
Sapor service
Audit Service
Audit events
isd-events-isd-visibility-service
Sapor Service
Visibility service
Pipeline execution failure events
isd-events-cd-route-info
Sapor service
Visibility, audit and gate service
Apache Camel route events*
isd-events-sapor-service
Gate, visibility, audit and gate service
Sapor service
Apache Camel Route events*
isd-userLoginDetails
Gate service
Sapor service
User Login Details events
Service name
Consumer Group Name
Audit service
oes-audit-consumer-group
Visibility Service
oes-visibility-consumer-group
Gate service
oes-gate-consumer-group
Sapor service
oes-sapor-consumer-group
Do the following config changes under the message-broker section, for audit-service, oes-sapor, visibility-service and gate service in their respective ConfigMaps.
ISD supports only custom use cases of SASL auth and AWS IAM auth for Kafka.
The above configuration varies depending on the type of authentication used.
Last updated
Was this helpful?