Unauthorized kubernetes response leads to panic #4

Open
opened 2026-02-15 19:27:01 +01:00 by tamipes · 0 comments
Owner

This happened after it was running correctly for a time, and then it started giving this response.
Might be a problem with my kuberentes install as well.(It was running as an external service)

Restarting fixed it.
Error code:

thread 'tokio-runtime-worker' (2855477) panicked at src/kube_cache.rs:57:42:
called `Result::unwrap()` on an `Err` value: Api(ErrorResponse { status: "Failure", message: "Unauthorized", reason: "Unauthorized", code: 401 })
This happened after it was running correctly for a time, and then it started giving this response. Might be a problem with my kuberentes install as well.(It was running as an external service) Restarting fixed it. Error code: ```text thread 'tokio-runtime-worker' (2855477) panicked at src/kube_cache.rs:57:42: called `Result::unwrap()` on an `Err` value: Api(ErrorResponse { status: "Failure", message: "Unauthorized", reason: "Unauthorized", code: 401 }) ```
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tamipes/mc-ingress#4
No description provided.