Skip to content
Snippets Groups Projects
Commit e5f91276 authored by Alex ubuntu vm's avatar Alex ubuntu vm
Browse files

l2sm net crd: added instructions of deployment

parent 85f0dbb8
No related branches found
No related tags found
1 merge request!2repo: added new directory where utils scripts will be
...@@ -37,6 +37,7 @@ kubectl create -f ./deployments/custom-installation/mysql/ ...@@ -37,6 +37,7 @@ kubectl create -f ./deployments/custom-installation/mysql/
kubectl get nodes kubectl get nodes
kubectl label nodes [your-master-node] dedicated=master kubectl label nodes [your-master-node] dedicated=master
``` ```
5. Deploy the L2S-M Controller by using the following command: 5. Deploy the L2S-M Controller by using the following command:
```bash ```bash
...@@ -49,7 +50,7 @@ kubectl create -f ./deployments/custom-installation/deployController.yaml ...@@ -49,7 +50,7 @@ kubectl create -f ./deployments/custom-installation/deployController.yaml
kubectl create -f ./deployments/custom-installation/deployOperator.yaml kubectl create -f ./deployments/custom-installation/deployOperator.yaml
``` ```
Once these two pods are in running state, you can finally deploy the virtual switches Once these two pods are in running state, you can finally deploy the virtual switches and custom CRD
7. This is done by: 7. This is done by:
...@@ -60,6 +61,11 @@ kubectl create -f ./deployments/custom-installation/deploySwitch.yaml ...@@ -60,6 +61,11 @@ kubectl create -f ./deployments/custom-installation/deploySwitch.yaml
And check there is a pod running in each node, with ```kubectl get pods -o wide``` And check there is a pod running in each node, with ```kubectl get pods -o wide```
8. And launch the CRD definition by:
```bash
kubectl create -f ./deployments/custom-installation/l2sm-network-crd.yaml
```
## Configuring Vxlans ## Configuring Vxlans
Each node enables the creation of custom L2S-M networks, as can be seen in the [examples section](../../examples/) section. But for communicating pods that are in different Nodes of the cluster, additional configuration must be done, of configuring the Vxlan tunnels between them. Each node enables the creation of custom L2S-M networks, as can be seen in the [examples section](../../examples/) section. But for communicating pods that are in different Nodes of the cluster, additional configuration must be done, of configuring the Vxlan tunnels between them.
......
...@@ -416,5 +416,44 @@ spec: ...@@ -416,5 +416,44 @@ spec:
add: ["NET_ADMIN"] add: ["NET_ADMIN"]
nodeSelector: nodeSelector:
kubernetes.io/arch: amd64 kubernetes.io/arch: amd64
---
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
name: l2sm-networks.l2sm.k8s.local
spec:
group: l2sm.k8s.local
versions:
- name: v1
served: true
storage: true
schema:
openAPIV3Schema:
type: object
properties:
spec:
type: object
properties:
type:
type: string
config:
type: string
nullable: true
signature:
type: string
nullable: true
status:
type: object
properties:
connectedPods:
type: array
items:
type: string
scope: Namespaced
names:
plural: l2sm-networks
singular: l2sm-network
kind: L2SMNetwork
shortNames:
- l2sm-net
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment