ct-Open-Source / ct-Open-Source/team-container

after reboot http 404 and Unable to perform initial Kubernetes service initialization: Service "kubernetes" is invalid: spec.clusterIP

Open
#49 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
116
Forks
37
PR merge metrics
No merged PRs in 30d

Description

after reboot seems that trafik is not starting:

E0813 03:32:39.006770 869 controller.go:114] loading OpenAPI spec for "v1beta1.metrics.k8s.io" failed with: failed to retrieve openAPI spec, http error: ResponseCode: 503, Body: servi

k3s[1652]: E0812 17:18:19.182101 1652 controller.go:151] Unable to perform initial Kubernetes service initialization: Service "kubernetes" is invalid: spec.clusterIP: Invalid value: "10.43.0.1": cannot
k3s[1652]: E0812 17:18:19.182591 1652 controller.go:156] Unable to remove old endpoints from kubernetes service: StorageError: key not found, Code: 1, Key: /registry/masterleases/xxx.xxx.xxx.xxx, Resource

Contributor guide

No contributing guide indexed for this repository

Research direction

No files or tests are named. Start by reproducing the reboot scenario and reviewing the k3s logs around the invalid Kubernetes service and failed metrics API request. Done means the services initialize successfully after reboot without the reported 404, 503, or clusterIP errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.