-
Notifications
You must be signed in to change notification settings - Fork 569
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
add kubernetes v1.25.x image to dockerhub #1581
Comments
i can not use this images in
run kk artifact export
|
Thanks for the feedback, we are still syncing the k8s images... |
As for this error, it looks like one of the images behind this |
|
I mean there is something wrong with the format of the other image names. Could you please paste your manifest file here? |
command
manifests-v1.25.3.yaml
|
Thanks @willzhang
|
some images lost
need pause and k8s-dns-node-cache
suggest
part1: kube images
part2: k8s-dns-node-cache
part3: calico images just use docker.iosuggest use github action workflow sync all version tagssync.yaml
workflow.yaml
|
some more error with
|
The images pause and k8s-dns-node-cache have synced to docker.io/kubesphere.
#1577 is included in the KubeKey v3.0.0. And you can use
Thanks for the suggestion! For some historical reasons, the ks community uses an internal AWX project to sync the images. And we also recently wanted to migrate this feature to GitHub action. The workflow.yaml is very useful and we will try it later. |
aliyun images should sync too. what's command
error logs
|
error logs
|
done |
/close |
@24sama: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Your current KubeKey version
2.3.0
Describe this feature
kk artifact export
Describe the solution you'd like
add v1.25 images to dockerhub, or sync everyday with github action.
Additional information
No response
The text was updated successfully, but these errors were encountered: