forked from pegasystems/pega-helm-charts
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ISSUE-655 Add backingservices subchart for Constellation Messaging
- Loading branch information
Showing
10 changed files
with
190 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6 changes: 6 additions & 0 deletions
6
charts/backingservices/charts/constellation-messaging/Chart.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
--- | ||
apiVersion: v1 | ||
name: constellation-messaging | ||
version: 1.0.0 | ||
description: Pega Constellation Messaging Service | ||
appVersion: 8.8.0 |
20 changes: 20 additions & 0 deletions
20
charts/backingservices/charts/constellation-messaging/README.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
#Constellation Messaging Service | ||
|
||
The optional Messaging service acts as a middle man between information publishers and information subscribers; accepting simple http publish of information to forward to 1000's of websocket subscribers. The publishers are typically the Infinity case engine or 3rd party integration services, and the subscribers are UI components in browsers running Constellation UI. | ||
|
||
Once the service routing (with TLS) is set up, configure the Pega Infinity ConstellationMessageSvcHostPath DSS to your service URL (e.g. http://yourhostname.com/c11n-messaging). | ||
|
||
Only a single Messaging Service deployment is necessary to support an entire organization. Do not install the service in every namespace or for every application or project. | ||
|
||
Complete information on the design of the service including architecture, scalability, reliability, operations and troubleshooting is available at [https://documents.constellation.pega.io/messaging/introduction.html](https://documents.constellation.pega.io/messaging/introduction.html). | ||
|
||
### Configuration settings | ||
|
||
| Configuration | Usage | | ||
|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ||
| `enabled` | Enable the Messaging Service deployment as a backing service. Set this parameter to `true` to deploy the service. | | ||
| `name` | Specify the name of your messaging service. Your deployment creates resources prefixed with this string. | | ||
| `imagePullSecretNames` | List pre-existing secrets to be used for pulling docker images. | | ||
| `pegaMessagingPort` | Defines the port used by the Service. | | ||
| `pegaMessagingTargetPort` | Defines the port used by the Pod and Container. | | ||
| `ingress` | Allows optional configuration of a domain name, ingressClass, and annotations. An ingress will be provisioned if a domain name is supplied. Due to the diversity of network configurations, ingress vendors, and TLS requirements it may be necessary to define your ingress separately from this chart. |
32 changes: 32 additions & 0 deletions
32
charts/backingservices/charts/constellation-messaging/templates/messaging-deployment.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
{{- if .Values.enabled }} | ||
kind: Deployment | ||
apiVersion: apps/v1 | ||
metadata: | ||
name: {{ .Values.name }} | ||
labels: | ||
app: {{ .Values.name }} | ||
spec: | ||
replicas: {{ .Values.replicas }} | ||
selector: | ||
matchLabels: | ||
app: {{ .Values.name }} | ||
template: | ||
metadata: | ||
labels: | ||
app: {{ .Values.name }} | ||
spec: | ||
imagePullSecrets: | ||
{{- range .Values.imagePullSecretNames }} | ||
- name: {{ . }} | ||
{{- end }} | ||
containers: | ||
- name: c11n-messaging | ||
imagePullPolicy: {{ .Values.imagePullPolicy }} | ||
image: {{ .Values.image }} | ||
args: | ||
- --max-semi-space-size=1024 | ||
- port={{ .Values.pegaMessagingTargetPort }} | ||
- path=/c11n-messaging | ||
ports: | ||
- containerPort: {{ .Values.pegaMessagingTargetPort }} | ||
{{ end }} |
25 changes: 25 additions & 0 deletions
25
charts/backingservices/charts/constellation-messaging/templates/messaging-ingress.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
{{- if and .Values.enabled .Values.ingress.domain }} | ||
apiVersion: networking.k8s.io/v1 | ||
kind: Ingress | ||
metadata: | ||
name: {{ .Values.name }} | ||
{{- if .Values.ingress.annotations }} | ||
annotations: | ||
{{ toYaml .Values.ingress.annotations | indent 4 }} | ||
{{- end }} | ||
spec: | ||
{{- if .Values.ingress.ingressClassName }} | ||
ingressClassName: {{ .Values.ingress.ingressClassName }} | ||
{{- end }} | ||
rules: | ||
- host: {{ .Values.ingress.domain }} | ||
http: | ||
paths: | ||
- path: /c11n-messaging | ||
pathType: Prefix | ||
backend: | ||
service: | ||
name: {{ .Values.name }} | ||
port: | ||
number: {{ $.Values.pegaMessagingPort }} | ||
{{ end }} |
16 changes: 16 additions & 0 deletions
16
charts/backingservices/charts/constellation-messaging/templates/messaging-service.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
{{- if .Values.enabled }} | ||
apiVersion: v1 | ||
kind: Service | ||
metadata: | ||
name: {{ .Values.name }} | ||
labels: | ||
app: {{ .Values.name }} | ||
spec: | ||
type: NodePort | ||
selector: | ||
app: {{ .Values.name }} | ||
ports: | ||
- protocol: TCP | ||
port: {{ .Values.pegaMessagingPort }} | ||
targetPort: {{ .Values.pegaMessagingTargetPort }} | ||
{{ end }} |
24 changes: 24 additions & 0 deletions
24
charts/backingservices/charts/constellation-messaging/values.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
--- | ||
enabled: false | ||
name: YOUR_MESSAGING_SERVICE_DEPLOYMENT_NAME | ||
|
||
image: YOUR_MESSAGING_SERVICE_IMAGE:TAG | ||
replicas: 1 | ||
|
||
# To avoid exposing Docker credentials, create a separate Docker config secret. | ||
# Specify secret names as an array of comma-separated strings. For example: ["secret1", "secret2"] | ||
imagePullSecretNames: [] | ||
imagePullPolicy: Always | ||
|
||
pegaMessagingPort: 3000 | ||
pegaMessagingTargetPort: 3000 | ||
|
||
serviceType: NodePort | ||
|
||
# An ingress will be provisioned if a hostname is defined, or omitted if the hostname is empty. | ||
# ingressClassName and annotations are optional and will be included if defined. | ||
# Due to the diverse requirements for ingresses and TLS configuration, it may be necessary to define the ingress separately from this chart. | ||
ingress: | ||
domain: | ||
ingressClassName: | ||
annotations: |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters