iovisor / iovisor/kubectl-trace
Add debug info about failures in CI system using the kubernetes-namespace-report action
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 176
- PR merge metrics
- No merged PRs in 30d
Description
I quickly looked at a recent test failure following the merge of #185. For things erroring in tests done in a k8s cluster, it could be relevant to make use of this github action: https://github.com/jupyterhub/action-k8s-namespace-report
I'm a maintainer of the action and we are using it across the jupyterhub org on github.
This is [how we use it](https://github.com/jupyterhub/zero-to-jupyterhub-k8s/blob/84ebc254a8854ade3c1ed2f6f72243ba5be59329/.github/workflows/test-chart.yaml#L372-L377):
```yaml
# ref: https://github.com/jupyterhub/action-k8s-namespace-report
- name: Kubernetes namespace report
uses: jupyterhub/action-k8s-namespace-report@v1
if: always()
with:
important-workloads: deploy/hub deploy/proxy
```
This is how it looks, where it will help provide logs of relevance when it detects something that has errored, or always emit logs by having a workload declared under "important-workloads".

Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the GitHub Actions workflow that runs tests in a Kubernetes cluster; the issue does not name a repository workflow file. Compare its failure handling with the provided action-k8s-namespace-report example and verify the report appears for failed cluster tests. Done means relevant workload logs are included in CI output when failures occur.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, kubernetes
- Domain
- ci-cd, devops, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100