Chapter 11. Creating a site on Kubernetes using YAML

Create a site CR YAML file named my-site.yaml, for example:

apiVersion: skupper.io/v2alpha1
kind: Site
metadata:
  name: my-site
  namespace: west

This YAML creates a site named my-site in the west namespace. Specifying the namespace is not required if the context is set to the namespace where you want to create the site.

If you need to link to this site, enable link access:

apiVersion: skupper.io/v2alpha1
kind: Site
metadata:
  name: my-site
  namespace: west
spec:
  linkAccess: default

Create the site:

kubectl apply -f my-site.yaml

Check the status of the site:

kubectl get site

You might need to issue the command multiple times before the site is ready:

$ kubectl get site
NAME   STATUS    SITES IN NETWORK   MESSAGE
west   Pending                      containers with unready status: [router kube-adaptor]
$ kubectl get site
NAME   STATUS   SITES IN NETWORK   MESSAGE
west   Ready    1                  OK

You can now link this site to another site to create an application network.

Create a sizing ConfigMap in the same namespace where your Skupper V2 controller is running.

The following example defines a sizing configuration named medium with 2 CPU cores suitable for production:

apiVersion: v1
kind: ConfigMap
metadata:
  name: sizing-medium
  labels:
    skupper.io/site-sizing: "medium"
  annotations:
    skupper.io/default-site-sizing: "true"
data:
  router-cpu-limit: "2"
  router-memory-limit: 1024Mi

The Skupper controller selects ConfigMaps based on the presence of a skupper.io/site-sizing label. The label’s value serves as an internal identifier for that particular sizing configuration.

To designate a sizing model as the default for all sites managed by your Skupper V2 controller instance, annotate the ConfigMap with skupper.io/default-site-sizing: "true".

A sizing ConfigMap can define the following fields:

Determine the controller namespace. Depending on your installation method, the controller namespace may be skupper, openshift-operators, or have a different name. You can check that you have chosen the correct namespace by running:

kubectl get pods

Confirm that the skupper controller pod is running in the namespace.

Apply the ConfigMap in the controller namespace:

kubectl apply -f sizing-medium.yaml

Assign the sizing configuration to a site by setting the spec.settings.size field in the site resource:

apiVersion: skupper.io/v2alpha1
kind: Site
metadata:
  name: my-site
spec:
  settings:
    size: medium

Verify the resource limits have been applied by inspecting the skupper-router deployment:

kubectl get deployment skupper-router -o json | jq .spec.template.spec.containers[].resources

The output should look like:

{
  "limits": {
    "cpu": "1",
    "memory": "1Gi"
  },
  "requests": {
    "cpu": "500m",
    "memory": "512Mi"
  }
}