You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@apisix.apache.org by kv...@apache.org on 2020/07/30 08:36:09 UTC
[apisix-control-plane] branch master updated: doc: move discuss to
issue #3 (#4)
This is an automated email from the ASF dual-hosted git repository.
kvn pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-control-plane.git
The following commit(s) were added to refs/heads/master by this push:
new d67cb31 doc: move discuss to issue #3 (#4)
d67cb31 is described below
commit d67cb31018272b9ad94031e080e8b5585508a79e
Author: kv <gx...@163.com>
AuthorDate: Thu Jul 30 16:36:03 2020 +0800
doc: move discuss to issue #3 (#4)
---
README.md | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/README.md b/README.md
index d94a498..04f0929 100644
--- a/README.md
+++ b/README.md
@@ -1,11 +1,14 @@
# apisix-control-plane
-apisix-control-plane provide APISIX with a yaml configuration capability
+## what is apisix-control-plane?
+apisix-control-plane provide APISIX with a `yaml` configuration capability,
+We can use `yaml` to define the proxy behavior of APISIX
-Why do you want to do this?
-1. In order to facilitate the integration of k8s, use yaml to define APISIX;
+## Why do you want to do this?
+1. In order to facilitate the integration of k8s, use `yaml` to define APISIX;
2. For easier synchronization across clusters;
3. Can be better adapted to multiple platforms (k8s, vm);
-Here are some examples of yaml and we can add comments here.
-https://docs.google.com/document/d/1mr0Wp7zYpEzgr4qsv8rxfS2MWzDpihgBcowIafgG8q4/edit#
\ No newline at end of file
+## DISCUSS
+Here are some examples of `yaml` and we can add comments here.
+https://github.com/apache/apisix-control-plane/issues/3
\ No newline at end of file