RFC: Use minikube prerelease ISO on CI

[irq0]

Now that minikube fscrypt kernel support is merged (kubernetes/minikube#14783), I'm looking for a way to run #3310 on the Ceph CSI CI with that ISO. A updated ISO was build and is available for download: https://storage.googleapis.com/minikube-builds/iso/14783/minikube-v1.26.1-1661377864-14783-amd64.iso

Would this be a way forward until the next minikube release?

[Rakshith-R]

@irq0
Add these commits as part of #3310, to check if ci for new encryption changes passes ?

[nixpanic]

I like the feature, and am sure @pkalever appreciates it too. Going to default for a pre-release for everything is not that great though... At the very least, we'll need an issue to track removing the default pre-release URL once the next minikube version is available.

We use pre-releases sometimes, so I don't think it's a blocking issue.

[Madhu-1]

If this doesn't get updated and CI works fine, am good with this one.

[pkalever]

I think @Madhu-1 concern is vaild, can we copy this to some local file server @nixpanic (I remember we supplied a native link with NBD patches before) ?

[nixpanic]

We don't really want to host ISO images ourselves. If this link stays available until a next minikube version contains the fscrypt feature, I'd prefer to using this.

[Madhu-1]

Now that minikube fscrypt kernel support is merged (kubernetes/minikube#14783), I'm looking for a way to run #3310 on the Ceph CSI CI with that ISO. A updated ISO was build and is available for download: https://storage.googleapis.com/minikube-builds/iso/14783/minikube-v1.26.1-1661377864-14783-amd64.iso

Would this be a way forward until the next minikube release?

The best option is to add it as a new commit in the PR which needs this support.

[irq0]

@irq0 Add these commits as part of #3310, to check if ci for new encryption changes passes ?

Tried, but it seems that single-node-k8s.sh from the ci branch doesn't forward the new env var. #3351 should handle that

[irq0]

@irq0 Add these commits as part of #3310, to check if ci for new encryption changes passes ?

Tried, but it seems that single-node-k8s.sh from the ci branch doesn't forward the new env var. #3351 should handle that

Thanks for merging #3351. I added the two commits to the last push to #3310 and the CI system picked up the new options. The ISO is listed in the minikube logs output of the 'log system status' jenkins node. I'm closing this one in favor #3310.