Paul Wright pwright

Template for CR and route YAMLs

./create.py api-controller.template api-controller.yaml values.yaml

Generating cURL Commands Using VSCode and the REST Client Extension

Manually crafting cURL commands can be tedious and error-prone, especially for complex HTTP requests. A more efficient method involves using Visual Studio Code (VSCode) with the REST Client extension. This approach allows you to easily set up, test, and validate your HTTP requests before converting them into cURL commands. Here's how you can do it:

Prerequisites

Visual Studio Code installed on your computer.
REST Client Extension by Huachao Mao installed in VSCode. You can download it from the VSCode Marketplace .

Installing
Introduction to API Controller
- Understanding the API Controller
- Integration of {studio} with {registry}
- Supported API and schema types
- Applying policies to an API
Getting started with {studio}
Creating an API design

User:

create a diagram showing how skupper links are created between a site with a token and a site with ingress. After establishing the link you can expose services from either site and consume any exposed service from the other site.

ChatGPT:

Sure, let's start by breaking down what we are trying to visualize:

Two sites: one with a token and another with ingress. The creation of Skupper links between these two sites.

High Availability Skupper router

When you create a site you can specify the number of Skupper routers provisioned, for example skupper init --routers 2. This can seem an attractive option, to ensure that traffic flows even if a Skupper router fails. However, there is no guarantee that traffic flow is balanced across the routers and the traffic flow distribution might be unexpected. NOTE: The high availability discussed here is not related to exposed traffic load balancing and failover, which is described in .

Skupper recommends increasing memory and CPU allocation to the Skupper router, rather than the number of Skupper routers to maximise resiliency.

Skupper console and flow collector component

With Skupper 1.3, a new console is available which allows you to monitor flows across your network. This console requires a process that is not enabled by default (--enable-flow-collector to enable)

This is a feature preview and not suitable for deployment in production. The Skupper team are working hard to simplify and improve the experience, expect changes over the next few releases.

To activate the new console, you should skupper init --enable-console --enable-flow-collector on one site only to avoid unnecessary resource usage. The single flow collector has access to data from all connected sites.

Sign up for dev sandbox at https://developers.redhat.com/
Click >_ to start terminal:
Get skupper cli using curl: curl --output skupper https://raw.githubusercontent.com/pwright/Waterworld/master/skupper
Use skupper.

NOTE: For later versions of skupper, host the binary somewhere and curl it, no tar commands available from OpenShift terminal.

Debugging Skupper

Initializing

The first step with skupper is typically skupper init and after waiting for some time, skupper status with the following output:

Skupper enabled for namespace 'west'

	�PNG

	IHDR \e IDATx�}w\T��]��TS�ݨ� �Į�\��$�\��ł
	j�{�-V�f (M��-�,��>�\|ATl�?`vΜ)�<�y��=8p� �NB�y'G� ��(8��N<7l8p��8��;:�ܰ9p� �18p� ��B�c��s�� A��8� �A��;
	�� p��(8��N<7l8p��8��;:�ܰ9p� �18p� ��B�c��s�� A��8� �A��;
	�� p��(8��N<7l8p��8��;:�ܰ9p� �18p� ��B�c��s�� A��s2��T�K��D��n?q��
	�FB]�N��^��UP\�a��x��ਮs췴�L/�&��Ϻj�*�e�Yۭe�u^�u��Y�}��:��U0�F�^��<Lf��0I�{�O��S?�e��$Q�ϩ��
	�2A�$j�93��~R��^0A�{b=��A��'~b�33v�i�`�xbo�0Ӥ9�YWMP��L<k�U�E U��6��\|�y�v��^��'��l�~�j�\|u��&��W�o�9��S�& ��g�ʛ��R�5��܍�`�KϺ�h`/��.��ݨ}�ouI��u��A�RU��r��!�W�\�[.��B�0��D~�枇��&�I�5��%��5]W�UWu��nu��Zv��S�枻��0��V�S�I��ڢ�MU+1)P˟U�AN-?j��Z�ShR�:8<k�I�$� ��? ��~U]�33��t&ͳ��8k(�.�2��e��2��TN��L�\|N?��
	��jxk2(�L�\|��LO��+P'0;��ߨJ04

	jq -Rs '.' input.json > min.json

	jq -r 'fromjson' min.json