Indicate managed ILM policies in the UI

[cjcenizal]

In elastic/elasticsearch#73629 Elasticsearch updated their built-in policies with information that identifies them and explains their purpose. We should surface this information in the UI, and potentially hide the built-in ones behind their own tab, since we don't expect users to mess around with them.

[elasticmachine]

Pinging @elastic/kibana-stack-management (Team:Stack Management)

[mostlyjason]

Nice thanks @cjcenizal! We could use this in integration packages as well

[jloleysens]

Hey @cjcenizal, thanks for opening this !

For Reporting, we'd like to provision an ILM policy for users to manage the lifecycle of reports (i.e., a Kibana provisioned policy). The idea being: we send users to edit this policy from within reporting to manage their reports' lifecycle.

Translating to the UX described here this sounds like a policy that does not belong in the "managed policies" tab, but also not quite in the "user policies" tab since it is automatically provisioned. Going on my gut, if I had to put it in one of these I'd put it in the "user policies" tab since we do want people to tweak it.

I'd love to hear your (or anyone elses) thoughts on this!

Issue: see #81544

[cjcenizal]

Going on my gut, if I had to put it in one of these I'd put it in the "user policies" tab since we do want people to tweak it.

👍 Makes sense to me.

[yuliacech]

More managed policies were added in 76791 and it would be great to not only add a badge for them, but also a warning that those policies should not be changed by the user.
The reason this warning is needed in the UI is that when an ILM policy is updated, its version is always incremented. ES uses the version number to know which managed policies need to be updated. So the user that changed any managed policies, won't get any updates from ES. The user can't set a lower version of the ILM policy, but they can delete the changed policy before the update to get new ILM policies from ES.
Also currently the empty state won't be shown as there are always policies in the table, so we could add a condition to show the empty state if the user has only managed policies. Maybe a callout inviting them to create their first custom policy.

[droberts195]

+1 for this. We have already had 2 users get ML into a mess by adding a cold or frozen phase to ml-size-based-ilm-policy and the current ILM UI makes it very easy to do this.

[elasticmachine]

Pinging @elastic/ml-ui (:ml)