Installation

Procedure

1. Download binary files for Linux, macOS or Windows, choose the latest Version for 1.8 at Software Downloads.

   For a Mac with Apple silicon, use Rosetta 2 and the Skupper CLI for Mac on x86-64 download.

2. Unzip the downloaded file and place the Skupper executable on your PATH.

3. Verify installation:

   $ skupper version
   client version                 1.8.2-rh-1

Procedure

1. Use the subscription-manager command to subscribe to the required package repositories. Replace <version> with 1 for the main release stream or 1.4 for the long term support release stream.

   Note

   Replacing <version> with 1 installs 1.8, while 1.8 is the main release stream and changes after further releases.

   Red Hat Enterprise Linux 8

   $ sudo subscription-manager repos --enable=service-interconnect-_<version>_-for-rhel-8-x86_64-rpms

   Red Hat Enterprise Linux 9

   $ sudo subscription-manager repos --enable=service-interconnect-_<version>_-for-rhel-9-x86_64-rpms

   1. Use the yum or dnf command to install the skupper command:

      $ sudo dnf install skupper-cli

Procedure

1. Log in as a cluster administrator.
2. Complete the steps described in Red Hat Container Registry Authentication.

3. Create a file named subscription-all.yaml with the following:

   apiVersion: operators.coreos.com/v1alpha1
   kind: Subscription
   metadata:
     name: skupper-operator
     namespace: openshift-operators
   spec:
     channel: stable-1
     installPlanApproval: Automatic
     name: skupper-operator
     source: redhat-operators
     sourceNamespace: openshift-marketplace
     startingCSV: skupper-operator.v1.8.1-rh-3

   Note

   If you want to keep updates confined to 1.8.x releases, set the value of channel to stable-1.8.

   If you do not specify startingCSV, the subscription defaults to the latest operator version.

   If you specify installPlanApproval as Manual, sites are not automatically upgraded to the latest version of Service Interconnect. See Chapter 4, Upgrading the Red Hat Service Interconnect Operator and sites for information on manually upgrading sites.

4. Apply the subscription YAML:

   $ kubectl apply -f subscription-all.yaml

Procedure

1. Log in as a cluster administrator.
2. Complete the steps described in Red Hat Container Registry Authentication.

3. Create an Operator group in the namespace where you want to create a site:

   1. Create a file named operator-group.yaml with the following:

      kind: OperatorGroup
      apiVersion: operators.coreos.com/v1
      metadata:
        name: skupper-operator
        namespace: my-namespace
      spec:
        targetNamespaces:
        - my-namespace

      where my-namespace is the name of the namespace you want to create the site.

   2. Apply the Operator group YAML:

      $ kubectl apply -f operator-group.yaml

4. Create a file named subscription-myns.yaml with the following:

   apiVersion: operators.coreos.com/v1alpha1
   kind: Subscription
   metadata:
     name: skupper-operator
     namespace: my-namespace
   spec:
     channel: stable-1
     installPlanApproval: Automatic
     name: skupper-operator
     source: redhat-operators
     sourceNamespace: openshift-marketplace
     startingCSV: skupper-operator.v1.8.1-rh-3

   where my-namespace is the name of the namespace you want to create the site.

   Note

   If you want to keep updates confined to 1.8.x releases, set the value of channel to stable-1.8.

   If you do not specify startingCSV, the subscription defaults to the latest operator version.

   If you specify installPlanApproval as Manual, sites are not automatically upgraded to the latest version of Service Interconnect. See Chapter 4, Upgrading the Red Hat Service Interconnect Operator and sites for information on manually upgrading sites.

5. Apply the subscription YAML:

   $ kubectl apply -f subscription-myns.yaml

Procedure

1. In the OpenShift web console, navigate to Operators → OperatorHub.
2. Choose Red Hat Service Interconnect Operator from the list of available Operators, and then click Install.

3. On the Operator Installation page, two Installation mode options are available:

   • All namespaces on the cluster

   • A specific namespace on the cluster

     For this example, choose A specific namespace on the cluster.

4. Choose an Update approval option.

   By default, Automatic approval is selected, and sites will upgrade to the latest version of Service Interconnect. If you choose Manual approval, sites will not be automatically upgraded to the latest version of Service Interconnect. See Chapter 4, Upgrading the Red Hat Service Interconnect Operator and sites for information on manually upgrading sites.

5. Select the namespace into which you want to install the Operator, and then click Install.

   The Installed Operators page appears displaying the status of the Operator installation.

6. Verify that the Red Hat Service Interconnect Operator is displayed and wait until the Status changes to Succeeded.

7. If the installation is not successful, troubleshoot the error:

   1. Click Red Hat Service Interconnect Operator on the Installed Operators page.
   2. Select the Subscription tab and view any failures or errors.

Procedure

1. Go to access.redhat.com.
2. If you do not already have an account, create one.
3. Log in to your account.

Procedure

1. Go to access.redhat.com.
2. Navigate to My Subscriptions.
3. Navigate to Activate a subscription and enter your 16-digit activation number.

Procedure

1. Go to access.redhat.com.
2. Navigate to Registration Assistant.
3. Select your OS version and continue to the next page.
4. Use the listed command in your system terminal to complete the registration.

1. Determine the router CPU allocation you require.

   By default, the router CPU allocation is BestEffort as described in Pod Quality of Service Classes.

   Consider the following CPU allocation options:

   Router CPU	Description
   1	Helps avoid issues with BestEffort on low resource clusters
   2	Suitable for production environments
   5	Maximum performance

2. If you are using the Skupper CLI, set the CPU allocation for the router using the --router-cpu option. For example:

   $ skupper init --router-cpu 2

3. If you are using YAML, set the CPU allocation for the router by setting a value for the router-cpu attribute. For example:

   apiVersion: v1
   kind: ConfigMap
   metadata:
     name: "skupper-site"
   data:
     name: "my-site"
     router-cpu: 2

1. If you are using the Skupper CLI, set the number of routers to 2 using the --routers option:

   $ skupper init --routers 2

2. If you are using YAML, set the number of routers to 2 by setting the routers attribute:

   apiVersion: v1
   kind: ConfigMap
   metadata:
     name: "skupper-site"
   data:
     name: "my-site"
     routers: 2