BESClient Installation on Kubernetes Cluster or Worker Nodes

We have a query regarding the appropriate method of installing the BESClient in a Kubernetes environment. Since I do not have extensive experience with Kubernetes, I would like to confirm:

  • Does HCL recommend installing the BESClient on Kubernetes worker nodes (host operating systems) or inside individual containers/pods?
  • Is there any official documentation or guidance available from HCL specifically related to deploying and managing BESClient in Kubernetes clusters?

I searched the available documentation but was unable to find anything specific to this use case, hence reaching out to you for clarification and recommendations.

Any guidance, best practices, or official documentation links would be greatly appreciated.

Installing on the host is supported.

Docker integration

1 Like

I’d like further suggestions on the following. Is there any supported way to install the BESClient on Bottlerocket AMI-backed nodes, or is it correct that the BESClient cannot be installed in this environment?

Currently not possible to install traditional packages on Bottlerocket AMIs, since the OS runs all software as containers and does not include a package manager.

What exactly would your use-case be for running BESClient inside a container, if I may ask? It wouldn’t be useful for much patching or configuration management inside the container itself as far as I can tell; and our patch content offerings may not be as useful either (given that something like “Patches for RHEL 8” isn’t going to work with a UBI image, for example), so… I’m really curious to know what the value is there.

These are not containers; they are nodes, and the description (shared by our AWS team) provided applies specifically to nodes.

I wanted to check if anyone has a similar environment and whether they have successfully installed the BESClient on such nodes.

I do understand no use for containers but if these are nodes besclient can be installed some way?

Please ignore my earlier comment, it was due to a misunderstanding on my side. After your message, I double-checked with the team and now it’s clear that these are containers only. I appreciate the clarification, as I was lacking some understanding around AWS container concepts.

1 Like