[Docs][9.0.2] Add known issue about kibana.yml file (#222213)

## Summary

Contributes to https://github.com/elastic/kibana/issues/222127 by
updating the Kibana 9.0.2 release notes to include a known issue about
`kibana.yml` file

**Corresponding PRs**
- Kibana 8.18.2 known issues:
https://github.com/elastic/kibana/pull/222212

## Preview
- [Known
issues](https://docs-v3-preview.elastic.dev/elastic/kibana/pull/222213/release-notes/known-issues)

---------

Co-authored-by: Ying Mao <ying.mao@elastic.co>

docs/release-notes/known-issues.md

@@ -4,6 +4,30 @@ navigation_title: "Known issues"
 
 # Kibana known issues
 
+::::{dropdown} Upgrading Kibana from 8.18.x to 9.0.2 fails due to a configuration conflict in the kibana.yml file
+
+Applies to: {{stack}} 9.0.2
+
+**Details**
+
+Upgrading {{kib}} from version 8.18.x to 9.0.2 fails due to a configuration conflict if `xpack.alerting.cancelAlertsOnRuleTimeout` is set to `false` in the `kibana.yml` file. {{kib}} fails to boot and shows a fatal error message in the {{kib}} logs that's similar to the following:
+
+````
+FATAL Error: Rule type "transform_health" cannot have both cancelAlertsOnRuleTimeout set to false and autoRecoverAlerts set to true.
+````
+
+This failure occurs when the `xpack.alerting.cancelAlertsOnRuleTimeout` setting is set to `false`, which is incompatible with the default configuration of an internal setting (`autoRecoverAlerts`) in 9.0.2.
+
+
+**Action**
+
+To temporarily resolve the issue and allow the upgrade to proceed, follow these steps:
+
+1. Remove the `xpack.alerting.cancelAlertsOnRuleTimeout: false` setting from the `kibana.yml` file.
+2. Restart {{kib}} to apply the changes.
+
+::::
+
 ::::{dropdown} Errors in rule executions occur when maintenance windows have filters
 
 Applies to: {{stack}} 9.0.0, 9.0.1