Skip to content

Add GCP Enterprise example with PSC#802

Open
Shashwat Johari (jshashwat93) wants to merge 5 commits intoconfluentinc:masterfrom
jshashwat93:master
Open

Add GCP Enterprise example with PSC#802
Shashwat Johari (jshashwat93) wants to merge 5 commits intoconfluentinc:masterfrom
jshashwat93:master

Conversation

@jshashwat93
Copy link

@jshashwat93 Shashwat Johari (jshashwat93) commented Sep 5, 2025

Release Notes

New Features

  • This pull request adds a new Terraform example for provisioning a Confluent Cloud enterprise cluster on Google Cloud Platform (GCP) with Private Service Connect (PSC).

Bug Fixes

  • N/A

Examples

  • Added a new example demonstrating how to provision a Confluent Cloud enterprise cluster on GCP with PSC.

Checklist

  • I can successfully build and use a custom Terraform provider binary for Confluent.
  • I have verified my PR with real Confluent Cloud resources in a pre-prod or production environment, or both.
  • I have attached manual Terraform verification results or screenshots in the Test & Review section below.
  • I have included appropriate Terraform acceptance or unit tests for any new resource, data source, or functionality.
  • I confirm that this PR introduces no breaking changes or backward compatibility issues.
  • I have updated the corresponding documentation and include relevant examples for this PR.
  • I have indicated the potential customer impact if something goes wrong in the Blast Radius section below.
  • I have put checkmarks below confirming that the feature associated with this PR is enabled in:
    • Confluent Cloud prod
    • Confluent Cloud stag
    • Check this box if the feature is enabled for certain organizations only

What

This pull request introduces a new Terraform configuration example for provisioning a Confluent Cloud enterprise cluster on Google Cloud Platform (GCP) with Private Service Connect (PSC). This example is necessary to provide users with a complete, runnable guide for setting up private, secure connectivity to Confluent Cloud within their GCP environment.

The implementation follows the established conventions of existing examples, mirroring the directory structure of the aws and azure enterprise examples and adhering to the GCP resource conventions from the dedicated cluster PSC example. Key changes include adding a new gcp-enterprise-example directory and configuring the necessary Terraform files (main.tf, variables.tf, outputs.tf) to manage the required resources.

Blast Radius

If something goes wrong with this pull request, the impact is minimal. This is a new example and not a change to the core provider functionality. The primary risk is that the example may not work as intended, potentially causing confusion for users attempting to follow it. It will not break existing user configurations or block any current customer operations, as it does not affect any existing resources, data sources, or import functions.

References

Test & Review

Yes, this pull request was tested from end to end using a GCP account. The verification process involved deploying all resources defined in the gcp-enterprise-example directory, including the Confluent Cloud enterprise cluster and the Private Service Connect (PSC) setup. All resources were successfully provisioned and then destroyed, confirming the example's functionality and ensuring it is a complete, runnable solution for users. This end-to-end test confirms that the provided Terraform example works as intended for setting up a private Confluent Cloud cluster on GCP.

Link to logs from tests: https://confluent.slack.com/archives/C01880K2BAA/p1758664258934339?thread_ts=1756217781.203839&cid=C01880K2BAA

Copy link
Contributor

@linouk23 Kostya Linou (linouk23) left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

Yes, this pull request was tested from end to end using a GCP account. The verification process involved deploying all resources defined in the gcp-enterprise-example directory, including the Confluent Cloud enterprise cluster and the Private Service Connect (PSC) setup. All resources were successfully provisioned and then destroyed, confirming the example's functionality and ensuring it is a complete, runnable solution for users. This end-to-end test confirms that the provided Terraform example works as intended for setting up a private Confluent Cloud cluster on GCP.

Could you attach the logs to the PR? Feel free to post them on Slack and then add a link to the PR description, thanks!

Adding dependency on PSC module so that the topic `orders` is deleted before the DNS records and hosted zone gets deleted during destroy
@jshashwat93
Copy link
Author

Looks great!

Yes, this pull request was tested from end to end using a GCP account. The verification process involved deploying all resources defined in the gcp-enterprise-example directory, including the Confluent Cloud enterprise cluster and the Private Service Connect (PSC) setup. All resources were successfully provisioned and then destroyed, confirming the example's functionality and ensuring it is a complete, runnable solution for users. This end-to-end test confirms that the provided Terraform example works as intended for setting up a private Confluent Cloud cluster on GCP.

Could you attach the logs to the PR? Feel free to post them on Slack and then add a link to the PR description, thanks!

Here are the logs:

https://confluent.slack.com/archives/C01880K2BAA/p1758664258934339?thread_ts=1756217781.203839&cid=C01880K2BAA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants