Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a document about how to get support #1388

Merged
merged 8 commits into from
Jan 10, 2024
Merged
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 42 additions & 0 deletions site/content/support.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
---
title: "Where to Go for Support"
Jcahilltorre marked this conversation as resolved.
Show resolved Hide resolved
draft: false
weight: 1100
toc: true
tags: [ "docs" ]
docs: "DOCS-OOO"
---

## Support Policy

NGINX Gateway Fabric adheres to the support policy detailed at [nginx.com/support](https://nginx.com/support).

## Commercial Support
ADubhlaoich marked this conversation as resolved.
Show resolved Hide resolved

For paid customers of NGINX Gateway Fabric, commercial support is available by opening a support case at the [MyF5](https://my.f5.com/) portal.

Generate a Support Package
Jcahilltorre marked this conversation as resolved.
Show resolved Hide resolved
To generate a support package, run the following command:

- (TBD)

## Community Support

For NGINX Gateway Fabric support or issues not addressed by documentation, you can reach out using the following two options:
Jcahilltorre marked this conversation as resolved.
Show resolved Hide resolved

- Create an issue using the [Issues tab in the NGINX Gateway Fabric GitHub repo](https://github.com/nginxinc/nginx-gateway-fabric/issues).

We use issues for bug reports and to discuss new features. Creating issues is good, creating good issues is even better. Filing meaningful bug reports with lots of information in them helps us figure out what to fix when and how it impacts our users. We like bugs because it means people are using our code, and we like fixing them even more.

All issues should follow these guidelines:

-Describe the problem. Include version of Kubernetes, NGINX Gateway Fabric version, and what Kubernetes platform.
-Include detailed information about how to recreate the issue.
-Include relevant configurations, error messages, and logs.
-Sanitize the data. For example, be mindful of IPs, ports, application names, and URLs.
Jcahilltorre marked this conversation as resolved.
Show resolved Hide resolved

- Join the [NGINX Community Slack](https://community.nginx.org/joinslack)

NGINX Community Slack is a place where you can give and receive help with NGINX Gateway Fabric questions and issues, share useful advice, get pointers to additional information, and even find info on related projects. You can keep up to date with the latest announcements and change logs.

We also actively monitor the #feedback channel where you can share your thoughts NGINX Gateway Fabric, give feedback about your experience using NGINX products, or share whatever else you think is important for us to know.
Loading