wagoodman/bridgy

Support a Kubernetes backend

Open

#31 opened on Oct 3, 2018

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Python (52 forks)github user discovery
Hacktoberfestenhancement

Repository metrics

Stars
 (416 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

It would ideal to allow for tracking of assets in Kubernetes. This would further extend the exec command to get a shell into one or more containers (or all containers in a pod with tmux).

This is a good starting point for how the mechanisms of streaming to/from the container (seems more kosher than wrapping kubectl): https://github.com/kubernetes-client/python/blob/master/examples/exec.py

Contributor guide

Research direction
Study the referenced Kubernetes Python client example to understand exec streaming. Then examine bridgy's current exec command implementation to see how to integrate a Kubernetes backend.
Tech stack
pythonkubernetes
Domain
backendclouddevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonKubernetes concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45