You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, clustering OpenCTI platform is one of the best practices suggested by Filigran. This helps in number of ways, as it segregates pods for users (Frontend Cluster) and pods for data ingestion (Ingestion Cluster). More details available in Filigran documentation here : https://docs.opencti.io/latest/deployment/clustering/
This feature request would focus only on OpenCTI platform component. All other dependencies are taken care by HA options provided by sub-charts.
If this feature request is reviewed and accepted, I'm happy to send PR for this ASAP.
Describe the solution you'd like
Add labels to pod to distinguish between frontend and ingestion. Create services accordingly.
Describe alternatives you've considered
Addition of new deployment and associated services. However, this would result in lot of code duplication and lead to maintainability issues.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Not exactly a pbm.
However, clustering OpenCTI platform is one of the best practices suggested by Filigran. This helps in number of ways, as it segregates pods for users (Frontend Cluster) and pods for data ingestion (Ingestion Cluster). More details available in Filigran documentation here : https://docs.opencti.io/latest/deployment/clustering/
This feature request would focus only on OpenCTI platform component. All other dependencies are taken care by HA options provided by sub-charts.
If this feature request is reviewed and accepted, I'm happy to send PR for this ASAP.
Describe the solution you'd like
Add labels to pod to distinguish between frontend and ingestion. Create services accordingly.
Describe alternatives you've considered
Addition of new deployment and associated services. However, this would result in lot of code duplication and lead to maintainability issues.
Additional context
No response
The text was updated successfully, but these errors were encountered: