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

Question: Do I need local helm charts, and Kubernetes manifests files if they already exists in the remote cluster? #2933

Open
Mapsfg opened this issue Jan 24, 2025 · 2 comments

Comments

@Mapsfg
Copy link

Mapsfg commented Jan 24, 2025

What if I want to use an existing helm chart that consists of a Kubernetes deployment, and service files that already exists in the remote cluster?

Would I still need to create I need to create these local files in order for Devspace dev mode?
The only features I'd like to use is the hot file sync reload, and remote debugging.

@Mapsfg Mapsfg changed the title Question: Do I need local helm charts, kubernetes manifests files if they already exists in the remote cluster? Question: Do I need local helm charts, and Kubernetes manifests files if they already exists in the remote cluster? Jan 24, 2025
@CCOLLOT
Copy link

CCOLLOT commented Jan 24, 2025

If you don't specify the deployment section then devspace will not try to deploy anything. All you need is to provide (in the dev section) an image selector or label selector to select the pod to replace with a dev container you can sync your code to.

@deniseschannon
Copy link

@Mapsfg Were you able to try out what @CCOLLOT suggested?

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

3 participants