Update google-functions.md

docs/continuous-delivery/deploy-srv-diff-platforms/google-cloud-functions/google-functions.md

@@ -38,7 +38,18 @@ Harness supports the following:
 
 - For Google Cloud Functions 2nd gen, Harness does not support [Google Cloud Source Repository](https://cloud.google.com/functions/docs/deploy#from-source-repo) at this time. Only Google Cloud Storage is supported.
 - For Google Cloud Functions 1st gen, Harness supports both Google Cloud Storage and Google Cloud Source.
-- Currently, the OIDC connectivity mode is not compatible with Google Cloud Functions. You can't deploy Google Cloud Functions with OIDC-enabled GCP connectors. 
+- We support OpenID Connect (OIDC) authentication in Google Cloud Functions, enabling seamless integration with OIDC-compliant identity providers for enhanced security and user management.
+
+To configure OIDC authentication in Kubernetes, navigate to account/project settings.
+
+Select **New Connector**, select **GCP**
+
+In the details tab, select **OIDC**
+
+Enter the necessary details like **Workload Pool ID**, **Provider ID**, **Project ID** and **Service Account Email**
+
+![](static/gcp-oidc.png)
+
 
 ## Deployment summary
 
@@ -705,21 +716,6 @@ The infrastructure definition is added.
   </TabItem2>
 </Tabs2>
 
-:::info
-
-We now support OpenID Connect (OIDC) authentication in GCP, enabling seamless integration with OIDC-compliant identity providers for enhanced security and user management.
-
-To configure OIDC authentication in Kubernetes, navigate to account/project settings.
-
-Select **New Connector**, select **GCP**
-
-In the details tab, select **OIDC**
-
-Enter the necessary details like **Workload Pool ID**, **Provider ID**, **Project ID** and **Service Account Email**
-
-![](static/gcp-oidc.png)
-:::
-
 ### Dynamically provisioned Functions infrastructure
 
 Here is a summary of the steps to dynamically provision the target infrastructure for a deployment: