Remove meridio-operator references in documentation

Author: LionelJouin

docs/deployment.md

@@ -4,6 +4,6 @@
 
 TODO
 
-## [Operator](https://github.com/Nordix/Meridio-Operator)
+## [Operator]()
 
 TODO

docs/deployment/operator.md

@@ -1,71 +1,14 @@
 # Meridio-Operator
 
-[Meridio](https://github.com/Nordix/Meridio)
-
-## Build
-
-The following parameters can be configured when building the operator image:
-* IMG: specify the image tag, default is "controller:0.0.1"
-* BUILDER: specifiy the image used in the binary compling phase, default is "golang:1.16"
-* BASE_IMG: the final base image, default is "ubuntu:18.04"
-
-```bash
-# build the image
-make docker-build
-# Make the image available for the cluster to use. The following commands are alternative
-make docker-push  # Push the image to a registry
-make kind-load  # Load the image to kind cluster
-```
-
-## Deploy
-
-### Deploy spire
-
-Spire is used by Meridio-Operator for provisioning tHe TLS certificates for the kubeapi server.
-
-```bash
-kubectl apply -k <Meridio>/docs/demo/deployments/spire
-```
-
-Spire will be deployed in "spire" namespace. Wait until the spire server and agent pods are running to continue deploying Meridio-Operator.
-
-**Note**: certmanager can also be used for the same purpose. To switch from spire to certmanager, you need to comment out all the sections with "[SPIRE]" comment and uncomment all the sections with "[CERTMANAGER]" comment in *config* directory.
-
-### Deploy Meridio-Operator
-
-Meridio-Operator is a namespace-scoped operator, which watches and manages custom resources in a single namespace where the operator is deployed.
-
-The following parameters can be set when you deploy Meridio-Operator:
-* NAMESPACE: specify the namespace where the Meridio-Operator resources will be deployed, default is "meridio-operator-system".
-* ENABLE_MUTATING_WEBHOOK: enable the mutating webhook to mutate the Cutstom Resources which will be created to configure Meridio-Operator, so that specific fields can be left out and use default values, default is true.
-* IMG: specify the image that Meridio-Operator deployment will use, default is controller:0.0.1
-
-```bash
-make deploy
-```
-
-### Run tests
-
-Running e2e tests requires the Meridio-Operator already deployed in the cluster.
-
-The following parameters are expected to be the same as what are configured when Meridio-Operator is deployed:
-* NAMESPACE: specify the namespace where the Meridio-Operator resources will be deployed, default is "meridio-operator-system".
-* ENABLE_MUTATING_WEBHOOK: enable the mutating webhook to mutate the Cutstom Resources which will be created to configure Meridio-Operator, so that specific fields can be left out and use default values, default is true.
-
-```bash
-# Run e2e test in the namespace "red"
-make e2e NAMESPACE="red"
-```
-
 ## Configuration
 
 **The Meridio-Operator is deployed in the "default" namespace in the examples below.**
 
 ### Trench
 
-A [trench](https://github.com/Nordix/Meridio-Operator/blob/master/config/samples/meridio_v1alpha1_trench.yaml) spawns the IPAM, NSP pods, and needed role, role-binding and service accounts, and the ConfigMap storing configuration of the trench. The resources created by a trench will be suffixed with the trench's name.
+A [trench](https://github.com/Nordix/Meridio/blob/master/config/samples/meridio_v1alpha1_trench.yaml) spawns the IPAM, NSP pods, and needed role, role-binding and service accounts, and the ConfigMap storing configuration of the trench. The resources created by a trench will be suffixed with the trench's name.
 
-To see how to configure a trench, please refer to [trench spec](https://pkg.go.dev/github.com/nordix/meridio-operator/api/v1alpha1#TrenchSpec).
+To see how to configure a trench, please refer to [trench spec](https://pkg.go.dev/github.com/nordix/meridio/api/v1alpha1#TrenchSpec).
 
 ```bash
 $ kubectl apply -f ./config/samples/meridio_v1alpha1_trench.yaml
@@ -102,7 +45,7 @@ To be noted, meridio-operator currently have a limitation to have one attractor
 
 An attractor is a resource needs to be created with label. `metadata.labels.trench` specifies the owner trench of the attractor.
 
-To see how to configure and read the status of an attractor, please refer to [attractor spec](https://pkg.go.dev/github.com/nordix/meridio-operator/api/v1alpha1#AttractorSpec) and [attractor status](https://pkg.go.dev/github.com/nordix/meridio-operator/api/v1alpha1#AttractorStatus).
+To see how to configure and read the status of an attractor, please refer to [attractor spec](https://pkg.go.dev/github.com/nordix/meridio/api/v1alpha1#AttractorSpec) and [attractor status](https://pkg.go.dev/github.com/nordix/meridio/api/v1alpha1#AttractorStatus).
 
 ```bash
 kubectl apply -f ./config/samples/meridio_v1alpha1_attractor.yaml
@@ -127,7 +70,7 @@ attr1   eth0.100         nsm-vlan         ["gateway1","gateway2"]   ["vip1","vip
 
 A gateway is a resource to describe the gateway information for the Meridio Front-ends.It must be created with label `metadata.labels.trench` to specify its owner reference trench.
 
-To see how to configure and read the status of a gateway, please refer to [gateway spec](https://pkg.go.dev/github.com/nordix/meridio-operator/api/v1alpha1#GatewaySpec) and [gateway status](https://pkg.go.dev/github.com/nordix/meridio-operator/api/v1alpha1#GatewayStatus).
+To see how to configure and read the status of a gateway, please refer to [gateway spec](https://pkg.go.dev/github.com/nordix/meridio/api/v1alpha1#GatewaySpec) and [gateway status](https://pkg.go.dev/github.com/nordix/meridio/api/v1alpha1#GatewayStatus).
 
 In the example below, two gateways will be created.
 
@@ -146,7 +89,7 @@ gateway2   1000::1   bgp        trench-a
 
 A Vip is a resource to reserving the destination addresses for the target applications.It must be created with label `metadata.labels.trench` to specify its owner reference trench.
 
-To see how to configure and read the status of a Vip, please refer to [Vip spec](https://pkg.go.dev/github.com/nordix/meridio-operator/api/v1alpha1#VipSpec) and [Vip status](https://pkg.go.dev/github.com/nordix/meridio-operator/api/v1alpha1#VipStatus).
+To see how to configure and read the status of a Vip, please refer to [Vip spec](https://pkg.go.dev/github.com/nordix/meridio/api/v1alpha1#VipSpec) and [Vip status](https://pkg.go.dev/github.com/nordix/meridio/api/v1alpha1#VipStatus).
 
 In the example below, two Vips will be created.
 
@@ -166,7 +109,7 @@ vip2   10.0.0.1/32   trench-a
 A Conduit is for configuring the load balancer type. It must be created with label `metadata.labels.trench` to specify its owner reference trench.
 There is a limitation that a conduit must be created when one attractor is created in the same trench. Meridio only supports one conduit per trench now.
 
-To see how to configure and read the status of a Conduit, please refer to [Conduit spec](https://pkg.go.dev/github.com/nordix/meridio-operator/api/v1alpha1#ConduitSpec) and [Conduit status](https://pkg.go.dev/github.com/nordix/meridio-operator/api/v1alpha1#ConduitStatus).
+To see how to configure and read the status of a Conduit, please refer to [Conduit spec](https://pkg.go.dev/github.com/nordix/meridio/api/v1alpha1#ConduitSpec) and [Conduit status](https://pkg.go.dev/github.com/nordix/meridio/api/v1alpha1#ConduitStatus).
 
 A Conduit can be created by following the example below.
 
@@ -195,7 +138,7 @@ conduit-stateless   stateless-lb   trench-a
 
 A Stream is for grouping different flows, and it can choose how traffic is load balanced by registering for a specific conduit. It must be created with label `metadata.labels.trench` to specify its owner reference trench.
 
-To see how to configure and read the status of a Stream, please refer to [Stream spec](https://pkg.go.dev/github.com/nordix/meridio-operator/api/v1alpha1#StreamSpec) and [Stream status](https://pkg.go.dev/github.com/nordix/meridio-operator/api/v1alpha1#StreamStatus).
+To see how to configure and read the status of a Stream, please refer to [Stream spec](https://pkg.go.dev/github.com/nordix/meridio/api/v1alpha1#StreamSpec) and [Stream status](https://pkg.go.dev/github.com/nordix/meridio/api/v1alpha1#StreamStatus).
 
 A Stream can be created by following the example below.
 
@@ -213,7 +156,7 @@ stream-1   conduit-stateless   trench-a
 
 A Flow enables the traffic to a selection of pods by specifying the 5-tuples and the Stream the traffic go through. It must be created with label `metadata.labels.trench` to specify its owner reference trench.
 
-To see how to configure and read the status of a Flow, please refer to [Flow spec](https://pkg.go.dev/github.com/nordix/meridio-operator/api/v1alpha1#FlowSpec) and [Flow status](https://pkg.go.dev/github.com/nordix/meridio-operator/api/v1alpha1#FlowStatus).
+To see how to configure and read the status of a Flow, please refer to [Flow spec](https://pkg.go.dev/github.com/nordix/meridio/api/v1alpha1#FlowSpec) and [Flow status](https://pkg.go.dev/github.com/nordix/meridio/api/v1alpha1#FlowStatus).
 
 A Flow can be created by following the example below.
 
@@ -248,7 +191,7 @@ spec:
 
 For each container making up a specific custom resource (e.g. Trench) the annotation value for key _resource-template_ is interpreted as the name of a resource requirements template. Such templates are defined per container, and are to be specified before building the Operator.
 
-As an example some [templates](https://github.com/Nordix/Meridio-Operator/tree/master/config/manager/resource_requirements/) are included for each container out-of-the-box. But they are not verified to fit any production use cases, and can be overridden at will. (A template is basically a kubernetes [core v1 ResourceRequirements](https://pkg.go.dev/k8s.io/[email protected]/core/v1#ResourceRequirements) block with name.)
+As an example some [templates](https://github.com/Nordix/Meridio/tree/master/config/manager/resource_requirements/) are included for each container out-of-the-box. But they are not verified to fit any production use cases, and can be overridden at will. (A template is basically a kubernetes [core v1 ResourceRequirements](https://pkg.go.dev/k8s.io/[email protected]/core/v1#ResourceRequirements) block with name.)
 
 The Operator looks up the templates based on the annotation value for each container contributing to the particular custom resource. If a template is missing for a container, then deployment proceeds without setting resource requirements for the container at issue. Otherwise the related resources will be deployed by importing the respective resource requirements from the matching templates.
 

docs/trouble-shooting/README.md

@@ -1,8 +1,6 @@
 # Meridio - Troubleshooting Guide
 
-This guide focuses on `Meridio`, the
-[Meridio-operator](https://github.com/Nordix/Meridio-Operator) is only
-briefly touched.
+This guide focuses on `Meridio`, the Operator is only briefly touched.
 
 To be able to troubleshoot *anything* you must know how it works when
 everything is OK. So try to follow this guide, check the logs and use

readme.md

@@ -48,13 +48,6 @@ As the current default network service, a **no-NAT stateless Load-Balancer** is
 
 Meridio users have the flexibility to **adjust the network services on the fly** as they desire. Traffic `attractors`, `streams` gathering traffic into logical groups and traffic classifiers (`flows`) can be added, removed and updated without any redeployment of the resources, and with no traffic disturbance. Individually, each user pods have the ability to **select the traffic to consume at runtime** which will produce secondary network reorganization to cover the user pods needs and requests.
 
-
-## Meridio Operator
-
-An operator is available to provide a very easy and user friendly way to create, configure and manage the different concepts Meridio offers.
-
-https://github.com/Nordix/Meridio-Operator
-
 ## Community
 
 ### Slack