Enable Personalized Service Health for a project using Config Connector

This document explains how to enable a project for service health events processing using Config Connector programmatically, if you're using Kubernetes and want to use the Service Health API.

Follow the prerequisites for using Config Connector.
Decide on the API VERSION: v1 or v1beta.

Create a file named psh-enable.yaml and copy the following snippet into it:

apiVersion: serviceusage.cnrm.cloud.google.com/API VERSION kind: Service metadata:  name: servicehealth.googleapis.com spec:  projectRef:  external: projects/PROJECT_ID

Run the following command:

kubectl apply -f psh-enable.yaml

The following message appears:

service.serviceusage.cnrm.cloud.google.com/servicehealth.googleapis.com created

Personalized Service Health will take up to 24 hours to start processing service health events.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-10-24 UTC.

Enable Personalized Service Health for a project using Config Connector Stay organized with collections Save and categorize content based on your preferences.

Enable Personalized Service Health for a project using Config Connector