Chapter 6. Deploying a single logical service across many sites for failover

Procedure

1. Create sites by using skupper init.
2. Deploy your servers on different sites.

3. Generate a token on the first site:

   $ skupper token create token.yaml

   Copy to Clipboard Toggle word wrap

   This file contains a key and the location of the site that created it.

   Note

   Access to this file provides access to the service network. Protect it appropriately.

4. Use the token on the cluster that you want to connect from:

   To create a link to the first site:

   $ skupper link create token.yaml --cost 99999

   Copy to Clipboard Toggle word wrap

   The high cost setting means that traffic is not directed to this site under normal circumstances. However, if there is no other server available, all traffic is directed to this site.

5. Expose the servers on the service network for both sites.

   1. Create the service:

      $ skupper service create <name> <port>

      Copy to Clipboard Toggle word wrap

      where

      • <name> is the name of the service you want to create.
      • <port> is the port the service uses.

      By default, this service is now visible on both sites, although there is no server available to process requests to this service.

      Note

      By default, if you create a service on one site, it is available on all sites. However, if enable-service-sync is set to false you need to create the service on both sites.

   2. Bind the service with the server on both sites.

      $ skupper service bind <service-name> <target-type> <target-name>

      Copy to Clipboard Toggle word wrap

      where

      • <service-name> is the name of the service on the service network
      • <target-type> is the object you want to expose, deployment, statefulset, pods, or service.
      • <target-name> is the name of the cluster service

      For example:

      $ skupper service bind hello-world-backend deployment hello-world-backend

      Copy to Clipboard Toggle word wrap
6. You can use the console to check the traffic flow or monitor the services using your tooling. Clients can connect to either site, and the server on that site processes the requests until the server is not available. Further requests are processed by the server on the other site.