New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[K8s] Parametrize tox task #8531
Conversation
tox.ini
Outdated
@@ -981,23 +984,29 @@ commands = | |||
description = Deploy Syft to a local Kubernetes cluster with Devspace | |||
changedir = {toxinidir}/packages/grid | |||
passenv=HOME, USER | |||
setenv= | |||
KUBE_CONTEXT = {env:KUBE_CONTEXT:k3d-syft-dev} | |||
DEVSPACE_PROFILE = {env:DEVSPACE_PROFILE:} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For launching gateway it could be like
CLUSTER_NAME="syft-gateway" NODE_PORT=9081 tox -e dev.k8s.start
KUBE_CONTEXT="k3d-syft-gateway" DEVSPACE_PROFILE="-p gateway" tox -e dev.k8s.hotreload
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since kubecontext is basically k3d-$CLUSTER_NAME
, it's redundant. I'll push an update for this.
Thank you for the cleanup @yashgorana , the commands are even more simpler now |
Description
Currently, for launching multiple clusters or same machine , we would have to manually modify the config in tox or deploy one by helm and other by devspace.
The PR adds parametrization by environment variables, until we have syft cli, which automates deployment of multiple clusters on local machine
How has this been tested?
Manually
Checklist