Skip to content
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

deprecated API spec when building 1.31.* images #487

Open
szechp opened this issue Feb 6, 2025 · 2 comments
Open

deprecated API spec when building 1.31.* images #487

szechp opened this issue Feb 6, 2025 · 2 comments

Comments

@szechp
Copy link

szechp commented Feb 6, 2025

I tried magnum-cluster-api-image-builder --version v1.31.5 and the ansible script gives me an error:

qemu: fatal: [default]: FAILED! => {"changed": true, "cmd": "kubeadm config images pull --config /etc/kubeadm.yml --cri-socket /var/run/containerd/containerd.sock", "delta": "0:02:30.597380", "end": "2025-02-06 17:19:59.431382", "msg": "non-zero return code", "rc": 1, "start": "2025-02-06 17:17:28.834002", "stderr": "W0206 17:17:28.883040    3814 common.go:101] your configuration file uses a deprecated API spec: \"kubeadm.k8s.io/v1beta3\" (kind: \"ClusterConfiguration\"). Please use 'kubeadm config migrate --old-config old.yaml --new-config new.yaml', which will write the new, similar spec using a newer API version.\nW0206 17:17:28.883554    3814 common.go:101] your configuration file uses a deprecated API spec: \"kubeadm.k8s.io/v1beta3\" (kind: \"InitConfiguration\"). Please use 'kubeadm config migrate --old-config old.yaml --new-config new.yaml', which will write the new, similar spec using a newer API version.\nW0206 17:17:28.884019    3814 initconfiguration.go:126] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme \"unix\" to the \"criSocket\" with value \"/var/run/containerd/containerd.sock\". Please update your configuration!\nfailed to pull image \"registry.k8s.io/kube-apiserver:v1.31.5\": failed to pull image registry.k8s.io/kube-apiserver:v1.31.5: failed to pull and unpack image \"registry.k8s.io/kube-apiserver:v1.31.5\": failed to resolve reference \"registry.k8s.io/kube-apiserver:v1.31.5\": failed to do request: Head \"https://europe-west3-docker.pkg.dev/v2/k8s-artifacts-prod/images/kube-apiserver/manifests/v1.31.5\": dial tcp 74.125.71.82:443: i/o timeout\nTo see the stack trace of this error execute with --v=5 or higher", "stderr_lines": ["W0206 17:17:28.883040    3814 common.go:101] your configuration file uses a deprecated API spec: \"kubeadm.k8s.io/v1beta3\" (kind: \"ClusterConfiguration\"). Please use 'kubeadm config migrate --old-config old.yaml --new-config new.yaml', which will write the new, similar spec using a newer API version.", "W0206 17:17:28.883554    3814 common.go:101] your configuration file uses a deprecated API spec: \"kubeadm.k8s.io/v1beta3\" (kind: \"InitConfiguration\"). Please use 'kubeadm config migrate --old-config old.yaml --new-config new.yaml', which will write the new, similar spec using a newer API version.", "W0206 17:17:28.884019    3814 initconfiguration.go:126] Usage of CRI endpoints without URL scheme is deprecated and can cause kubelet errors in the future. Automatically prepending scheme \"unix\" to the \"criSocket\" with value \"/var/run/containerd/containerd.sock\". Please update your configuration!", "failed to pull image \"registry.k8s.io/kube-apiserver:v1.31.5\": failed to pull image registry.k8s.io/kube-apiserver:v1.31.5: failed to pull and unpack image \"registry.k8s.io/kube-apiserver:v1.31.5\": failed to resolve reference \"registry.k8s.io/kube-apiserver:v1.31.5\": failed to do request: Head \"https://europe-west3-docker.pkg.dev/v2/k8s-artifacts-prod/images/kube-apiserver/manifests/v1.31.5\": dial tcp 74.125.71.82:443: i/o timeout", "To see the stack trace of this error execute with --v=5 or higher"], "stdout": "", "stdout_lines": []}

these stand out:
your configuration file uses a deprecated API spec: \"kubeadm.k8s.io/v1beta3\" (kind: \"ClusterConfiguration\"). Please use 'kubeadm config migrate --old-config old.yaml --new-config new.yaml', which will write the new, similar spec using a newer API version.

also this
failed to pull image \"registry.k8s.io/kube-apiserver:v1.31.5\": failed to pull image registry.k8s.io/kube-apiserver:v1.31.5: failed to pull and unpack image \"registry.k8s.io/kube-apiserver:v1.31.5\": failed to resolve reference \"registry.k8s.io/kube-apiserver:v1.31.5\": failed to do request: Head \"https://europe-west3-docker.pkg.dev/v2/k8s-artifacts-prod/images/kube-apiserver/manifests/v1.31.5\": dial tcp 74.125.71.82:443: i/o timeout

it seems like the kubeadm file is deprecated, among other things. is this failing because of kubeadm, or is this failing bc it cant pull images?

edit: i can in fact build 1.31.4, but not 1.31.5 was there a deprecation?

@mnaser
Copy link
Member

mnaser commented Feb 6, 2025

@szechp Can you try using the https://github.com/vexxhost/capo-image-elements repository for building images? We've actually been relying more on that for image builds instead of this.

@szechp
Copy link
Author

szechp commented Feb 6, 2025

Okay, so this is deprecated? Btw, 1.32.1 builds fine again 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants