kubernetes 1.25 changed the key for the NoSchedule taint to
'control-plane'.
Fix the script to handle both pre and post version 1.25
Signed-off-by: Peter W. Morreale <pwmorreale@gmail.com>
* Removing static cpu pinning due to confusion and complications it causes with disabling/enabling cores.
* Static CPU policy by defaults pins the process to CPUs if a kubernetes pod limits are set to be full cpus. While this a neat thing, this also causes issues when setaffinity is tried in a particular CPU. While we would like to set limits, pinning a process to a core is something we will try to avoid in the near future.
per https://github.com/AntonioMeireles/ClearLinux-packer/issues/24 the
ClearLinux libvirt boxes default size was lowered from the previous 40G
to a more manageable 5G, having the user the ability to, at box
instantiation, to increase that value to whatever is adequate.
In order to avoid surprises in this side the Vagrantfile was modded to
have hardcoded the previous default value.
This change is forward and backward compatible as it will just be
ignored when using older boxes ( since the 'new' root volume size just
the same as original one) and will resize the box to the expected 40G in
newer ones.
Signed-off-by: António Meireles <antonio.meireles@reformi.st>
Previously used IP range seems to be allocated to NASA and probably not
a good idea to use it here. Switching the private network to be part of
the IPs allocated to private networks.
Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
* Update multi-net components to latest releases
Multus CNI 3.4.2
SR-IOV CNI 2.3
SR-IOV DP 3.2
Tested as per the README. Works fine.
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
* Provide dpdk-stable 3 LTS and 1 recent release
Testpmd manifests of the last 3 LTS and 1 latest release from stable
repo to help test actual DPDK app instead of sleep.
Currently 17.11 and 19.11 are the only functioning ones without
privileged.
```
NAME READY STATUS RESTARTS AGE
dpdk-1711 1/1 Running 0 3m5s
dpdk-1811 0/1 Error 0 3m5s
dpdk-1911 1/1 Running 0 3m5s
dpdk-2002 0/1 Error 0 3m5s
```
```
EAL: PCI device 0000:07:06.4 on NUMA socket 0
EAL: probe driver: 8086:154c net_i40e_vf
EAL: Getting a vfio_dev_fd for 0000:07:06.4 failed
EAL: Requested device 0000:07:06.4 cannot be used
…
testpmd: No probed ethernet devices
EAL: Error - exiting with code: 1
Cause: Invalid port 1
```
Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
Currently the system.conf.d/proxy.conf file is saved at /usr/lib
which is the vendor path, and can be dropped by
"swupd repair --picky --force".
This commit creates the local administrator /etc/systemd/system.conf.d
directory and store the proxy.conf inside.
The metrics-server package has moved out of the kubernetes incubator
github location and is now in the sigs location.
Signed-off-by: Craig Sterrett <craig.Sterrett@intel.com>
Modified setup_system.sh to use Systemd level proxy instead of per
service proxy.
Tested create_stack all with defaults and ran Sonobuoy successfully against change.
Closes issue #307
Signed-off-by: Craig Sterrett <craig.Sterrett@intel.com>
* Fix rook single node setup
Modified the rook installation to support both multinode kubernetes
clusters and standalone kubernetes clusters. Multinode installations
will occur as before, with changes for standalone installations.
v0.8.3 I found it was not currently working and
is too old to continue to support, will submit a PR for removing it. Also made a couple minor spacing
changes to yaml as detected by yamllint
closes issue 306 https://github.com/clearlinux/cloud-native-setup/issues/306
closes issue 311 https://github.com/clearlinux/cloud-native-setup/issues/311
Signed-off-by: Craig Sterrett <craig.Sterrett@intel.com>
* Fix rook single node setup
Modified the rook installation to support both multinode kubernetes
clusters and standalone kubernetes clusters. Multinode installations
will occur as before, with changes for standalone installations.
v0.8.3 I found it was not currently working and
is too old to continue to support, will submit a PR for removing it. Also made a couple minor spacing
changes to yaml as detected by yamllint
closes issue 306 clearlinux#306
closes issue 311 clearlinux#311
Signed-off-by: Craig Sterrett <craig.Sterrett@intel.com>
Running setup_system.sh on a system setting the OS version to keep setup_system from upgrading the OS causes an error because a package has been removed. Need to add the --force flag to the
sudo swupd repair -m "${CLR_VER}" --picky command
Closes issue #297
Earlier there was confusion between CLRK8S_RUNNER and RUNNER in
setup_system.sh and create_stack.sh script, this patch fixes this
and now the variable can either be RUNNER/CLRK8S_RUNNER.
Signed-off: syed.ahsan.shamim.zaidi@intel.com
Adding non-routable IPs to the no_proxy, non-routable addresses will
never go out the proxy, and are used as internal IPs by VM's running
cloud-native setup. Without the addition of the IP's in no_proxy,
kubernetes nodes will not be able to communicate to the Kubernetes IP as
the traffic will be routed out the proxy server.
Signed-off-by: Craig Sterrett <craig.Sterrett@intel.com>
The sed command for updating no-proxy settings in the proxy.sh file was
not working. I made it match the above command which was working for
/etc/environment.
Signed-off-by: Craig Sterrett <craig.sterrett@intel.com>
base_image_size is effectively the max size of the thinpool snapshot,
and this is static (does not resize). If you are running containers
with larger individual layers, this will fail. (elastic is a good test
for this).
The thinpool should be 10GB, not 1GB (to align with the .img's defined
earlier in file).
Fixes: #266
Signed-off-by: Eric Ernst <eric.ernst@intel.com>
This adds ability to upgrade/downgrade to desired Clear version.
The default behavior remains unchanged (auto updating to latest)
Signed-off-by: Justin Scott <justin.a.scott@intel.com>
This patch add's Flannel to CNI, export the environment variable
to use Flannel, and uses crio as default unless the user
specify otherwise.
Signed-Off: Syed Ahsan <syed.ahsan.shamim.zaidi@intel.com>