KusionStack / KusionStack/karpor

Topology get Error Pod message

Open
#767 3 comments 0 reactions 0 assignees View on GitHub
bug priority/important-longterm
Dominant language
Go
Stars
1.7k
Forks
113
PR merge metrics
No merged PRs in 30d

Description

### What happened?

Namespace Page
1. Click ReplicaSet and then click Pod;
2. It triggers two requests
3. The Error is reported as follows.

![Image](https://github.com/user-attachments/assets/81ff3338-5c57-4f9f-82e6-86888da748ef)

Payload:
![Image](https://github.com/user-attachments/assets/eac1cb80-bfb8-4c4c-ade4-72e8e929e6b6)

Response:
![Image](https://github.com/user-attachments/assets/8ee930c1-ff0f-4ca9-8144-643b799ab337)

The true request payload:
![Image](https://github.com/user-attachments/assets/877dab57-a5c6-4549-89c8-40a8fff93b7a)

### What did you expect to happen?

-

### How can we reproduce it (as minimally and precisely as possible)?

-

### Anything else we need to know?

-

### Karpor version

```console
$ karpor -V
# paste output here
```

### OS version

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

### Install tools

Contributor guide

Open the contributing guide

Research direction

Start at the Namespace Page's ReplicaSet-to-Pod navigation and compare the two requests with the attached payload and response examples. Trace the request entry point and determine why the Pod request produces the reported error; it is done when clicking a ReplicaSet and then a Pod sends the correct payload and no longer shows the error.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
frontend
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.