-
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] On-prem Instructions for setting fleet-server displayed under add agent flyout on cloud deployments #104280
Comments
Pinging @elastic/fleet (Team:Fleet) |
@manishgupta-qasource Please review |
Reviewed & Assigned to @jen-huang CC @EricDavisX |
This is expected behavior. We allow users to add additional Fleet Servers on Cloud, if they wish, hence this showing when you have a policy with Fleet Server integration. |
Hi @jen-huang Thanks for confirmation on above reported issue. However, we have now come up with following queries.
Thanks |
@dikshachauhan-qasource For quick start certs shouldn't be needed. For production, the commands generated in the following step has placeholder arguments for certs. |
Hi @jen-huang Thanks |
@amolnater-qasource I think that should work. |
Hi @EricDavisX We have created a testcase for above reported issue under bug conversion task . Testcase link is : C149906 Thanks |
Kibana version: 7.14 BC1 Kibana Cloud-qa environment
Host OS and Browser version: Chrome, Firefox and edge
Preconditions:
Build Details:
Steps to reproduce:
- Login to Kibana.
- Navigate to Fleet>Agents tab.
- Click on 'Add Agent' button and select policy as 'test1'.
- Observe, On-prem Instructions for setting fleet-server displayed.
Expected result:
Screenshot:
The text was updated successfully, but these errors were encountered: