testing
testing copied to clipboard
eksctl latest release will break cluster setup
Taking a note here after our discussion with @kimwnasptd , this is a time-bomb that will explode next time the aws image will be built with the combination of a newer release of eksctl which might deprecate the version of k8s we're using.
We are using the latest eksctl
release for the image:
https://github.com/kubeflow/testing/blob/a59d753d76c8c35bf17b88b5cd9cea80768f0e69/images/Dockerfile.py3.aws#L60
eksctl
last week deprecated k8s 1.17:
weaveworks/eksctl#4487
We are using k8s 1.18 for the ephemeral cluster: https://github.com/kubeflow/testing/blob/a59d753d76c8c35bf17b88b5cd9cea80768f0e69/images/aws-scripts/create-eks-cluster.sh#L29
Actually eksctl
will remove the support when EKS will remove the support for 1.18. So our actual problem is that we're still testing on 1.18.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in one week if no further activity occurs. Thank you for your contributions.
/remove-lifecycle stale