bitovi / bitovi/bitops

Facilitate local/minikube development

Open
#105 6 comments 0 reactions 0 assignees View on GitHub
enhancement ✨
Dominant language
Python
Stars
37
Forks
9
PR merge metrics
No merged PRs in 30d

Description

**Problem**: it's error-prone to test bitops changes locally and difficult to test any helm changes locally for sufficiently complex helm projects and most bitops scripts.

**Solution**: add minikube as a deploy target, update scripts so they can be run locally, and discuss other enhancements below.

I see a few options:
1. Add 'minikube' support: could run before helm + allow us to do things like `minikube addons enable ingress` / `minikube addons enable metrics-server`
- Would be nice to conditionally enable or disable entire environments or tools based on bitops config or the environment
- No issue yet, but there's a blog ticket after: https://github.com/bitovi/bitops/issues/108
1. Update scripts to easily be run locally/debug/refactor
- Things like: usage info, options, separating parameters + `ENV_VARS` would all make these scripts be easier to run and debug locally. Not directly related to deploying to minikube, but would be helpful for local _bitops_ development and debugging
- We might also want to adopt a style guide ([example](https://google.github.io/styleguide/shellguide.html)) or add something like shellcheck to CI
1. Does running helm tests fit in here?
- Likely not, this seems like something we can support with `helm upgrade`-- but we haven't confirmed yet
1. ~Do we need shell unit tests?~ https://github.com/bitovi/bitops/issues/106
1. ~Is there a standard way we could set up debugging? `DEBUG=1` is inconsistently used in some scripts and `set -x` adds a lot of noise/potentially sensitive values to log files.~ https://github.com/bitovi/bitops/issues/88
1. Does (1) require us to support ordered or dependent deployments? E.g. only deploy helm after minikube, or allow users to specify an order
- https://github.com/bitovi/bitops/issues/63
2. ~Diffing environments~ https://github.com/bitovi/bitops/issues/107 and/or https://github.com/bitovi/bitops/issues/102
3. Generating environments + generating minikube setup scritps for a "local" dev env

Contributor guide

Open the contributing guide

Research direction

Start by determining which proposed option is in scope: Minikube deployment support, locally runnable and debuggable scripts, Helm testing, or local environment generation. Read the existing deployment and Helm-related scripts, then define a single workflow and its acceptance checks; the issue does not currently identify files, tests, or a finished outcome.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes, shell
Domain
devops, infrastructure, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.