[teiid-issues] [JBoss JIRA] (TEIIDSB-64) Research HA
[
https://issues.jboss.org/browse/TEIIDSB-64?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIIDSB-64:
---------------------------------------
The docs are little confusing on this, but a loadbalancer selector does not seem to work
well against a service name. If you use app/dc it works fine:
{code}
oc create -f - <<INGRESS
apiVersion: v1
kind: Service
metadata:
name: rdbms-example-ingress
spec:
ports:
- name: teiid
port: 31000
type: LoadBalancer
selector:
app: rdbms-example
sessionAffinity: ClientIP
INGRESS
{code}
We want to use the app directly in any case as the internal services themselves will be
set to have ClientIP sessionAffinity - so using the internal service would mean that all
of the external load balanced traffic would go to a single pod.
I'll see how/if this can be incorporated in the example.
Research HA
-----------
Key: TEIIDSB-64
URL: https://issues.jboss.org/browse/TEIIDSB-64
Project: Teiid Spring Boot
Issue Type: Quality Risk
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Teiid's pg, and jdbc assume session affinity. Also OData pagination works best with
session affinity.
For HA, and horizontal scaling, it would be good to have more than 1 pod alive and
receiving traffic. It appears that there is a sessionAffinity setting at a service level
https://kubernetes.io/docs/concepts/services-networking/service/ and some work that can be
done to customize routes
https://docs.openshift.com/container-platform/3.9/architecture/networking...
- but that doesn't appear to work for just tcp traffic.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)