[Meta] Obs-ds-hosted-services Integration enablement for 9.0.0

[gizas]

Based on the email, this meta issue aims to track the 9.0.0 enablement activities for all the integrations that belong to Obs-ds-hosted-services.

Main requirement is to update the version constrains of each related integration eg. version: "^8.17.0 || ^9.0.0"

Some sanity checks need to happen for all related packages

The minimum xpack.fleet.internal.registry.spec.min should be 3.0 for 9.0.0 migration. See info

Related Issues:

• https://github.com/elastic/integrations/pull/12251/files
• https://github.com/elastic/obs-integration-team/issues/148

Integrations to update:

Cloud related

• aws
• aws_logs
• awsfirehose
• azure
• azure_metrics
• gcp ---> This seems already done
• gcp_metrics

Cloudnative related

• containerd - Enabling 9.0.0 kibana support for kubernetes, kubernetes_otel, nginx_ingress, istio and containerd integrations #12535
• docker
• istio - Enabling 9.0.0 kibana support for kubernetes, kubernetes_otel, nginx_ingress, istio and containerd integrations #12535
• kubernetes - Enabling 9.0.0 kibana support for kubernetes, kubernetes_otel, nginx_ingress, istio and containerd integrations #12535
• kubernetes_otel - Enabling 9.0.0 kibana support for kubernetes, kubernetes_otel, nginx_ingress, istio and containerd integrations #12535
• nginx_ingress_controller - Enabling 9.0.0 kibana support for kubernetes, kubernetes_otel, nginx_ingress, istio and containerd integrations #12535
• prometheus ---> Shared with integrations team

[gizas]

Note:

See #12468 (comment)

First set temporarily the Kibana constraint ^9.0.0 for the packages and then revert it before merging. This way we will be sure that the pipeline checks will run for the 9.0.0 version. For any package, run the pipeline, fix any errors and then revert back the constrains