From f47093d1d83654e186ccee419bf0f988149da23b Mon Sep 17 00:00:00 2001
From: Justin Ross
Date: Mon, 14 Oct 2024 08:57:22 -0400
Subject: [PATCH] WIP (3) v2 content (still hidden)
---
docs/v2/index.html | 96 +++++++++++++++-------------------------------
input/v2/index.md | 71 +++++++++++++---------------------
2 files changed, 58 insertions(+), 109 deletions(-)
diff --git a/docs/v2/index.html b/docs/v2/index.html
index a4fdd79..99f7060 100644
--- a/docs/v2/index.html
+++ b/docs/v2/index.html
@@ -100,8 +100,6 @@ The move to custom resources
something v1 did not require. This is an advantage for some of our
users, but a disadvantage for others. We believe that custom
resources are, on balance, the right choice.
-
-
V2 has a new, uniform API for site configuration, site linking, and
service exposure. In v2, all of Skupper's interfaces and platforms
@@ -134,16 +132,10 @@
Service exposure in particular sees a change in v2. In v1, service
exposure is implicit: exposing a service in one site by default
exposed it in all the linked sites. In v2, service exposure is
-instead explicit. A connector binds a local workload to a routing
+instead explicit. A connector binds a local workload to a routing
key. In another site, a listener with a matching routing key makes it
available for application connections. Only those sites with a
-listener can connect to the service.
-
-
-
-
-
-
+matching listener can connect to the service.
A new controller and CLI
The new controller combines the previous service and site controllers
into one that can be deployed at cluster or namespace scope. The
@@ -152,39 +144,27 @@
A new controller and CLI
configuration changes without requiring re-creation of the site.
Notably, you can reconfigure your site without losing existing
site-to-site links.
-The new CLI closely follows the API, and indeed the CLI is really just
-a thin layer on top of the API. To simplify its use, the CLI blocks
-until operations are complete.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+The new CLI closely follows the API. Indeed, in v2 the CLI is really
+just a thin layer on top of the API. To simplify its use, the CLI
+blocks until operations are complete.
+Router improvements
+The router in v2 has a new, faster TCP adaptor with improved buffer
+handling and reduced threading overhead. The new TCP adaptor
+incorporates lightweight protocol observers for capturing HTTP traffic
+metrics. Together these reduce application latency and router CPU
+utilization.
+
-
-
-
-
-
-
-
-
-
-
-
+
+Non-Kube sites
+Skupper is not just for Kubernetes. Skupper sites can run on Docker,
+Podman, VMs, or bare metal. In v2, we've made the support for
+non-Kube sites simpler and more uniform. They use the same YAML
+resources as Kube sites. One codebase implements support for all of
+the non-Kube platforms.
@@ -195,47 +175,33 @@ A new controller and CLI
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
diff --git a/input/v2/index.md b/input/v2/index.md
index b8a923a..6ea0731 100644
--- a/input/v2/index.md
+++ b/input/v2/index.md
@@ -32,8 +32,6 @@ something v1 did not require. This is an advantage for some of our
users, but a disadvantage for others. We believe that custom
resources are, on balance, the right choice.
-
-
[custom-resources]: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/
[rbac]: https://kubernetes.io/docs/reference/access-authn-authz/rbac/
@@ -64,14 +62,10 @@ tools and to provide a foundation for third-party integrations.
Service exposure in particular sees a change in v2. In v1, service
exposure is implicit: exposing a service in one site by default
exposed it in all the linked sites. In v2, service exposure is
-instead explicit. A connector binds a local workload to a routing
+instead *explicit*. A connector binds a local workload to a routing
key. In another site, a listener with a matching routing key makes it
available for application connections. Only those sites with a
-listener can connect to the service.
-
-
-
-
+matching listener can connect to the service.
## A new controller and CLI
@@ -84,32 +78,29 @@ configuration changes without requiring re-creation of the site.
Notably, you can reconfigure your site without losing existing
site-to-site links.
-The new CLI closely follows the API, and indeed the CLI is really just
-a thin layer on top of the API. To simplify its use, the CLI blocks
-until operations are complete.
+The new CLI closely follows the API. Indeed, in v2 the CLI is really
+just a thin layer on top of the API. To simplify its use, the CLI
+blocks until operations are complete.
-
+## Router improvements
-
-
-
-
-
-
-
-
-
+The router in v2 has a new, faster TCP adaptor with improved buffer
+handling and reduced threading overhead. The new TCP adaptor
+incorporates lightweight protocol observers for capturing HTTP traffic
+metrics. Together these reduce application latency and router CPU
+utilization.
+
+
-
-
-
-
-
-
+## Non-Kube sites
-
+Skupper is not just for Kubernetes. Skupper sites can run on Docker,
+Podman, VMs, or bare metal. In v2, we've made the support for
+non-Kube sites simpler and more uniform. They use the same YAML
+resources as Kube sites. One codebase implements support for all of
+the non-Kube platforms.
@@ -120,34 +111,26 @@ until operations are complete.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+