Deploy

Deploy your CNI plugin

Fury Kubernetes modules are deployed via the furyctl command line tool.

Packages are then customized with kustomize. It lets you create customized Kubernetes resources based on other Kubernetes resource files, leaving the original YAML untouched. To learn how to create you own customization layer with it, please see the kustomize repository.

Requirements

To deploy the Fury Kubernetes Monitoring module, you need the following

Compatibility

Module Version / Kubernetes Version 1.14.X 1.15.X 1.16.X 1.17.X 1.18.X
v1.0.0
v1.0.1
v1.1.0
v1.2.0
v1.2.1
v1.3.0
  • Compatible
  • Has issues
  • Incompatible

Deployment

To start using Fury Kubernetes Monitoring, you need to use the furyctl command line tool and create a Furyfile.yml with the list of all the packages you want to download.

You can download the packages for a full monitoring stack including Prometheus Operator, Prometheus, Alertmanager, node-exporter, kube-state-metrics and Grafana using the following Furyfile.yml :

bases:
  - name: networking/calico
    version: "v1.3.0"

and execute

$ furyctl vendor

to download the packages under ./vendor/katalog/networking.

See furyctl documentation for details about Furyfile.yml format.

To deploy the packages to your cluster, define a kustomization.yaml with the following content:

bases:
- ./vendor/katalog/networking/calico

and execute

$ kustomize build . | kubectl apply -f -

See kustomize documentation for details about kustomization.yaml format.

Custom deployment

Different pod network cidr

If the cluster has another pod network cidr different than 172.16.0.0/16 you can create a patch.yaml file:

apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: calico-node
spec:
  template:
    spec:
      containers:
        - name: calico-node
          env:
          - name: CALICO_IPV4POOL_CIDR
            value: "192.168.0.0/16" # PUT YOUR NETWORK CIDR HERE

Adding the following section to your kustomization.yaml file:

patchesStrategicMerge:
  - patch.yaml

final kustomization.yaml file should looks like:

bases:
  - ./vendor/katalog/networking/calico

patchesStrategicMerge:
  - patch.yaml

The rendered manifests contains the new CALICO_IPV4POOL_CIDR value.


Last modified 25.06.2020: Updating module references (82f9ca7)