@@ -27,10 +27,10 @@ figure out what to fix when and how it impacts our users. We like bugs
2727because it means people are using our code, and we like fixing them even
2828more. Please follow these guidelines for filing issues:
2929
30- * Describe the problem Include version of k8s, ` nginx-meshctl version ` , and what K8s platform.
31- * Include detailed information about how to recreate the issue
32- * Include relevant configuration , error messages and logs
33- * Sanitize the data. For example, be mindful of IPs, ports, application names and URLs
30+ * Describe the problem. Include version of k8s, ` nginx-meshctl version ` , and what K8s platform.
31+ * Include detailed information about how to recreate the issue.
32+ * Include relevant configurations , error messages, and logs.
33+ * Sanitize the data. For example, be mindful of IPs, ports, application names, and URLs
3434
3535** NOTE**
3636
@@ -40,11 +40,6 @@ Issues](https://github.com/nginxinc/nginx-service-mesh/issues)
4040
4141** NGINX Plus KIC Support**
4242
43- When running NSM with NGINX Plus Ingress Controller for Kubernetes
44- integration, support for NGINX Plus Kubernetes Ingress Controller (KIC),
45- when deploying NGINX Plus KIC with NGINX Service Mesh, is still available
46- through traditional channels.
47-
48- Existing NGINX and F5 customers can reach out to their accout team(s) for
49- help and support with NGINX Service Mesh.
43+ If you are using NSM with NGINX Plus Ingress Controller for Kubernetes, you can get support through your usual channels.
5044
45+ Existing NGINX and F5 customers can reach out to their account team(s) for help and support with NGINX Service Mesh.
0 commit comments