bcgov / bcgov/SIMS

Openshift: Ensure TLS communication between application components

Open
#1,881 0 comments 0 reactions 0 assignees View on GitHub
Devops
Dominant language
TypeScript
Stars
29
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Application components may communicate sensitive data that should be protected. Unless you consider the underlying OpenShift network to be secure, you may want to leverage TLS to protect the traffic between the application components. Consider leveraging OpenShift Service Mesh to offload the TLS management from the application.

**Acceptance Criteria**
Check if the application needs TLS connection or not if yes, enable the ingress controller to enable them.
https://docs.openshift.com/container-platform/4.7/security/tls-security-profiles.html

@guru-aot to look if other BC gov projects are implementing the same.

Contributor guide

No contributing guide indexed for this repository

Research direction

No repository file, test, or entry point is identified. Start with the linked OpenShift TLS security profiles documentation, then inspect the application's ingress configuration to determine whether TLS is required. Done means recording that decision and enabling ingress TLS when required, with component communication protected.

Written by the indexing model from the issue text.

Assessment

Domain
infrastructure, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.