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
Hello! First of all, I'd like to thank you for maintaining this project.
That said, the current version expects dependencies (elasticsearch, redis, ...) are deployed via the OpenCTI Helm chart for the ready checker to work well, as it makes use of addresses that would be set if the dependecies have been deployed as subcharts of the OpenCTI chart.
Will you be okay with that contribution?
Thank you in advance,
Raouf
Describe the solution you'd like
I propose to modify to the values and Platform deployment manifest to add the possibility of checking services that are deployed in other ways (for example in case of using Cloud-based managed services).
I plan to add a field called address in the items of the services list:
services:
raoufkh
changed the title
[repo] Readychecker when some services are out of the Kubernetes cluster
[repo] Readychecker doesn' work when some services are out of the Kubernetes cluster
Jan 2, 2025
raoufkh
changed the title
[repo] Readychecker doesn' work when some services are out of the Kubernetes cluster
[repo] Readychecker doesn't work when some services are out of the Kubernetes cluster
Jan 2, 2025
Is your feature request related to a problem?
Hello! First of all, I'd like to thank you for maintaining this project.
That said, the current version expects dependencies (elasticsearch, redis, ...) are deployed via the OpenCTI Helm chart for the ready checker to work well, as it makes use of addresses that would be set if the dependecies have been deployed as subcharts of the OpenCTI chart.
Will you be okay with that contribution?
Thank you in advance,
Raouf
Describe the solution you'd like
I propose to modify to the values and Platform deployment manifest to add the possibility of checking services that are deployed in other ways (for example in case of using Cloud-based managed services).
I plan to add a field called
address
in the items of the services list:services:
address: elasticsearchip
port: 9200
port: 9000
port: 5672
port: 6379
The URL to use for checking for readiness wille be
**address**
if this field is specified, otherwisechart-fullname-**name**
.Describe alternatives you've considered
I think the proposed solution is good as it is simple and it doesn't make significant changes to the values.
Additional context
Would you be okay with such a contribution? With your agreement I will try to make it available ASAP.
The text was updated successfully, but these errors were encountered: