SSCS Container
Summary
Container exposes an interface by which RCKMS Output from a control and test variant of the RCKMS Shared Service (SS) can be ingested for performing a diff against, for stakeholders to validate and certify new releases of the SS workload.
Attributes
Type
Primary
Name
ss-comparison-service
Image
ss-comparison-service
Image Pull Policy
Always
Command
Arguments
Port
8080
Security Context
Allow Privilege Escalation:
false
Endpoints
External-to-Cluster
This container does have external-to-cluster exposed endpoints.
Submitting Shared Service Output for Comparison
POST /ss-comparison-service/v1/comparison-tests/{test-id}/comparison-sets/{set-id}/output/{source-id}
The primary entrypoint for the SSCS. Path parameters specify the comparison record metadata, whereas the request body contains a JSON payload with the rckmsOutput and other necessary data points from the Shared Service invocation.
Path Parameters
test-id*
String
Should be set to a valid ComparisonTest ID that exists in the comparison_test collection in the Document store database.
set-id*
String
The unique ID that identifies a set of output files. This value must be the same for the submission of both the control and variant outputs.
source-id*
String
A unique identifier for the source of the file, i.e. for the control or variant output.
For example, when submitting the output for the control version of the Shared Service, it might be RCKMS_OLD, and for the variant version it might be RCKMS_NEW.
Note that whatever value is used for the control version, must also be configured in the comparison_test document in mongo corresponding with the test ID being used.
Headers
Content-Type*
String
Should be set to application/json.
Request Body
serviceStatus*
Integer
HTTP status code from the Shared Service response.
serviceOutput*
String
rckmsOutput XML document response from the Shared Service.
serviceResponseTime*
Integer
The elapsed time to get the Shared Service response, in milliseconds.
Internal
Liveness Probe
GET /manage/health
Refer to the Kubernetes Documentation for more information on probes.
Readiness Probe
GET /manage/health
Refer to the Kubernetes Documentation for more information on probes.
Environment Variables
All environment variables, unless otherwise indicated, are considered required.
General Variables
Application Configuration
Document Database Connectivity
Probes
Liveness
Mode
HTTP (GET)
Arguments
Path:
/manage/healthPort:
8080(must match container port)
Timings
Initial Delay of
60sPeriod of
30sTimeout of
5s
Thresholds
1Successes3Failures
Readiness
Mode
HTTP (GET)
Arguments
Path:
/manage/healthPort:
8080(must match container port)
Timings
Initial Delay of
15sPeriod of
15sTimeout of
5s
Thresholds
1Successes3Failures
Startup
Resources
250
1024
N/A
500
1536
N/A
Technology Stack
Container is a Java Spring Boot web application.
Volume Mounts
java-diag
/hln/diagnostics
Workload Identity
Container requires writable connectivity to the Document store database.
Code Owners
Last updated