Calico requires the default reverse path forwarding to be either 0 (no
validation) or 1 (strict validation). The default value of 2 (loose
validation) prevents calico from completing the setup and the pod is
always stuck getting ready.
Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
CRD was removed as part of 1.14 update. Missed update to create_stack
Fixes: #84
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
RuntimeClass moved from alpha to beta. Remove the feature gates, remove
the runtimeClass CRD since it is a built in type, and take the new data
structure into account.
Fixes: #77
Signed-off-by: Eric Ernst <eric.ernst@intel.com>
This is finally supported in Kata 1.6
Update memory limit for kata to run in guaranteed test case
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
In case of containerd there is no need to restart. Restart for crio is needed
when it manages the networks ns lifecycle. Removed the kubelet stop step which
was a leftover from earlier device plugin install.
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
We only support kubernetes versions with support for runtimeClass.
Remove the legacy annotations to reduce confusion.
Signed-off-by: Manohar Castelino <manohar.r.castelino@intel.com>
The admission controller is now able to access full context.
Hence explicit tagging of pod manifests to exclude them from
kata is no longer required.
Signed-off-by: Manohar Castelino <manohar.r.castelino@intel.com>
Disable proxy setup if the host does not have proxy setup in
the enviornment variables
Signed-off-by: Manohar Castelino <manohar.r.castelino@intel.com>
* Remove duplicate lifecycle entry in crio.conf
* Remove fc config.toml as that is provided by the distro.
Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
Disable devicemapper udev sync. Without this the storage device
will not be discovered post system reboot
Signed-off-by: Manohar Castelino <manohar.r.castelino@intel.com>
The parent box is already downloading the OVMF firmware.
Just use the firmware that is already downloaded.
Signed-off-by: Manohar Castelino <manohar.r.castelino@intel.com>
With kubelet service file fixed and correct args set in
metrics-server-deployment.yaml, autoscale seems to be working reliably.
Fixes: #5
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Currently cpumanagerpolicy:static is partially broken.
Hope these files catch future regressions
Added a script to generate yamls for different runtimeclass from
a template with different resource constraints on the pod
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Addressing comments -
1a. added flag to `sriov.sh` to indicate bind to vfio-pci
1b. systemd unit sets up two pools 1 per mode
2a. updated `sriov-conf.yaml` to use the two pools
3a. included network examples for both resource pools
3b. included pod examples for both resource pools
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Adding a cni to mirror MAC address of VF on a veth pair with results
from ipam applied to enable DPDK apps to configure themselves when
operating sriov-network-device-plugin in vfio mode
Updated helper sriov.sh to allow for binding VFs to vfio-pci on boot
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Avoid creating unique names for disks as vagrant-libvirt today does not
delete those images when VMs are deleted. Once that is fixed we can move
back to using unique names. Until then this should suffice.
Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
In case we need to exit early this would have copied the credentials
into the home dir
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Instead of mounting at /vagrant it will now be at /home/vagrant/clr-k8s-examples
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Instead of relying on configmap to be created/customized by the user to
generate multus conf, we autogenerate it using the current default CNI
conf file on the host. This way CNI's with host specific conf details
will continue to work.
```
{
"type": "calico",
"nodename": "clr-01",
...
}
```
Since SR-IOV device may not be present on all nodes, the daemonset
should not exit as this will put the pod in restart loop. This would
cause the kubelet and runtimes to repeatedly restart, as per
initContainer logic.
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Runtime class kata-qemu created and older kata point to kata-qemu
handler. Now all the handlers match the crio.conf settings.
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Ganesh Maharaj Mahalingam