You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After talking with Release team of K8s they told me that they do not
always create images for every version of k8s. In this PR we are
changing our logic to retrieve the latest publish image of kindest/node
from docker hub itself.
As part of the change we are also adding a warning, because now these 2
versions are decoupled, whenever a new minor of k8s is released and they
do not publish a new kindest/node image, we write a warning in the
output.
Signed-off-by: Joao Pereira <joaopapereira@gmail.com>
echo "::warning::kindest/node latest is $k8s_version (minor=$kind_minor) but upstream Kubernetes latest is $k8s_latest (minor=$k8s_minor). kind has not yet published an image for the newest minor version."
43
+
fi
30
44
fi
31
-
echo "k8s_version=$k8s_version" >> $GITHUB_ENV
32
-
- name: Create Kind Cluster(k8s version ${{ env.k8s_version }})
45
+
echo "k8s_version=${k8s_version}" >> $GITHUB_ENV
46
+
- name: Create Kind Cluster(k8s version ${{ env.k8s_version }})
33
47
run: |
34
-
k8s_version=${{ env.k8s_version }}
35
-
echo "Checking if kindest/node:${k8s_version} exists..."
0 commit comments