Age | Commit message (Collapse) | Author | Files | Lines |
|
Issue-ID: MULTICLOUD-1324
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: Ifd8ae34b8f04da52acc4c3a6a8259d1bcd05616c
|
|
The CAP_NET_RAW capability is not available with the default
PodSecurityPolicy. Create a service account and role binding to the
privileged policy and specify the sink to use it.
Issue-ID: MULTICLOUD-1310
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: Ib00ee1e8797d497d024a167fc9a0336d4c2a7ae1
|
|
Issue-ID: MULTICLOUD-1146
Signed-off-by: Kuralamudhan Ramakrishnan <kuralamudhan.ramakrishnan@intel.com>
Change-Id: I221cfc74809c3179c6bc389b513f20128138d24f
|
|
Add demonstration files and test scripts to show the vFW
use case as a composite application using network intents
and ovnaction intents to deploy to multiple clusters.
Issue-ID: MULTICLOUD-1095
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: I74b837f9f97747f1eefffbcd105a6630a7b3a374
|
|
Defines a service for the vfw packet generator of
the K8S demo. This allows netconf mount to be made
by appc.
Issue-ID: MULTICLOUD-802
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
Change-Id: I895edcbc3950c798e39906ff5cb862602193fc3b
|
|
ovn4nfvk8s plugin now uses operator sdk
and controller runtime. It now includes
support for Network operator. This patch
includes changes needed in KUD for that.
Signed-off-by: Ritu Sood <ritu.sood@intel.com>
Issue-ID: MULTICLOUD-684
Change-Id: I63dc971e257067c69c70a8996eaffd1a9d8a4c2c
|
|
Pull policy is "Always" because of that
VM/container images are pulled everytime
for each chart. This slows down the
deployment to several minutes in the
lab environment. Changing pull policy to
"IfNotPresent".
Change-Id: I3c01e681f010481221f1e720e6f09b317fbe9d87
Signed-off-by: Ritu Sood <ritu.sood@intel.com>
Issue-ID: MULTICLOUD-708
|
|
Fixing a typo in vFw Helm chart
Change-Id: I5e7657dba037e48539ac32a98f1731ec1ff942a8
Issue-ID: MULTICLOUD-708
Signed-off-by: Ritu Sood <ritu.sood@intel.com>
|
|
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>
|