fix(devspace): find the pod by name, not by release - #29
Merged
Conversation
The selector paired app.kubernetes.io/name with app.kubernetes.io/instance=<service>. That held when each service was its own Helm release; the platform umbrella makes the instance label its own release name, so it matches nothing: DevSpace still couldn't find any Pods that match the selector The pod comes up and waits for a binary the sync never delivers, and the deploy times out having patched a Deployment it then cannot reach. The name label alone is unique in the namespace and holds either way.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Deploying this service from source into the platform VM hangs:
The
devselector pairedapp.kubernetes.io/namewithapp.kubernetes.io/instance=<service>. That held when every service was its own Helm release. The agyn-platform umbrella makes the instance label its own release name, so the selector matches nothing — verified against a running VM, where the pod carriesapp.kubernetes.io/instance: agyn-platform.The pod starts and spins waiting for a binary the sync never delivers, and the deploy times out having already patched a Deployment it cannot reach.
The
namelabel alone is unique in the namespace and is correct under both layouts. Same fix as the E2E workflow’s own selectors.