Connect to Elasticsearch via SSL when starting kibana with --ssl#42840
Connect to Elasticsearch via SSL when starting kibana with --ssl#42840mikecote merged 8 commits intoelastic:masterfrom
--ssl#42840Conversation
mikecote
added
Team:Operations
|
Pinging @elastic/kibana-operations |
This comment has been minimized.
This comment has been minimized.
src/cli/serve/serve.js
Outdated
| } | ||
|
|
||
| if (opts.ssl && !opts.elasticsearch && !has('elasticsearch.hosts')) { | ||
| set('elasticsearch.hosts', 'https://localhost:9200'); |
There was a problem hiding this comment.
This doesn't seem to be the best way to hardcode the host. Maybe there's a better way to do this? Or to findout if Elasticsearch is running on a different port?
Note the certificate within CA_CERT_PATH is bound to localhost.
There was a problem hiding this comment.
If --elasticsearch or --elasticsearch.hosts is defined we should parse that url with url.parse(), throw if parsedUrl.hostname !== 'localhost', and if it is then use parsedUrl.port and default to 9200.
💚 Build Succeeded |
src/cli/serve/serve.js
Outdated
| import _ from 'lodash'; | ||
| import { statSync } from 'fs'; | ||
| import { resolve } from 'path'; | ||
| import { CA_CERT_PATH } from '@kbn/dev-utils'; |
There was a problem hiding this comment.
are we okay shipping dev certs? i know there's quite a bit in this file that makes it tough and extends beyond the scope of this PR
There was a problem hiding this comment.
Yeah, we should only be requiring this when opts.dev is true so that we don't have to ship @kbn/dev-utils in the distributable.
|
Out of scope of this PR for now but I think this makes a great example of committing a new config.*.yml for development. Other variations include disabled plugins for quicker refreshes and no base paths and so on. |
💚 Build Succeeded |
💔 Build Failed |
|
retest |
💚 Build Succeeded |
…lastic#42840) * Initial work * Add check for elasticsearch.hosts * Make --ssl apply default config values only * Move @kbn/dev-utils to devDependencies * Check elasticsearch url for localhost * Cleanup * elasticsearch.hosts can be string too
…p-metrics-selectall * 'master' of github.com:elastic/kibana: (306 commits) [ML] Adding job overrides to the module setup endpoint (elastic#42946) [APM] Fix missing RUM url (elastic#42940) close socket timeouts without message (elastic#42456) Upgrade elastic/charts to 8.1.6 (elastic#42518) [ML] Delete old AngularJS data visualizer and refactor folders (elastic#42962) Add custom formatting for Date Nanos Format (elastic#42445) [Vega] Shim new platform - vega_fn.js -> vega_fn.js , use ExpressionFunction (elastic#42582) add socket.getPeerCertificate to KibanaRequest (elastic#42929) [Automation] ISTANBUL PRESET PATH is not working fine with constructor(private foo) (elastic#42683) [ML] Data frames: Updated stats structure. (elastic#42923) [Code] fixed the issue that the repository can not be deleted in some cases. (elastic#42841) [kbn-es] Support for passing regex value to ES (elastic#42651) Connect to Elasticsearch via SSL when starting kibana with `--ssl` (elastic#42840) Add Elasticsearch SSL support for integration tests (elastic#41765) Fix duplicate fetch in Visualize (elastic#41204) [DOCS] TSVB and Timelion clean up (elastic#42953) [Maps] [File upload] Fix maps geojson upload hanging on index step (elastic#42623) [APM] Use rounded bucket sizes for transaction distribution (elastic#42830) [yarn.lock] consistent resolve domain (elastic#42969) [Uptime] [Test] Repurpose unit test assertions to avoid flakiness (elastic#40650) ...
4 participants
In this PR, I'm making
--sslflag also connect to Elasticsearch via SSL. This will expect Elasticsearch to already be running with SSL enabled (yarn es snapshot --ssl). I'm also making the--ssloption only apply default configurations. It will throw an error if something is already configured for SSL.