RRS

RCKMS Reports Service

Overview

The objective of the RCKMS Reports Service (RRS) is to isolate the responsibility of generating reports and report artifacts by RCKMS users in CAT from the Middle Tier Service (MTS), to deliver the following benefits:

• As an isolated workload, resources allocated to MTS will not be used for generating reports, which in some instances, can be a resource intensive and lengthy process.

• As an isolated workload, updates to data fetched or optimizations to existing reports or the addition of new report options can be implemented without requiring an update to MTS.

Service Mesh

Interactions

The RCKMS Reports Service (RRS) is invoked by CAT, and communicates with the Middle Tier Service (MTS) for performing session validation.

In addition, RRS utilizes Cloud Storage Buckets (which, due to namespacing of directories utilized, can be shared with the Knowledge Module storage bucket) to store artifacts of reports that require extensive time to be generated.

Placement

Workload should be deployed to the authoring environment.

Pod Specification

Attributes

Parameter	Value
Name	rckms-reports-service
Restart Policy	Always
Termination Grace Period (seconds)	30
Tolerations (optional for AIMS environments)	NoSchedule: k8s.rckms.dev/preemptible=true

Containers

RRS Container

The Cloud SQL Proxy sidecar container notated below is only applicable for HLN's internal environments, and should not be deployed in AIMS environments.

🪢Cloud SQL Proxy

Volumes

Pod does not require any Volume resource requirements.

Workload Definition

Production Environments

Provision workload as a Kubernetes Deployment resource, with RollingUpdate strategy and the following attributes for nominal operation state:

Parameter	Value
Replicas	1
Minimum Ready Seconds	10
Maximum Surge	1
Maximum Unavailable	0

Non-Production Environments

Workload Identity

A Kubernetes Service Account named rckms-reports-service should be associated with this workload, for bindings specified in containers.