Age | Commit message (Collapse) | Author | Files | Lines |
|
Multus has a limitation that namespace
in which network is defined has to be
explicitly provided. As we are defining
network in "default" namespace, that needs
to be provided in all deployment files
Signed-off-by: Ritu Sood <ritu.sood@intel.com>
Issue-ID: MULTICLOUD-663
Change-Id: Iefc17691fa909843f12fa35693900a063a6d20ae
|
|
IP address was incorrect for
sink
Change-Id: I28962cedeecd25b136eecf39786b4daed6ae9c26
Signed-off-by: Ritu Sood <ritu.sood@intel.com>
Issue-ID: MULTICLOUD-653
|
|
Fixed sink containers
to use the right containers and also
fixed IP addresses. Some cleanup
Change-Id: Id7ed7fe48c9e37f5d3c52c02c0585af7511c5efe
Signed-off-by: Ritu Sood <ritu.sood@intel.com>
Issue-ID: MULTICLOUD-653
|
|
The charts are complete with templating and basic constructs.
They need to be modified in terms of chart dependency and also address
network configuration. Addressed comments, changed network config
values and included subcharts. Removed redundent vars. Removed
shell vars and updated sink. Updated vars. Removed escape
chars from password which and removed comment in pod annotations.
Removed comments from network files. Changed the deployment file
lables for all 3 charts. Extricated some of the values addressed by comments.
Set global vars. Updated sink-service labels.
Change-Id: Id6fc2e066c8a6c5b33b65caae3a49637521c3133
Issue-ID: MULTICLOUD-628
Signed-off-by: Akhila Kishore <akhila.kishore@intel.com>
|