NetOps
The netop pods enforce the QoS Profile for a slice. It uses Linux TC (Traffic Control) for the slice traffic classification.
Getting Started
Please refer to our documentation on:
Prerequisites
Before you begin, make sure the following prerequisites are met:
Local Build and Update
Latest Docker Hub Image
docker pull aveshasystems/netops:latest
Setting up Your Helm Repo
If you have not added avesha helm repo yet, add it.
helm repo add avesha https://kubeslice.github.io/charts/
Upgrade the avesha helm repo.
helm repo update
Build docker images
- Clone the latest version of netops from the
master
branch.
git clone https://github.com/kubeslice/netops.git
cd netops
- Adjust the
VERSION
variable in the Makefile to change the docker tag to be built.
Image is set as docker.io/aveshasystems/netops:$(VERSION)
in the Makefile. Change this if required.
make docker-build
Running Locally on Kind Clusters
- You can load the netops image on your kind cluster using the following command:
kind load docker-image my-custom-image:unique-tag --name clustername
Example
kind load docker-image aveshasystems/netops:1.2.1 --name kind
- Check the loaded image in the cluster. Modify node name if required.
docker exec -it <node-name> crictl images
Example
docker exec -it kind-control-plane crictl images
Deploy in a Cluster
Update the chart values file called yourvaluesfile.yaml
that you have previously created.
Refer to values.yaml to create yourvaluesfiel.yaml
and update the netop image subsection to use the local image.
From the sample:
netop:
image: docker.io/aveshasystems/netops
tag: 0.1.0
Change it to:
netop:
image: <my-custom-image>
tag: <unique-tag>
Deploy the updated chart.
make chart-deploy VALUESFILE=yourvaluesfile.yaml
Verify the Installation
Verify the installation of NetOps by checking the status of pods belonging to the kubeslice-system
namespace.
kubectl get pods -n kubeslice-system | grep netop
Example output
avesha-netop-pnbbr 1/1 Running 0 4d23h
License
Apache 2.0 License.