add link to Jira and Documentation
A Kubernetes operator for [Percona XtraDB Cluster](https://www.percona.com/software/mysql-database/percona-xtradb-cluster) based on the [Operator SDK](https://github.com/operator-framework/operator-sdk).
-# :heavy_exclamation_mark: In the stage of active developing. Not ready for use yet.
-
-## Run
-```sh
-kubectl create -f deploy/crd.yaml
-kubectl create -f deploy/rbac.yaml
-kubectl create -f deploy/secrets.yaml
-kubectl apply -f deploy/cr.yaml
-```
-
-```sh
-OPERATOR_NAME=<operator-name> operator-sdk up local --namespace=<namespace>
-```
-
-## Delete
-```sh
-kubectl delete -f deploy/crd.yaml
-kubectl delete -f deploy/rbac.yaml
-kubectl delete -f deploy/cr.yaml
-kubectl delete -f deploy/secrets.yaml
-```
\ No newline at end of file
+# Documentation
+See the [Official Documentation](https://percona-lab.github.io/percona-xtradb-cluster-operator/) for more information.
+
+[![Official Documentation](https://via.placeholder.com/260x60/419bdc/FFFFFF/?text=Documentation)](https://percona-lab.github.io/percona-xtradb-cluster-operator/)
+
+# DISCLAIMER
+
+**This code is incomplete, expect major issues and changes until this repo has stabilised!**
+
+## Submitting Bug Reports
+
+If you find a bug in Percona Docker Images or in one of the related projects, please submit a report to that project's [JIRA](https://jira.percona.com) issue tracker.
+
+Your first step should be [search](https://jira.percona.com/issues/?jql=project%20%3D%20%22Cloud%20Dev%22) for a similar report in the existing set of open tickets. If someone else has already reported your problem, upvote that report to increase its visibility.
+
+If there is no existing report, submit a report following these steps:
+
+1. [Sign in to Percona JIRA.](https://jira.percona.com/login.jsp) You will need to create an account if you do not have one.
+2. [Go to the Create Issue screen and select the relevant project.](https://jira.percona.com/secure/CreateIssueDetails!init.jspa?pid=12500&issuetype=1&priority=3)
+3. Fill in the fields of Summary, Description, Steps To Reproduce, and Affects Version to the best you can. If the bug corresponds to a crash, attach the stack trace from the logs.
+
+An excellent resource is [Elika Etemad's article on filing good bug reports.](http://fantasai.inkedblade.net/style/talks/filing-good-bugs/).
+
+As a general rule of thumb, please try to create bug reports that are:
+
+- *Reproducible.* Include steps to reproduce the problem.
+- *Specific.* Include as much detail as possible: which version, what environment, etc.
+- *Unique.* Do not duplicate existing tickets.
+- *Scoped to a Single Bug.* One bug per report.
+
