Administering Red Hat OpenShift API Management

Procedure

1. Click the application launcher in OpenShift Dedicated.
2. Click API Management Dashboards in the OpenShift Managed Services drop-down menu.
3. You are prompted to log in. Click Log in with OpenShift.
4. Enter login credentials, if prompted.
5. Click Allow selected permissions to authorize monitoring access.
6. In the Grafana console, click the Dashboards dropdown menu from the main menu to access the available dashboards and folders.
7. Click Manage.
8. Click redhat-rhoam-customer-monitoring-operator to open the folder.

9. Click Rate Limiting to access the monitoring data.

   Note

   Alternatively, click Home to search for a dashboard by name.

Procedure

1. Log in to the cluster using the oc login command.

2. Use the following command to change the project:

   $ oc project <project_name>

   Copy to Clipboard Toggle word wrap

   where <project_name> is the name of a project that you want to accept communications from other projects.

3. Create a NetworkPolicy object:

   1. Create a allow-from-middleware-namespaces.yaml file.

   2. Define a policy in the file you just created, such as in the following example:

      apiVersion: networking.k8s.io/v1
      kind: NetworkPolicy
      metadata:
        name: allow-from-middleware-namespaces
      spec:
        podSelector:
        ingress:
          - from:
              - namespaceSelector:
                  matchLabels:
                    integreatly-middleware-service: 'true'

      Copy to Clipboard Toggle word wrap

   3. Run the following command to create the policy object:

      $ oc create -f allow-from-middleware-namespaces.yaml -n <project>
      
      networkpolicy "allow-from-middleware-namespaces" created

      Copy to Clipboard Toggle word wrap

Procedure

1. Log in to the cluster using the oc login command.

2. Use the following command to change the project:

   $ oc project <project_name>

   Copy to Clipboard Toggle word wrap

   where <project_name> is the name of a project that you want to accept communications from other projects.

3. Create a NetworkPolicy object:

   1. Create a NetworkPolicy.yaml file.

   2. Define a policy in the file you just created, such as in the following example.

      This policy enables incoming communication for all projects in the cluster:

      kind: NetworkPolicy
      apiVersion: networking.k8s.io/v1
      metadata:
        name: allow-all
      spec:
        podSelector:
        ingress:
        - {}

      Copy to Clipboard Toggle word wrap
      Note

      This policy configuration enables this project to communicate with all projects in the cluster.

   3. Run the following command to create the policy object:

      $ oc create -f <policy-name>.yaml -n <project>

      Copy to Clipboard Toggle word wrap

Procedure

1. Log in to the cluster using the oc login command.

2. Use the following command to change the project:

   $ oc project <project_name>

   Copy to Clipboard Toggle word wrap

   <project_name> is the name of a project that you want to accept communications from.

3. Create a NetworkPolicy object:

   1. Create a allow-from-myproject-namespace.yaml file.

   2. Define a policy in the file you just created, such as in the following example.

      This policy enables incoming communication for a specific project (myproject):

      apiVersion: networking.k8s.io/v1
      kind: NetworkPolicy
      metadata:
        name: allow-from-myproject-namespace
      spec:
        podSelector:
        ingress:
          - from:
              - namespaceSelector:
                   matchLabels:
                     project: myproject

      Copy to Clipboard Toggle word wrap

4. Run the following commands to create the policy object:

   $ oc create -f allow-from-myproject-namespace.yaml -n <project>
   networkpolicy "allow-from-myproject-namespace" created

   Copy to Clipboard Toggle word wrap

Procedure

1. Log in to the cluster using the oc login command.

2. Use the following command to change the project:

   $ oc project <project_name>

   Copy to Clipboard Toggle word wrap

   where <project_name> is the name of a project that you want to isolate from the managed services.

3. Create a NetworkPolicy object:

   1. Create a deny-all.yaml file.

   2. Define a policy in the file you just created, such as in the following example:

      kind: NetworkPolicy
      apiVersion: networking.k8s.io/v1
      metadata:
        name: deny-all
      spec:
        podSelector: {}
        ingress:
          - from:
              - namespaceSelector:
                  matchLabels:
                    integreatly-middleware-service: 'true'

      Copy to Clipboard Toggle word wrap

   3. Run the following command to create the policy object:

      $ oc create -f <policy-name>.yaml -n <project>

      Copy to Clipboard Toggle word wrap

Procedure

1. Navigate to [Your_product_name] > Integration > Methods & Metrics or [Your_backend_name] > Methods & Metrics.
2. Click New method.

3. In the Friendly name field, enter a short description of the method. This name is displayed in different sections of the 3scale Admin Portal. The friendly name must be unique for the product.

   Important

   Be careful with changing the system name of the methods or deleting them. These changes can break your already deployed 3scale integration if there are mapping rules pointing to the previous system name of the method.

4. In the System name field, enter the name of the method in your API to use to report the usage through the 3scale Service Management API. The system name must conform to these rules:

   • Unique in the product or backend
   • Contain only alphanumeric characters, underscore _, hyphen - or forward slash /
   • No spaces

   Otherwise, you are free to decide what the system name looks like. It can be the same as the endpoint (/status), or, for example, it can include the method and the path (GET_/status).

5. Optional: In the Description field, enter a more detailed description of the method.
6. Click Create Method.

Procedure

1. Navigate to [Your_product_name] > Integration > Methods & Metrics or [Your_backend_name] > Methods & Metrics.
2. Click New metric.

3. In the Friendly name field, enter a short description of the metric. This name is displayed in different sections of the 3scale Admin Portal. The friendly name must be unique for the product.

   Important

   Be careful with changing the system name of the metrics or deleting them. These changes can break your already deployed 3scale integration if there are mapping rules pointing to the previous system name of the metric.

4. In the System name field, enter the name of the metric in your API to use to report the usage through the 3scale Service Management API. The system name must conform to these rules:

   • Unique in the product or backend
   • Contain only alphanumeric characters, underscore _, hyphen - or forward slash /
   • No spaces

   Otherwise, you are free to decide what the system name looks like.

5. In the Unit field, enter the unit.

   • Use a singular noun, for example, hit. The singular will become plural in the analytics charts.
6. Optional: In the Description field, enter a more detailed description of the metric.
7. Click Create Metric.

Procedure

1. Navigate to [Your_product_name] > Integration > Mapping Rules.
2. Click Add Mapping Rule.
3. The Verb field is pre-populated with the HTTP method, GET, however you can select other options from the dropdown list.
4. In the Pattern field, add a valid URL that starts with an forward slash /. The URL can be from a wildcard you specified inside curly brackets {}.
5. In the Metric or Method to increment field, select from one of your previously created methods or metrics.
6. The Increment by field is pre-populated with 1, however, change this to suit your own needs.
7. Click the Create Mapping Rule button.