ingressClassName: kong
informationservice:
- informationservice:
- persistence:
- # Either refer to a volume created under the nonrtric by storageClassName. Then the claimed size should be the same.
- # The alternative use a dynamic volume provisioner in the cluster. Storage class can then be for instance 'standard' or 'gluster-fs' (depeneds on which classes that are available)
- size: 2Gi
- storageClassName: ics-storage
- ingress:
- enabled: true
+ persistence:
+ # Either refer to a volume created under the nonrtric by storageClassName. Then the claimed size should be the same.
+ # The alternative use a dynamic volume provisioner in the cluster. Storage class can then be for instance 'standard' or 'gluster-fs' (depeneds on which classes that are available)
+ size: 2Gi
+ storageClassName: ics-storage
+ ingress:
+ enabled: true
# Need to check the external port Availability
policymanagementservice:
- policymanagementservice:
- persistence:
- # Either refer to a volume created under the nonrtric by storageClassName. Then the claimed size should be the same.
- # The alternative use a dynamic volume provisioner in the cluster. Storage class can then be fon instance 'standard' or 'gluster-fs' (depeneds on which classes that are available)
- size: 2Gi
- storageClassName: pms-storage
+ persistence:
+ # Either refer to a volume created under the nonrtric by storageClassName. Then the claimed size should be the same.
+ # The alternative use a dynamic volume provisioner in the cluster. Storage class can then be fon instance 'standard' or 'gluster-fs' (depeneds on which classes that are available)
+ size: 2Gi
+ storageClassName: pms-storage
ingress:
enabled: true
enabled: true
helmmanager:
- helmmanager:
- persistence:
- # Either refer to a volume created under the nonrtric by storageClassName. Then the claimed si>
- # The alternative use a dynamic volume provisioner in the cluster. Storage class can then be f>
- storageClassName: helmmanager-storage
+ persistence:
+ # Either refer to a volume created under the nonrtric by storageClassName. Then the claimed si>
+ # The alternative use a dynamic volume provisioner in the cluster. Storage class can then be f>
+ storageClassName: helmmanager-storage
controlpanel:
- controlpanel:
- ingress:
- enabled: false
+ ingress:
+ enabled: false
oru-app:
simulators: