My Oracle Support Banner

CNE ECE Helm Charts Missing K8s Service For Coherence Federation (Doc ID 2779268.1)

Last updated on MAY 27, 2021

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.3.0 and later
Information in this document applies to any platform.

Goal

ece-service (defined in ece-service.yaml) is missing Federation port defined in federation-config (which should be part of charging-coherence-override-dev.xml, defined in charging-settings.yaml).

In detail:


{{- if eq .Values.charging.isFederation true }}
<federation-config>
<participants>
<participant>
<name system-property="primary.cluster">PrimaryCluster</name>
{{- if eq .Values.charging.secondaryCluster true }}
<initial-action>stop</initial-action>
{{- else }}
<initial-action>start</initial-action>
{{- end }}
<remote-addresses>
<socket-address>
<address system-property="primary.cluster.host">{{.Values.charging.cluster.primary.eceServicefqdn }}
</address><port system-property="primary.cluster.port">{{.Values.charging.ecs.coherencePort }}</port>
</socket-address>
</remote-addresses>
</participant>
¿¿¿¿¿¿.
</participants>
</federation-config>

.Values.charging.ecs.coherencePort seems not exposed in .Values.charging.cluster.secondary.eceServiceName (=¿ece-service¿)

apiVersion: v1
kind: Service
metadata:
{{- if eq .Values.charging.secondaryCluster true }}
name: {{ .Values.charging.cluster.secondary.eceServiceName }}
labels:
app: {{ .Values.charging.cluster.secondary.eceServiceName }}
{{- else }}
name: {{ .Values.charging.cluster.primary.eceServiceName }}
labels:
app: {{ .Values.charging.cluster.primary.eceServiceName }}
{{- end }}
annotations:
service.alpha.kubernetes.io/tolerate-unready-endpoints: "true"
spec:
ports:
- port: {{ .Values.charging.jmxport }}
selector:
app: {{ .Values.charging.labels | default "ece" }}
clusterIP: None
publishNotReadyAddresses: true

 

Note : Federation in ECE CN across k8s clusters requires ports exposed for federated services on an external IP. This also requires changes in
charging-coherence-override-dev.xml and charging-cache-config.xml.
Above configuration shown in snippets works only for federation across different namespaces within same k8s cluster.


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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.