DaveCTurner
commented
3 years ago It's unclear what warning you are talking about: every deprecation warning emitted by Elasticsearch v7.15.0 starts with Warning: 299 Elasticsearch-7.15.0-79d65f6e357953a5b3cbcc5e2c7c21073d89aa29. I'm going to guess you mean the message with content Elasticsearch built-in security features are not enabled. Without authentication, your cluster could be accessible to anyone. See https://www.elastic.co/guide/en/elasticsearch/reference/7.15/security-minimal-setup.html to enable security. If so you can suppress this warning by configuring security as per the linked docs, or by explicitly indicating to Elasticsearch that you do not want to use the built-in security features by setting xpack.security.enabled: false.
elasticmachine
turnUpTheChill
lockewritesdocs
bytebilly
renzedj
NetwarSystem
Having recently run apt upgrade on an Ubuntu 20.04 box I see that I've now got Elasticsearch 7.15.0 and it comes with a spectacular misfeature - an endless cascade of Warning: 299 regarding network security settings when accessing Kibana.
"Warning: 299 Elasticsearch-7.15.0-79d65f6e357953a5b3cbcc5e2c7c21073d89aa29"
The URL, which can not simply be selected and accessed from the warning, is this:
https://www.elastic.co/guide/en/elasticsearch/reference/7.15/security-minimal-setup.html
I get that Elasticsearch is just trying to head off trouble for people who might install an unprotected system on an internet accessible machine. My system is very well protected by an outer layer access control and I have zero interest in having to jump through hoops like this. It's the middle of the night, and now I have to do this meaningless stuff, then reach out to a dozen users and explain to them that they're going to have to enter a username and password after they get through Cloudflare Access.
This really needs a configuration option like this:
xpack.security.stfu: immediately