-
Notifications
You must be signed in to change notification settings - Fork 536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: script changes to run minikube with none driver #3415
Conversation
install required crio to run minikube with none driver and added if check to exclude minikube argements which doesnot required for none driver. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
I think you also need to modify https://github.com/ceph/ceph-csi/blob/ci/centos/single-node-k8s.sh |
Yes for now hardcoding the script to start cluster with none driver for testing, if everything goes well i move some installation and configurtion to above script |
782acd8
to
bdcc708
Compare
scripts/minikube.sh
Outdated
EXTRA_MINIKUBE_ARGS=${EXTRA_MINIKUBE_ARGS:-"--container-runtime=cri-o"} | ||
|
||
function install_crio() { | ||
dnf install jq conntrack docker -y |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please do not use Docker, use Podman instead.
Isn't there a repository that provides CRIO RPMs?
75fd672
to
ef372c1
Compare
/test ci/centos/k8s-e2e-external-storage/1.22 |
1 similar comment
/test ci/centos/k8s-e2e-external-storage/1.22 |
/retest ci/centos/mini-e2e/k8s-1.22 |
b72e8b1
to
a85765c
Compare
/retest ci/centos/mini-e2e/k8s-1.22 |
@Mergifyio rebase |
☑️ Nothing to do
|
b2f2145
to
9fbf360
Compare
test only change to check everything works fine for the none driver Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
When running on AWE EC2 virtual-machines, we'll use Podman instead of installing a VM. The "none" driver might work as well, but it requires additional dependencies to be installed, which may change over time with new minikube or Kubernetes releases. Hopefully the Podman driver is less affected with changes in dependencies. Depends-on: ceph#3419 Closes: ceph#3415 Signed-off-by: Niels de Vos <ndevos@redhat.com>
When running on AWE EC2 virtual-machines, we'll use Podman instead of installing a VM. The "none" driver might work as well, but it requires additional dependencies to be installed, which may change over time with new minikube or Kubernetes releases. Hopefully the Podman driver is less affected with changes in dependencies. Depends-on: ceph#3419 Closes: ceph#3415 Signed-off-by: Niels de Vos <ndevos@redhat.com>
When running on AWE EC2 virtual-machines, we'll use Podman instead of installing a VM. The "none" driver might work as well, but it requires additional dependencies to be installed, which may change over time with new minikube or Kubernetes releases. Hopefully the Podman driver is less affected with changes in dependencies. Depends-on: ceph#3419 Closes: ceph#3415 Signed-off-by: Niels de Vos <ndevos@redhat.com>
When running on AWE EC2 virtual-machines, we'll use Podman instead of installing a VM. The "none" driver might work as well, but it requires additional dependencies to be installed, which may change over time with new minikube or Kubernetes releases. Hopefully the Podman driver is less affected with changes in dependencies. Depends-on: ceph#3419 Closes: ceph#3415 Signed-off-by: Niels de Vos <ndevos@redhat.com>
When running on AWE EC2 virtual-machines, we'll use Podman instead of installing a VM. The "none" driver might work as well, but it requires additional dependencies to be installed, which may change over time with new minikube or Kubernetes releases. Hopefully the Podman driver is less affected with changes in dependencies. Depends-on: ceph#3419 Closes: ceph#3415 Signed-off-by: Niels de Vos <ndevos@redhat.com>
When running on AWE EC2 virtual-machines, we'll use Podman instead of installing a VM. The "none" driver might work as well, but it requires additional dependencies to be installed, which may change over time with new minikube or Kubernetes releases. Hopefully the Podman driver is less affected with changes in dependencies. Depends-on: ceph#3419 Closes: ceph#3415 Signed-off-by: Niels de Vos <ndevos@redhat.com>
When running on AWE EC2 virtual-machines, we'll use Podman instead of installing a VM. The "none" driver might work as well, but it requires additional dependencies to be installed, which may change over time with new minikube or Kubernetes releases. Hopefully the Podman driver is less affected with changes in dependencies. Depends-on: #3419 Closes: #3415 Signed-off-by: Niels de Vos <ndevos@redhat.com>
When running on AWE EC2 virtual-machines, we'll use Podman instead of installing a VM. The "none" driver might work as well, but it requires additional dependencies to be installed, which may change over time with new minikube or Kubernetes releases. Hopefully the Podman driver is less affected with changes in dependencies. Depends-on: #3419 Closes: #3415 Signed-off-by: Niels de Vos <ndevos@redhat.com> (cherry picked from commit 0cba724)
When running on AWE EC2 virtual-machines, we'll use Podman instead of installing a VM. The "none" driver might work as well, but it requires additional dependencies to be installed, which may change over time with new minikube or Kubernetes releases. Hopefully the Podman driver is less affected with changes in dependencies. Depends-on: #3419 Closes: #3415 Signed-off-by: Niels de Vos <ndevos@redhat.com> (cherry picked from commit 0cba724)
install required crio to run minikube with none driver and added if check to exclude minikube arguments which doesnot required for none driver.
Signed-off-by: Madhu Rajanna madhupr007@gmail.com