-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fleet] Do not provide instruction to setup an http Fleet server #129371
Conversation
Pinging @elastic/fleet (Team:Fleet) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we change the UI to not require the user to enter the protocol at all? Instead I think we should have https://
be added to the "Fleet Server host" prepend
prop or completely replace it.
We should also verify what the behavior is of showing the --insecure
option on the regular Elastic Agent enrollment command given to the user. Do we need to display it somehow when a Fleet Server https
host is configured, but it was known to be configured with Quick Start?
I'd also like @jen-huang to 👍 this before moving forward.
Just tested and using |
We should revert this flag from docs as well: elastic/observability-docs#1441 |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
Looks like Cypress tests are failing because some of the packages removed here elastic/package-storage#3992 are returning random 404 from the snapshot registry |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small copy nit, otherwise LGTM
...eet/sections/agents/agent_requirements_page/components/fleet_server_on_prem_instructions.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I think it would make sense to open an enhancement issue to allow us to track whether or not the Fleet Server is using a self-signed certificate so we could automatically tell the user to use the --insecure
flag on Agent enrollment when necessary, along with some warnings in the UI about this not being a production-ready configuration.
@elasticmachine merge upstream |
💛 Build succeeded, but was flakyMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @nchaulet |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…9371) (#129756) (cherry picked from commit eff1e0c) Co-authored-by: Nicolas Chaulet <[email protected]>
Hi @nchaulet
Build details: Thanks |
Summary
Resolve #122625
Change the fleet server on prem instruction to not provide instructions to setup an http fleet server and do not allow to add an
http
fleet server url in these instructions (it's still possible to do it via the settings tab or via the kibana preconfigure output)Details:
--fleet-server-insecure-http
flag