summaryrefslogtreecommitdiffstats
path: root/kubernetes/consul/charts/consul-server/templates/statefulset.yaml
AgeCommit message (Collapse)AuthorFilesLines
2020-12-09[CONSUL] Move components to component dirJakub Latusek1-76/+0
Helm 3.4 requires the dependencies in the charts dir to be included in the requirements. Dependencies need to be moved to the components folder Signed-off-by: Jakub Latusek <j.latusek@samsung.com> Change-Id: Id91e9afe881fa744e5398425d0b4438c15488374 Issue-ID: OOM-2562
2020-11-27[CONSUL] Make consul run as non-rootKrzysztof Opasiak1-1/+4
Use our recently build consul image (still based on the same old consul version) and modify the deployment to make sure that it is able to run as non-root user. Yes, I know that moving consul-server to component would be more proper solution but as this commit is supposed to be cherry-picked to guilin I've tried to make as little changes as possible. Issue-ID: REQ-362 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: Idfc09ee225d4f89bb699683fa5e4ae3b86491c08
2020-11-21[CONSUL] Uses new tpls for repos / imagesSylvain Desbureaux1-1/+1
This commit makes Consul chart to use the new generator for repositories and images. Issue-ID: OOM-2364 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: Id46ed756b1f975695585e873c8e13accf3b1d7ca
2020-11-16Revert "[CONSUL] Make consul server run as non-root"Daniel Milaszkiewicz1-3/+1
Revert submission 114556 Reason for revert: Bug - OOM-2630 Reverted Changes: Ic1302ac28:[CONSUL] Make consul server run as non-root I43584b7f0:[CONSUL] Make consul run as non-root Issue-ID: OOM-2630 Change-Id: I3e96f85ad92239f6a3e3df019fc1f675b837ce0d Signed-off-by: Daniel Milaszkiewicz <daniel.milaszkiewicz@nokia.com>
2020-11-03[CONSUL] Make consul server run as non-rootKrzysztof Opasiak1-1/+3
Modify the entrypoint to eliminate root process from container. Issue-ID: REQ-362 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: Ic1302ac2858dda1bac71be4449ea74cfc73ba197
2020-10-27Merge "[CONSUL] Add limits to consul chart."Krzysztof Opasiak1-0/+1
2020-10-21[CONSUL] change comment styleJakub Latusek1-0/+2
Signed-off-by: Jakub Latusek <j.latusek@samsung.com> Change-Id: Ifc524b9818517d5c7741f11e09734300ef66ce77 Issue-ID: OOM-2562
2020-10-20[CONSUL] Add limits to consul chart.Sylvain Desbureaux1-0/+1
Having limits is important in order to have safe deployment. consul didn't had one so let's add them. Issue-ID: OOM-2230 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: Idb49a5db304236c0786848acbc69c786084d7e33
2020-07-10Make CONSUL compatible with Kubernetes v1.17Magdalena_Biernacka1-1/+1
Issue-ID: OOM-2451 Signed-off-by: Magdalena Biernacka <magdalena.1.biernacka@nokia.com> Change-Id: Idc86f18d1693e3b98188a3632343bf9b6ae3c7f5
2020-02-01[ONAP-wide] Replace .Release.Name with common.releaseKrzysztof Opasiak1-2/+2
ONAP is too big to be deployed using helm install so we need to use a custom helm plugin helm deploy. This script deloys onap component by component instead of deploying evrything at once. Unfortunately this script also modifies the helm release by appending component name to it. As a result of this behavior our objects are called for example: onap-mariadb-galera-mariadb-galera-0 instead of just being called onap-mariadb-galera-0. This patch simplifies this naming convention by replacing all direct usages of .Release.Name with common.release macro which strips the component specific part from the release name. Issue-ID: OOM-2275 Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com> Change-Id: Ia8cead50d305adb00eef666d0a1ace74479b5183
2018-09-05Apache 2 license addition for consul,appcMukul1-0/+1
Issue-ID: OOM-1308 Change-Id: I6cfe05841a17f81e862dfbf4bedaa4ba87f96e1e Signed-off-by: Mukul <mukul.joshi@amdocs.com>
2018-05-15Consul Stateful SetPriyanka Jain1-0/+69
Issue-ID: OOM-1032 Change-Id: I911085dffc35067d844b5dcb286581fa0897a27a Signed-off-by: Priyanka Jain <Priyanka.Jain3@amdocs.com>