Skip to content
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

Unable to connect the local default k8s cluster to helm-wrapper #51

Open
arunavamagi opened this issue Mar 14, 2022 · 4 comments
Open

Comments

@arunavamagi
Copy link

Hi,

Thank you for the tool.
We have build the helm-wrapper docker and running it locally.
How do we configure helm-wrapper API Server to connect to a k8s cluster?

Screenshot 2022-03-14 at 9 17 11 PM

Is there any file where we can set the kubecontext before running the server?

@opskumu
Copy link
Owner

opskumu commented Mar 15, 2022

@arunavamagi helm-wrapper need --kubeconfig options, default value ~/.kube/config

https://github.com/opskumu/helm-wrapper#helm-wrapper-help

@arunavamagi
Copy link
Author

@opskumu I understand that part, but since we are running this as a standalone docker, is there any particular method via which we can pass this kubeconfig file to the docker. We were running it via

docker run -p 8080:8080 helm-wrapper:51fa091

currently, but we guess we have to pass runtime options at the time of running. Please correct me if I am wrong.

@arunavamagi
Copy link
Author

@opskumu We are able to build the makefile on linux and then run it as server by passing this command :

./helm-wrapper --config /home/ec2-user/helm-wrapper/bin/config.yaml --kubeconfig ~/.kube/config

but would like to know the method of doing the same via docker.

Screenshot 2022-03-15 at 10 40 20 AM

@opskumu
Copy link
Owner

opskumu commented Mar 15, 2022

@arunavamagi maybe you can use docker -v like:

docker run -v <local_kubeconfig_path>:<container_kubeconfig_path> -p 8080:8080 helm-wrapper:51fa091

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants