Closed coollog closed 5 years ago
Should we add a KubectlDownloader
as well? Or are we assuming people already have it installed?
@TadCordle We'll assume (and check) that people have it installed. It could come from a variety of places including downloading the binary releases, building from source, installing via gcloud
, etc.
A couple other questions: What are the intended use cases for this class? Should it be more generalized and low-level (i.e. you just pass in the kubectl
flags and options as strings) or should there be specific method calls for each of our use cases (e.g. one for generating the k8s yaml, one of getting logs, etc.)?
@TadCordle
Use cases:
kubectl run...
/kubectl expose ...
)kubectl port-forward ...
)kubectl logs ...
)This class should be more low-level and provide just a wrapper for kubectl
including subcommands and flags. The higher-level actions like generating YAML will be the responsibility of other classes.
Should work similarly to (and share a lot of code with)
Skaffold
in #7.Kubectl
should runkubectl
commands, including but not limited to:kubectl run --dry-run -o yaml
kubectl logs
kubectl port-forward