I'm getting ready to release some Dockerized ElasticSearch/Kibana nodes. Given that Marvel basic licenses are now free, I'd like to bake the agent plugin into my ElasticSearch images and the UI app into my Kibana images.
The important part here is that I am not calling the "license" plugin as a part of my Dockerfiles - instead this will be called the first time the image instance is spun up. By the user running the container. To be explicit, here's what I'm doing:
- My ElasticSearch Dockerfile calls plugin install marvel-agent
- My Kibana Dockerfile calls plugin --install elasticsearch/marvel/latest
- The script in ENTRYPOINT for my ElasticSearch Dockerfile calls plugin install license the first time the person running the docker image spins it up. Once, and only once.
The nodes are intended to be run for specific short-lived ad hoc tasks, generally less than 30 days. In the event that users need to run the containers longer, I've left cURL on the images so that they can install a basic license - these images aren't for production usage - via something like a docker exec across the cluster. Either way, obtaining and managing licenses is left to the user of the image.
I've looked over all the licensing that I could find, I've searched the forums, I've read https://www.elastic.co/guide/en/marvel/current/license-management.html, and I've hopped on IRC. So far everything seems kosher given that I am not distributing licenses. Further, given what I've seen from Elastic itself in terms of reaching out about customer success, and advocation, leads me to believe that this is logically consistent. Still, I'd like to Do The Right Thing (tm) and get an official answer from Elastic.
I'm asking this in the forums (as opposed to email) so that it can act as temporary documentation for anyone else that is curious about this question. I figure that'll help until you folks can update your license management page, as well as anything else mentioning Marvel licensing, heh.
Thanks in advance,