Bug: Running in-cluster and the items in Workloads tab has wrong order since 4.19
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- kubernetes, typescript
- Domain
- frontend
Research direction
Reproduce the issue with the provided in-cluster vanilla Kubernetes manifest, comparing origin-console images 4.18 and 4.19 or newer. Trace the Workloads tab ordering in the TypeScript frontend and compare the displayed resource order; done means Topology, Pods, and Deployments appear first as expected.
Written by the indexing model from the issue text.
Description
When running conosle in-cluster on vanilla k8s the tab Workloads have the wrong order. Topology, Pods and Deployments drops to the bottom, they should be on the top. Before 4.19 this bug in not there. Booting up same manifest config with 4.18 image the ordering is correct, from 4.19 and newer the order is wrong.
I dont have enough skills in TypeScript to debug where in the code it goes wrong.
My settings is like this:
containers:
- name: console
image: quay.io/openshift/origin-console:4.22
ports:
- containerPort: 9000
env:
- name: BRIDGE_K8S_AUTH_BEARER_TOKEN
valueFrom:
secretKeyRef:
name: openshift-console-token
key: token
args:
- "/opt/bridge/bin/bridge"
- "--k8s-mode=in-cluster"
- "--k8s-auth=bearer-token"
- "--user-auth=disabled"
- "--user-settings-location=localstorage"
- "--public-dir=/opt/bridge/static"
From image tag 4.19 and newser the (wrong) order is like this, Topology, Pods, Deployments should have the order 1, 2, 3 in Workloads list, but does not when running with in.cluster on vanilla k8s for some reason.
Workloads
StatefulSets
Secrets
ConfigMaps
CronJobs
Jobs
DaemonSets
ReplicaSets
ReplicationControllers
HorizontalPodAutoscalers
PodDisruptionBudgets
Topology
Pods
Deployments
If I boot up 4.18 the order is correct,
Pods
Deployments
StatefulSets
Secrets
ConfigMaps
CronJobs
Jobs
DaemonSets
ReplicaSets
ReplicationControllers
HorizontalPodAutoscalers
PodDisruptionBudgets
I have tested these images, all have the wrong ordering
image: quay.io/openshift/origin-console:4.22
image: quay.io/openshift/origin-console:4.19
image: quay.io/openshift/origin-console:latest
Image 4.18 have correct ordering
image: quay.io/openshift/origin-console:4.18
- Dominant language
- TypeScript
- Stars
- 460
- Forks
- 756
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 88
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.
More from openshift/console
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 67/100
All issues in openshift/console
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·