Age | Commit message (Collapse) | Author | Files | Lines |
|
so-monitoring pod doesn't start completely.
This issue has been addressed here
Change-Id: Iab0d8fd3f1a7b9b000d2eac3968fefc07b5b2230
Issue-ID: SO-1138
Signed-off-by: Ramesh Parthasarathy(rp6768)<ramesh.parthasarathy@att.com>
|
|
All the override files are updated to be in sync with so docker config repository
and address the issue raised.
Change-Id: Iee2badf00dbf57b68871505370d070a2450d3d0b
Issue-ID: SO-1105
Signed-off-by: Ramesh Parthasarathy(rp6768)<rp6768@att.com>
|
|
watchdog timeout was increased to 300 seconds from 60 seconds in override.yaml to overcome distribution timeout
Change-Id: Icaf9e31ae92b5b786eb89487c0744d71921fa97e
Issue-ID: SO-1072
Signed-off-by: Ramesh Parthasarathy(rp6768)<rp6768@att.com>
|
|
All SO override files are updated with correct kube dns address for inter application communications based on review comments
Change-Id: I6e1487f3d5a7db49df3e40fb41b6b148aacfee8d
Issue-ID: SO-1022
Signed-off-by: Ramesh Parthasarathy(rp6768)<rp6768@att.com>
|
|
This check-in is an updated version of helm charts for so
containers based on review comments
Change-Id: I690430622ecbdcaf099a6165844142841db436dd
Issue-ID: SO-709
Signed-off-by: Ramesh Parthasarathy(rp6768)<rp6768@att.com>
|