Get support

This page shows you how to get support for Config Sync.

Before contacting support

Before contacting support, you can try and resolve issues yourself. For troubleshooting tips, see Troubleshoot Config Sync.

Support options

Google Cloud offers different support packages to meet different needs, such as 24/7 coverage, phone support, and access to a technical support manager. For more information, see Cloud Customer Care.

For open source Config Sync, you can get support by checking for existing issues or opening a new issue in the public GitHub issue tracker.

What Google doesn't support

Google doesn't support issues with customer-owned YAML file configurations.

If you install open source products, such as open source Config Sync or other tools like kpt, you can get community support for these products:

We recommend that you use Config Sync version 1.22.0.

Shared responsibility model

Running a business-critical production application on GKE Enterprise requires multiple parties to carry different responsibilities. These responsibilities are described at GKE Enterprise shared responsibility.

Community resources

Use the following resources to get support from the Config Sync community.

Ask a question on Stack Overflow

If you use kpt or Kustomize, you can use Stack Overflow tags to receive responses from the Stack Overflow community. This community includes Google engineers, who monitor the tag and offer unofficial support. You can use the following tags:

File bugs or feature requests

You can submit a product issue by using one of the following procedures:

  • Config Sync issues and feature requests: Check for existing issues or open new issues in the public issue trackers For new issues, consider including a bug report by using the nomos bugreport command.

  • Documentation issues: On the documentation page, select Send feedback. This action opens a feedback form. The Config Management team reviews and takes action on your comments.

Billing questions

Use the following resources to get help with billing questions:

What's next