updates (#258)

* updates

Author: pwright

config/config.py

@@ -9,4 +9,4 @@ def path_nav(page):
 
     return f"<nav id=\"-path-nav\"><div>{links}</div></nav>"
 
-skupper_cli_version = '2.0.0-rc1'
+skupper_cli_version = '2.0.0'

input/console/index.md

@@ -1,7 +1,9 @@
+<a id="console"></a>
 # Using the Network console
 
 The Network console provides data and visualizations of the traffic flow between sites.
 
+<a id="console-enabling"></a>
 ## Enabling the Network console
 
 **Prerequisites**
@@ -23,6 +25,7 @@ The Network console provides data and visualizations of the traffic flow between
    ```
    helm install skupper-network-observer oci://quay.io/skupper/helm/network-observer --version {{skupper_cli_version}}
    ```
+
    The output is similar to the following:
    ```
    Pulled: quay.io/skupper/helm/network-observer:2.0.0
@@ -61,7 +64,9 @@ The Network console provides data and visualizations of the traffic flow between
    ```
    oc expose skupper-network-observer
    ```
-## Exploring the Skupper console
+
+<a id="console-exploring"></a>
+## Exploring the Network console
 
 The Network console provides an overview of the following:
 

input/install/index.md

@@ -1,4 +1,5 @@
-# Installing the Skupper controller
+<a id="kube-installing-controller"></a>
+# Installing the Skupper controller on Kubernetes
 
 Before you can create a site on Kubernetes, you must install the Skupper controller. 
 You can install the controller using the following methods:
@@ -7,29 +8,39 @@ You can install the controller using the following methods:
 * Helm charts
 * Operator 
 
+After installing the Skupper controller, you can create sites using the CLI or YAML:
+
+* [Creating a site using the CLI][cli-site]
+* [Creating a site using YAML][yaml-site]
+
+[cli-site]: ../kube-cli/site-configuration.html
+[yaml-site]: ../kube-yaml/site-configuration.html
+
+**NOTE**: If you install the controller scoped to cluster, you can create sites in any namespace.
+If you scope the controller to a namespace, you can only create sites in that namespace.
+
+
+<a id="kube-installing-controller-yaml"></a>
 ## Installing the Skupper controller using YAML
 
 **Prerequisites**
 
 * cluster-admin access to cluster
 
-Install the latest version using the following commands:
+Install a cluster-scoped controller using the following commands:
 
 ```
-kubectl apply -f https://raw.githubusercontent.com/skupperproject/skupper/v2/config/crd/bases/skupper_access_grant_crd.yaml
-kubectl apply -f https://raw.githubusercontent.com/skupperproject/skupper/v2/config/crd/bases/skupper_access_token_crd.yaml
-kubectl apply -f https://raw.githubusercontent.com/skupperproject/skupper/v2/config/crd/bases/skupper_attached_connector_anchor_crd.yaml
-kubectl apply -f https://raw.githubusercontent.com/skupperproject/skupper/v2/config/crd/bases/skupper_attached_connector_crd.yaml
-kubectl apply -f https://raw.githubusercontent.com/skupperproject/skupper/v2/config/crd/bases/skupper_certificate_crd.yaml
-kubectl apply -f https://raw.githubusercontent.com/skupperproject/skupper/v2/config/crd/bases/skupper_connector_crd.yaml
-kubectl apply -f https://raw.githubusercontent.com/skupperproject/skupper/v2/config/crd/bases/skupper_link_crd.yaml
-kubectl apply -f https://raw.githubusercontent.com/skupperproject/skupper/v2/config/crd/bases/skupper_listener_crd.yaml
-kubectl apply -f https://raw.githubusercontent.com/skupperproject/skupper/v2/config/crd/bases/skupper_router_access_crd.yaml
-kubectl apply -f https://raw.githubusercontent.com/skupperproject/skupper/v2/config/crd/bases/skupper_secured_access_crd.yaml
-kubectl apply -f https://raw.githubusercontent.com/skupperproject/skupper/v2/config/crd/bases/skupper_site_crd.yaml
-kubectl apply -f https://raw.githubusercontent.com/skupperproject/skupper/v2/cmd/controller/deploy_cluster_scope.yaml
+kubectl apply -f https://github.com/skupperproject/skupper/releases/download/{{skupper_cli_version}}/skupper-cluster-scope.yaml
 ```
 
+Install a namespace-scoped controller using the following commands:
+
+```
+kubectl apply -f https://github.com/skupperproject/skupper/releases/download/{{skupper_cli_version}}/skupper-namespace-scope.yaml
+```
+
+
+<a id="kube-installing-controller-helm"></a>
 ## Installing the Skupper controller using the Skupper Helm charts
 
 **Prerequisites**
@@ -40,17 +51,28 @@ kubectl apply -f https://raw.githubusercontent.com/skupperproject/skupper/v2/cmd
 
 **Procedure**
 
-1. Run the following command to install the Skupper controller on a cluster:
+Run the following command to install a cluster-scoped controller:
 
-   ```
-   helm install skupper oci://quay.io/skupper/helm/skupper --version {{skupper_cli_version}}
-   ```
-2. Optionally install the network observer:
-   ```
-   helm install skupper-network-observer oci://quay.io/skupper/helm/network-observer --version {{skupper_cli_version}}
-   ```
+```
+helm install skupper oci://quay.io/skupper/helm/skupper --version {{skupper_cli_version}}
+```
+To install a namespace-scoped controller, add the `--set scope=namespace` option.
 
 
 <!--
+<a id="kube-installing-controller-operator"></a>
 ## Installing the Skupper controller using the Skupper Operator
+
+**Prerequisites**
+
+* cluster-admin access to cluster
+* OpenShift
+
+**Procedure**
+
+1. Navigate to the **OperatorHub** in the **Administrator** view.
+2. Search for `Skupper`, provided by `Skupper project`.
+3. Select **stable-2.0** from **Channel**.
+4. Select the latest **Version**.
+5. Click **Install**.
 -->

input/kube-cli/index.md

@@ -1,3 +1,4 @@
+<a id="kube-cli"></a>
 # Overview of Skupper CLI on Kubernetes
 
 You can use the `skupper` CLI on Kubernetes after installing the Skupper controller to configure sites, links and services. 

input/kube-cli/service-exposure.md

@@ -1,3 +1,4 @@
+<a id="kube-exposing-services-cli"></a>
 # Exposing services on the application network using the CLI
 
 After creating an application network by linking sites, you can expose services from one site using connectors and consume those services on other sites using listeners.
@@ -6,6 +7,8 @@ For example, if you create a connector with the routing key `backend`, you need
 
 This section assumes you have created and linked at least two sites.
 
+<a id="kube-creating-connector-cli"></a>
+<!-- Creating a connector on Kubernetes using the CLI -->
 ## Creating a connector using the CLI
 
 A connector binds a local workload to listeners in remote sites.
@@ -47,7 +50,8 @@ For more information about connectors see [Connector concept][connector]
 
 There are many options to consider when creating connectors using the CLI, see [CLI Reference][cli-ref], including *frequently used* options.
 
-
+<a id="kube-creating-listener-cli"></a>
+<!-- Creating a listener on Kubernetes using the CLI -->
 ## Creating a listener using the CLI
 
 A listener binds a local connection endpoint to connectors in remote sites. 

input/kube-cli/site-configuration.md

@@ -1,9 +1,11 @@
+<a id="kube-creating-site-cli"></a>
 # Creating a site on Kubernetes using the Skupper CLI
 
 Using the skupper command-line interface (CLI) allows you to create and manage sites from the context of the current namespace.
 
 A typical workflow is to create a site, link sites together, and expose services to the service network.
 
+<a id="kube-checking-cli"></a>
 ## Checking the Skupper CLI
 
 Installing the skupper command-line interface (CLI) provides a simple method to get started with Skupper.
@@ -17,6 +19,7 @@ Installing the skupper command-line interface (CLI) provides a simple method to
    cli                     {{skupper_cli_version}}
    ```
 
+<a id="kube-creating-simple-site-cli"></a>
 ## Creating a simple site using the CLI on Kubernetes
 
 **Prerequisites**
@@ -67,6 +70,7 @@ For example
   ```
   You can check the status of the site at any time using `skupper site status`.
 
+<a id="kube-deleting-site-cli"></a>
 ## Deleting a site using the CLI on Kubernetes
 
 **Prerequisites**
@@ -84,5 +88,4 @@ For example
    ```bash
    skupper site delete
    ```
-
 [cli-ref]: https://skupperproject.github.io/refdog/commands/index.html

input/kube-cli/site-linking.md

@@ -1,10 +1,12 @@
+<a id="kube-linking-cli"></a>
 # Linking sites on Kubernetes using the Skupper CLI
 
 Using the Skupper command-line interface (CLI) allows you to create links between sites.
 The link direction is not significant, and is typically determined by ease of connectivity. For example, if east is behind a firewall, linking from east to west is the easiest option.
 
 Once sites are linked, services can be exposed and consumed across the application network without the need to open ports or manage inter-site connectivity.
 
+<a id="kube-token-cli"></a>
 ## Linking sites using a token
 
 A token provides a secure method to link sites.
@@ -76,6 +78,7 @@ To link sites, you create a token on one site and redeem that token on the other
 
 There are many options to consider when linking sites using the CLI, see [CLI Reference][cli-ref], including *frequently used* options.
 
+<a id="kube-link-cli"></a>
 ## Linking sites using a `link` resource
 
 An alternative approach to linking sites using tokens is to create a `link` resource YAML file using the CLI, and to apply that resource to another site.

input/kube-yaml/index.md

@@ -1,3 +1,4 @@
+<a id="kube-yaml"></a>
 # Overview of using YAML CLI on Kubernetes
 
 You can use YAML on Kubernetes after installing the Skupper controller to

input/kube-yaml/service-exposure.md

@@ -1,3 +1,4 @@
+<a id="kube-exposing-services-yaml"></a>
 # Exposing services on the application network using YAML
 
 After creating an application network by linking sites, you can expose services from one site using connectors and consume those services on other sites using listeners.
@@ -6,6 +7,8 @@ For example, if you create a connector with the routing key `backend`, you need
 
 This section assumes you have created and linked at least two sites.
 
+<a id="kube-creating-connector-yaml"></a>
+<!-- Creating a connector on Kubernetes using YAML -->
 ## Creating a connector using YAML
 
 A connector binds a local workload to listeners in remote sites.
@@ -60,7 +63,8 @@ For more information about connectors see [Connector concept][connector]
 
 There are many options to consider when creating connectors using YAML, see [CLI Reference][cli-ref], including *frequently used* options.
 
-
+<a id="kube-creating-listener-yaml"></a>
+<!-- Creating a listener on Kubernetes using YAML -->
 ## Creating a listener using YAML
 
 A listener binds a local connection endpoint to connectors in remote sites. 
@@ -111,5 +115,86 @@ Listeners and connectors are matched using routing keys.
 
 There are many options to consider when creating connectors using YAML, see [CLI Reference][cli-ref], including *frequently used* options.
 
+
+<a id="kube-creating-attachedconnector-yaml"></a>
+## Creating a connector for a different namespace using YAML
+
+A connector binds a local workload to listeners in remote sites.
+
+If you create a site in one namespace and need to expose a service in a different namespace, use this procedure to create an *attached connector* in the other namespace and an *AttachedConnectorBinding* in the site namespace.
+
+* An attached connector is a connector in a peer namespace, that is, not the site namespace.
+* The AttachedConnectorBinding is a binding to an attached connector in a peer namespace and is created in the site namespace.
+
+**Procedure**
+
+1. Create a workload that you want to expose on the network in a non-site namespace, for example:
+   ```bash
+   kubectl create deployment backend --image quay.io/skupper/hello-world-backend --replicas 3
+   ```
+
+2. Create an AttachedConnector resource YAML file in the same namespace:
+   ```yaml
+   apiVersion: skupper.io/v2alpha1
+   kind: AttachedConnector
+   metadata:
+     name: backend
+     namespace: attached
+   spec:
+     siteNamespace: skupper
+     selector: app=backend
+     port: 8080
+   ```
+
+   To create the AttachedConnector resource:
+
+   ```bash
+   kubectl apply -f <filename>
+   ```
+
+   where `<filename>` is the name of a YAML file that is saved on your local filesystem.
+
+3. Create an AttachedConnectorBinding resource YAML file in the site namespace:
+   ```yaml
+   apiVersion: skupper.io/v2alpha1
+   kind: AttachedConnector
+   metadata:
+     name: backend
+     namespace: attached
+   spec:
+     siteNamespace: skupper
+     selector: app=backend
+     port: 8080
+   ```
+
+   To create the AttachedConnectorBinding resource:
+
+   ```bash
+   kubectl apply -f <filename>
+   ```
+
+   where `<filename>` is the name of a YAML file that is saved on your local filesystem.
+
+
+
+3. Check the AttachedConnectorBinding status from the context of the site namespace:
+   ```bash
+   kubectl get AttachedConnectorBinding
+   ```
+   
+   For example:
+   
+   ```
+   NAME      ROUTING KEY   CONNECTOR NAMESPACE   STATUS   HAS MATCHING LISTENER
+   backend   backend       attached              Ready    true
+   ```
+   **📌 NOTE**
+   By default, the routing key name is set to the name of the connector.
+   If you want to use a custom routing key, set the `--routing-key` to your custom name.
+
+There are many options to consider when creating connectors using YAML, see [CLI Reference][cli-ref], including *frequently used* options.
+
+
+
 [connector]: https://skupperproject.github.io/refdog/concepts/connector.html
 [listener]: https://skupperproject.github.io/refdog/concepts/listener.html

input/kube-yaml/site-configuration.md

@@ -1,10 +1,11 @@
+<a id="kube-creating-site-yaml"></a>
 # Creating a site on Kubernetes using YAML
 
 Using YAML allows you to create and manage sites from the context of the current namespace.
 
 A typical workflow is to create a site, link sites together, and expose services to the service network.
 
-
+<a id="kube-creating-simple-site-yaml"></a>
 ## Creating a simple site on Kubernetes using YAML
 
 You can use YAML to create and manage Skupper sites.