The Red Hat Ecosystem Catalog is the official source for discovering and learning more about the Red Hat Ecosystem of both Red Hat and certified third-party products and services.
We’re the world’s leading provider of enterprise open source solutions—including Linux, cloud, container, and Kubernetes. We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

A10 Thunder Kubernetes Connector monitors the pod services,secrets, configmap,and A10 resource CRD in a Kubernetes or OpenShift cluster and configures the ACOS ADC configuration.
The A10 Thunder Kubernetes Connector monitors the pod and service activities in OpenShift cluster. All the pods, deployments or services inside a OpenShift cluster send messages to the API server when they start, stop or move. The API server then communicates these changes to Thunder Kubernetes Connector using REST API.
Thunder ADC is usually deployed externally to OpenShift cluster. The information received by A10 Thunder Kubernetes Connector regarding the update resource is forwarded to the Thunder ADC using aXAPI. This way, the owners and operators of cloud applications do not need to monitor their applications for updates.
Documentation Link: https://documentation.a10networks.com/Install/Software/A10_ACOS_Install/thunderKubernetesConnector.html
The ACOS ADC Configuration for Virtual Server, Virtual Port, ServerSsl, ClientSsl, NatPool, Template Cipher,Service Group,Health Monitor can be configured using Custom Resource Defination(CRD).
Guide For Configuring Virtual Server, Virtual Port, ServerSsl, ClientSsl, NatPool, Template Cipher,Service Group,Health Monitor is available at link
Write Configuration to ACOS Memory enables user to save the configuration performed pre and post deployment of A10 Thunder Kubernetes Connector(TKC) under a profile name . User needs to enable the profile as start up config if default profile name is different then default.
More Details regarding this feature is available at link
To enable this feature use --resync-disable flag to enable or disable the feature. When set to false, the configurations will be validated with ACOS device periodically.Otherwise ACOS configuration will change only based on changed performed on Kubernetes Object.
Configuration Guide for this is available at link under command line argument section.
IP over IP tunnel and is defined in RFC2003. The IP tunneling protocol encapsulates one IP packet in another IP packet.
IPIP tunnel can be configured using the static IP route or Border Gateway Protocol (BGP) route.
Configuration Guide is available at link
IP UnNumbered feature is configured on a Thunder device, only one IP address is used for all the logical interfaces attached to the nodes in the overlay tunnel which are required for the traffic flow. In this case, the IP address is shared among the logical interfaces available on the same node.
Thunder Kubernetes Connector supports IP UnNumbered feature for the IPinIP Overlay Tunneling. It allows the following actions:
Configuration Guide of IPUnNumbered is available at link
Red Hat certified products are tested to meet Red Hat’s criteria and supported as defined in the Red Hat Collaborative Support Process.
Partner validated products are tested by Red Hat Partners and supported as defined in the Red Hat Third Party Component Policy.
Do I need ACOS device for running A10 Thunder Kubernetes Connector?
Yes, you need VThunder setup with ADC enabled license.We don't support cThunder solution as of now
Does A10 TKC support OpenShift service of type "Route" and “Ingress”
Yes, A10TKC supports both types of Resource Ingress and Route