Add more details to cross-cluster page #20230811 #20231102 #20230804

[AntonEliatra]

Description

Added more details to cross cluster page focusing on bare metal, kubernetes/helm and curl using UI dev tools

Issues Resolved

#20230811 #20231102 #20230804 from list on issue #4314

Checklist

• [x ] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
  For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[hdhalter]

Thanks, @AntonEliatra! Can you please resolve the Vale errors in the file before we send it for technical review?

[AntonEliatra]

@hdhalter all errors have now been resolved, please let me know if there are other changes needed

[hdhalter]

Thanks, @AntonEliatra! I have a few comments, but will send for a tech review.

[hdhalter]

Suggested change

	{: .label .label-green }
	{: .tip }

@AntonEliatra - You'll want to use Callouts for this type of info, not Labels.

[hdhalter]

Can we add another H2 above this section? Something like, "Configuring cross-cluster search from Dashboards"? (I would rethink the other headings, too.)

[AntonEliatra]

@hdhalter I dont think we discussed this today, can you elaborated please

[AntonEliatra]

There is only one screenshot just to demonstrate that all of the curl commands can be executed from dev tools, Do you mean to add more screenshots and expand on this?

[hdhalter]

Hi @scrawfor99, can you please review for technical accuracy? Thanks!

[stephen-crawford]

Thanks @AntonEliatra. Everything written looks correct on review.

I do have a couple general points for you and @hdhalter to consider:

1. I am not sure why we are splitting the examples into different infrastructure types. Looking at the examples, these seem standard across platforms. I am not sure whether splitting these into supported frameworks would cause a misunderstanding or perception that some of the commands only work on one system. I would expect all of the standard requests and commands to properly work on all systems.

2. I am not sure whether this page is better served in the search documentation directory. Other than the fact that you will need to authorize and authenticate with the requests (which is true for all of the requests when security is enabled) I don't see any security specific.

[AntonEliatra]

@scrawfor99 thanks for above feedback, I do agree that the docker example is quite comprehensive and commands apply to any installation, however there has been quite a few questions as to why its docker specific and how to configure this via UI, we could just state at the very top, that the example is using docker, but the steps/commands apply to any install, but will this sufficiently address the existing questions? @hdhalter what do you think?

Regarding point 2, I do agree, this page seems better placed under "Search" docs, I'm happy enough to change.

[hdhalter]

@peterzhuamazon - Can you please comment on Anton's suggestion above for positioning the Docker instructions?

[stephen-crawford]

Hi @AntonEliatra, gotcha. I definitely don't want to be a pain or anything. I think having the documentation like you wrote it would be just fine. My comment was more for the sake of @Naarcha-AWS or @hdhalter etc. for when they review as something they may consider.

I am in a bit of a unique case since I help with the documentation a lot but don't have as much opinion on the formatting as the technical content etc. Since you nailed the details there I have no issues :)

Looks like Peter may be able to give some advice on where things can best go

[hdhalter]

Thanks, @AntonEliatra !

@Naarcha-AWS - I made a few more tweaks to the content to add some context and fixed a few formatting issues. Please review at your convenience. Thanks!

Review feedback implemented.

[natebower]

@AntonEliatra @Naarcha-AWS Please see my comments and changes and let me know if you have any questions. Thanks!