k8s apiserver not running on RPi 4 model B
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 692
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
I have VMware ESXi 7.0.0 over RPi 4 mod. B with Photon OS 5.0 GA Binaries OVA with virtual hardware v14 arm64
Linux photon-ova 6.1.94-1.ph5-esx # 1-photon SMP Sat Jun 29 03:04:00 UTC 2024 aarch64 GNU/Linux.
But systemctl restart kube-apiserver not sturted apiserver
And i try use Photon OS 4.0 Rev2 OVA with virtual hardware v13 arm64 with the same errors
Reproduction steps
- Use docs https://vmware.github.io/photon/docs-v5/user-guide/kubernetes-on-photon-os/running-kubernetes-on-photon-os/prepare-the-hosts/
tdnf install kubernetessystemctl restart kube-apiserver- Have next message
'Job for kube-apiserver.service failed because the control process exited with error code.
See "systemctl status kube-apiserver.service" and "journalctl -xeu kube-apiserver.service" for details.'
`systemctl status kube-apiserver.service
× kube-apiserver.service - Kubernetes API Server
Loaded: loaded (/usr/lib/systemd/system/kube-apiserver.service; disabled; preset: enabled)
Active: failed (Result: exit-code) since Mon 2024-07-01 08:41:10 UTC; 1min 13s ago
Docs: https://github.com/GoogleCloudPlatform/kubernetes
Process: 801 ExecStart=/usr/bin/kube-apiserver $KUBE_LOGTOSTDERR $KUBE_LOG_LEVEL $KUBE_ETCD_SERVERS $KUBE_API_ADDRESS $KUBE_API>
Main PID: 801 (code=exited, status=1/FAILURE)
CPU: 182ms
Jul 01 08:41:10 photon-ova systemd[1]: kube-apiserver.service: Main process exited, code=exited, status=1/FAILURE
Jul 01 08:41:10 photon-ova systemd[1]: kube-apiserver.service: Failed with result 'exit-code'.
Jul 01 08:41:10 photon-ova systemd[1]: Failed to start Kubernetes API Server.
Jul 01 08:41:10 photon-ova systemd[1]: kube-apiserver.service: Scheduled restart job, restart counter is at 5.
Jul 01 08:41:10 photon-ova systemd[1]: Stopped Kubernetes API Server.
Jul 01 08:41:10 photon-ova systemd[1]: kube-apiserver.service: Start request repeated too quickly.
Jul 01 08:41:10 photon-ova systemd[1]: kube-apiserver.service: Failed with result 'exit-code'.
Jul 01 08:41:10 photon-ova systemd[1]: Failed to start Kubernetes API Server.
`
...
Expected behavior
k8s does not start. Also the documentation is not true in the following files
nano /etc/kubernetes/apiserver
# The address on the local server to listen to.
KUBE_API_ADDRESS="--insecure-bind-address=0.0.0.0"
# Comma separated list of nodes in the etcd cluster
# KUBE_ETCD_SERVERS="--etcd-servers=http://127.0.0.1:2379"
KUBE_ETCD_SERVERS="--etcd-servers=http://127.0.0.1:4001"
As you can see, the name of the API --address flag has changed to --insecure-bind-address, the etcd port number is not correct. Need 2379
Additional context
I found numerous complaints about similar problems with keys on the internet.
I rebuilt apiserver directly on my RPi device with the same result. So the problem is definitely in the configuration, not the software.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Kubernetes-on-Photon-OS preparation documentation and /etc/kubernetes/apiserver, then run systemctl status kube-apiserver.service and journalctl -xeu kube-apiserver.service to identify the failing configuration. Compare the documented API address and etcd settings with the installed service configuration. Done means the documented setup matches the current Kubernetes flags and kube-apiserver starts successfully on the RPi 4 configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, linux, raspberry-pi
- Domain
- devops, infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100