Get help and support

Review the following ways to get help, training, and other forms of support as you use Gloo Gateway.

Product demos and proof of concept

Thanks for your interest in Gloo Gateway! Review the following ways you can get your hands on the product.

• To schedule a demo, meeting, or get more information about pricing, go to solo.io and click Request demo.
• To start building out a proof of concept, request an enterprise trial.
• For specific downloads, see the Versions page.

Slack support

Sign up for Slack and join the #gloo-gateway channel to post questions, share your experience, and talk with Solo engineers and fellow product users.

Product workshops and trainings

For asynchronous learning on your own and courses that include completion badges like Istio, try out Solo Academy.

To meet us in real time, check the upcoming Events.

Troubleshooting

Before opening an issue, try to debug your Gloo setup, your gateway, or application issues. For more information, see Troubleshooting.

Support process

For enterprise customers, refer to your service level agreement (SLA) for details on your included support. To raise a support issue, see the How to get help FAQ.

When you contact support, provide some basic information, including the following.

• Name, company and contact method.
• Environment details:
  • Versions for Gloo Gateway, Istio, and Kubernetes
  • Infrastructure provider, such as AWS or on-premises VMs
  • Production, development, or other environment details
• Setup details:
  • Installation method, such as Helm, istioctl, or meshctl
  • Management cluster details, such as whether it also runs workloads
  • Number of workload clusters
  • Ingress gateway details and namespace
  • East-west gateway details and namespace, if you use Gloo Gateway with Gloo Mesh or your own Istio installation
  • Federated trust details, such as self-signed certificates or certificate manager provided
  • Snapshot of your Gloo management-agent relay connection
• Issue details:
  • Description of the issue
  • Steps to reproduce the issue
  • Severity of the issue, such as urgent, high, normal, or low
  • Impact of the issue, such as blocking an update, blocking a demo, data loss or the system is down