Kubernetes Pods Don't Work With Coherence WKA Cluster Nodes Running On Virtual Machines
(Doc ID 3061261.1)
Last updated on DECEMBER 04, 2024
Applies to:
Oracle Coherence - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Goal
Kubernetes pods don't work with coherence wka cluster nodes running on Virtual Machines. There is an oracle coherence cluster (unicast) with wka nodes (storage enabled) and proxy-tier (storage disabled) running on Virtual Machines, some client applications running on other VMs and other client containers running on kubernetes cluster. Client applications on VMs work well as cluster members (storage disabled) and as extended-client too. Client pods work well only as extended-clients. When Client pods use wka connection users receive these tracing messages:
Is this issue related to some misconfiguration about k8s cluster resources?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |