Hello Haidar,
Thanks for sharing your doubts with the community.
Could you please provide the following information?
Please note that this kind of deployment is intended for Cloud environments. In case you are deploying it in an On-Prem environment, you need to take into account some considerations.
For example, On-Prem deployments do not use Load Balancer. Instead, you need to use Nodeport for networking.
Also, you need to define the persistent volumes manually, as they are not created automatically.
I hope this information would be useful.
Best regards.
Hello Haidar,
Thanks for your reply.
As previously mentioned, deploying Wazuh in an On-Prem environment with Kubernetes, needs some prerequisites, such as the Persistent Volumes creation and the networking configuration. You can share with us the events for every pod, in order we can check for errors.
In addition to this, you can use the following Github repository, which explains the deployment of Wazuh in an On-Premise environment with Kubernetes. Take into account that you need to use this repo from scratch, not applying it with the current installation:
Looking forward to hearing from you.
Best regards.
Hello Haidar,
Thanks for your answer.
It would be important to check the reason why the indexer container is not being created. To check this, you can run the following commands:
# kubectl -n wazuh describe pod <pod-name> # kubectl get eventsCheck this and let us know the output for these commands.
Best regards.