oxidecomputer / oxidecomputer/oxide-cloud-controller-manager
Add a kind-based e2e smoke test
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6
- Forks
- 2
- Avg merge
- 2h 5m
- Merged PRs (30d)
- 14
Description
Context
Unit tests can't catch framework-wiring regressions — RBAC gaps, flag changes, leader-election issues — that surface when k8s.io packages get bumped (which Dependabot does regularly in this repo).
Scope
Add a CI job that:
- Starts a kind cluster with
--cloud-provider=external. - Runs the CCM binary against a stub Oxide API server.
- Verifies a node loses the
node.cloudprovider.kubernetes.io/uninitializedtaint and gets a provider ID set.
Done when
The job runs in CI on PRs and fails if node initialization doesn't complete.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No file or test path is named. Start by locating the repository's CI workflows, CCM binary entry point, and any existing integration-test or kind setup; then determine how a stub Oxide API server is used. Done means a PR CI job starts the requested kind cluster, runs the CCM, and verifies the node loses the uninitialized taint and receives a provider ID.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- ci-cd, cloud, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100