Jun Duan

Mystery clusterrole reference in docs/getting-started

1

# Expected Behavior The `roleRef` of the `tekton-triggers-getting-started-clusterbinding` clusterrolebinding in docs/getting-started/rbac/clusterrolebinding.yaml refers to some real clusterrole. # Actual Behavior The `roleRef` refers to a clusterrole `tekton-triggers-example-clusterrole` which doesn't exist. #...

When building for ppc64le, I saw error messages like these: ``` /root/go/pkg/mod/github.com/headzoo/[email protected]/agent/agent_linux.go:19:23: cannot use buf.Sysname (variable of type [65]uint8) as [65]int8 value in argument to charsToString /root/go/pkg/mod/github.com/headzoo/[email protected]/agent/agent_linux.go:29:23: cannot use buf.Release...

✨ Make the status controller handle the deletion of workstatuses

10

## Summary This PR adds logic to the status controller so that it handles the deletion of WorkStatus objects. This PR also completes a pending e2e test, tracked by [this...

bug: No deletion of workload object status on deletion of workstatus

1

### Describe the bug Status of workload objects in WDSes are not deleted, when corresponding WorkStatus objects are deleted due to BindingPolicy selection changes on singleton status report WEC(s). I...

### Describe the bug As described in the title. For example, the status controller clears the entire status of a workload object when the status controller sees the wec-returned status...

[Core] Expose API endpoint `/is_sleeping`

1

This PR exposes a read-only API to check whether the engine is sleeping. More details are documented as #14311 . FIX #14311

[Feature]: Expose a read-only API to check whether engine is sleeping

1

### 🚀 The feature, motivation and pitch The sleep feature works great! We can do even better by adding a read-only probe to check whether the engine is sleeping or...

possible bug: `for` loop in `NoteStatusCollector` never enters body

4

### Describe the bug The for loop https://github.com/kubestellar/kubestellar/blob/fed2272bb76cdd64c9f8b91c85cd571ab0ed2390/pkg/status/combinedstatus-resolver.go#L378 seems not been entered at all during our e2e tests. Not 100% sure it's a bug, but It's surprising to me that...

bug: e2e test is flaky

2

### Failures in GH Actions There are several failures in recent e2e tests run by GitHub Actions. https://github.com/kubestellar/kubestellar/actions/runs/11558128440 https://github.com/kubestellar/kubestellar/actions/runs/11558733913 https://github.com/kubestellar/kubestellar/actions/runs/11562980808 Specifically, two ginkgo nodes - `can sum status.availableReplicas across WECs`...

Fixed duration of wait in ginkgo e2e tests

1

As comments https://github.com/kubestellar/kubestellar/issues/2532#issuecomment-2449091093 and https://github.com/kubestellar/kubestellar/issues/2532#issuecomment-2449024478 suggested, the concerned code is https://github.com/kubestellar/kubestellar/blob/047f0451043b4df75a00952f67eaf6d41d7b928c/test/e2e/ginkgo/multiple_cluster_deployment_test.go#L133-L135