Details
-
Enabler
-
Should have
-
None
-
True
-
Data Processing
-
-
-
Intra Program
-
1
-
1
-
0
-
REL-815 SDP 0.18.0
-
Team_NALEDI
-
Sprint 4
-
-
-
-
20.4
-
Stories Completed, Integrated, BDD Testing Passes (no errors), Outcomes Reviewed, Satisfies Acceptance Criteria, Accepted by FO
Description
The SDP Helm chart currently deploys Kafka indirectly as a dependency of the SDP QA sub-chart. This is sub-optimal for a number of reasons:
- If we need Kafka, we have to deploy the QA components too, even if they are not needed (e.g. pointing calibration integration tests);
- Components deployed directly by the SDP chart, such as the queue connector Tango devices, have to guess the name of the broker service.
To solve these problems we should move the Kafka dependency into the SDP chart, and pass the location of the broker in a consistent way to the components and sub-charts that need it.
Who?
- SDP developers.
What?
- Move Kafka dependency into the SDP Helm chart.
- Pass location of broker consistently to components and sub-charts.
Why?
- Ensure minimal deployments are possible.
- Ensures Kafka configuration is consistent throughout the SDP.
- Reduces scope for problems in the future.
Attachments
Issue Links
- Is delivered by
-
- Released