How to set ingress controller to handle the external traffic while skupperV2 installation in OpenShift cluster

[vishavjeet somwanshi]

Hi Team,

We have upgraded skupper in our development environment from Skupper V1 to V2 which is working fine as development environment is public link cluster. Now, we are proceeding further with higher environment which are private link clusters where to access them outside we have created ingress controllers ( public router ). I have gone the V2 installation documentation which quite different compare to V1. V2 has different method to create a skupper site so where should we define the ingress controller while creating a respective skupper site ?

As we see in Skupper V1 while installing skupper with ingress-host there the command skupper init --ingress-host <hostname_or_ip_address> which is used to initialize a Skupper site and explicitly specify the hostname or IP address that should be used for ingress.

here is the minimal configuration as per the documentation for V2:

apiVersion: skupper.io/v2alpha1
kind: Site
metadata:
  name: skupper-qa
  namespace: skupper-qa
spec:
  linkAccess: default
  serviceaccount: skupper-router

I could see that we can set the linkAccess to either route or loadbalancer

I've noticed one issue, sometimes while issuing token using "skupper token issue" command it takes longer time and throw below warning. Accessgrant stuck in pending state.

$ skupper token issue token.yaml --redemptions-allowed 2 --timeout 10m0s

Waiting for token status ...

grant "skupper-qa-771fc12a-7733-4575-9359-b338aafdd848" not ready yet, check the status for more information

$ oc get grant

NAME                                              REDEMPTIONS ALLOWED   REDEMPTIONS MADE   EXPIRATION             STATUS    MESSAGE

skupper-qa-771fc12a-7733-4575-9359-b338aafdd848   2                                        2025-08-25T13:47:14Z   Pending   Pending

Thanks,

Vishavjeet S

[Fernando Giorgetti]

At present, the default Skupper V2 deployment YAML does not specify the enabled access types, which causes the
Controller to allow only the default values, which are: local, loadbalancer and route.

If you want to use an Nginx Ingress, you need to enable it, by adding the following environment variable
to the controller container, which enables the ingress-nginx option in the controller:

- name: SKUPPER_ENABLED_ACCESS_TYPES
 value: local,loadbalancer,route,ingress-nginx

After the ingress-nginx entry is allowed, you need to create your site definition using a YAML definition, like:

apiVersion: skupper.io/v2alpha1
kind: Site
metadata:

  name: my-site
  namespace: my-namespace
spec:
  linkAccess: ingress-nginx

With Skupper V2 you can use a declarative approach to manage your resources as you can
benefit from using native tools like kubectl or gitops, instead of relying only on the CLI.

All the different ingress types will be properly supported and documented soon.

--
You received this message because you are subscribed to the Google Groups "Skupper" group.
To unsubscribe from this group and stop receiving emails from it, send an email to skupper+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/skupper/bfa55937-b665-4f0e-8b57-25f2218115een%40googlegroups.com.

--

Fernando Giorgetti

Red Hat

fgio...@redhat.com   

[Fernando Giorgetti]

One more thing.

You will also need to specify the SKUPPER_INGRESS_DOMAIN environment variable, with the desired domain.

Thanks,

[vishavjeet somwanshi]

Thanks Fernando.

Yes we are using kustomize method for skupper setup and ArgoCD.

So, to enable the ingress controller, I need to enable the below env variables.

- name: SKUPPER_ENABLED_ACCESS_TYPES

value: local,loadbalancer,route,ingress-nginx

- name: SKUPPER_INGRESS_DOMAIN

value: <ingress-host-domain>

Regards,

Vishavjeet N. Somwanshi

+91 8888202485