bpfman / bpfman/bpfman-operator
`make run-on-kind` enhancements
- Dominant language
- Go
- Stars
- 38
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
By default, `make run-on-kind`
- builds and uses local images for `bpfman-operator` and `bpfman-agent`
- uses the remote version of `quay.io/bpfman/bpfman:latest`
Consider adding the following new options:
`BPFMAN_LOCAL=1 make run-on-kind`
- uses the local version of whatever `BPFMAN_IMG` is set to
- by default, this is the local version of `quay.io/bpfman/bpfman:latest`
`BPFMAN_REMOTE=1 make run-on-kind`
- use the remote versions of everything
- This allows someone to quickly spin up a cluster w/bpfman without building anything for kicking the tires or testing.
_Originally posted by @anfredette in https://github.com/bpfman/bpfman-operator/issues/113#issuecomment-2316075225_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Makefile entry point for `run-on-kind` and tracing how it selects local or remote images and the `BPFMAN_IMG` value. Done means the default behavior remains unchanged, `BPFMAN_LOCAL=1` uses the local bpfman image, and `BPFMAN_REMOTE=1` uses remote images for everything.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100