New nav in ESS

[nastasha-solomon]

Description

The main Security nav in ESS is being updated so it aligns with the main Security nav in Serverless. The updated nav will be available in 8.15 and only affects the ESS version of Security.

Notes

• Users will have an option to revert back to the "classic" nav at any time.
• Changes are being merged to 8.14, but they won't be available for customers until 8.15. There'll be additional work to clean up classic nav components after 8.14. I'm not sure what the doc impact of this work will be -- or if there will be any. Will need to sync with @semd on this.
• Check out the latest set of TH team demos for a demo of these changes.

Background & resources

• PRs: [Security Solution] Integrate new navigation in stateful kibana#179971
• Issues/metas: [Security Solution] Integrate new stateful navigation kibana#179162
• Point of contact: @semd
• Test environments: TBD - currently we'll have to add several feature flags to enable the new nav

Issue template info

• Which documentation set does this change impact? ESS only

• ESS release: 8.15

• Serverless release: N/A

• Feature differences: N/A? (confirm if the navs will truly be identical between ESS and serverless, or if any differences will still occur)

• API docs impact: N/A

• Prerequisites, privileges, feature flags: Refer to related dev PR [Security Solution] Integrate new navigation in stateful kibana#179971:

  Expand for feature flag details

  Unless we add the kibana.yml configurations to enable the new navigation, the regular classic navigation will be displayed, it should keep working the same way without any change. The new landing pages (Assets, Investigations, Machine Learning,...), that exist only when using the new navigation, should not be accessible using the classic version.

  To enable the new navigation add the following kibana.yml configs:

  xpack.cloud_integrations.experiments.enabled: true
  xpack.cloud_integrations.experiments.flag_overrides:
    "navigation.solutionNavEnabled": true
  
  xpack.cloud.id: "ftr_fake_cloud_id:aGVsbG8uY29tOjQ0MyRFUzEyM2FiYyRrYm4xMjNhYmM="
  xpack.cloud.base_url: "https://cloud.elastic.co"
  xpack.cloud.deployment_url: "/deployments/deploymentId"
  

  And enable the advanced setting

  

[joepeeples]

Adjusting ESS release from 8.14 to 8.15, based on related PR elastic/kibana#179971:

Rollout

The new solutions navigation will not be available for customers on 8.14, it will only be enabled for internal Elastic users (via Lauchdarkly), who will have the ability to opt out of it from their profile menu. We'll collect feedback and telemetry and address any bugs or improvements (together with the Kibana platform team). The plan is to start making it available to customers in 8.15.

This PR also has details on feature flags and other config needed to enable the new nav in 8.14. Even if it's planned to roll out until 8.15, it'll be helpful to start getting familiar with the new nav and plan how we'd like to update docs for 8.15.

[joepeeples]

Doesn't appear to be enabled by default in 8.15; I'm assuming it'll be 8.16...

[nastasha-solomon]

Note from today's doc team sync: generalized wording for feature access from the main nav or global search is currently being discussed. Once it's finalized, we'll discuss a strategy for updating the Security docs.

[nastasha-solomon]

Closing this as we're using nav-agnostic language in 8.16 to refer to pages and apps. The language and patterns that we're using are described in #5896.