Repository navigation
fix(devspace): select the deployed pods and stop forwarding a port - #32
Merged
Merged
Conversation
The selectors named app.kubernetes.io/instance=authorization, but the umbrella labels every subchart with the release name — instance is agyn-platform. Nothing matched, so `devspace dev` failed outright on the patch hook and then waited forever for a pod that its own selector could never find. Selecting by service name alone matches either way. The port forward is dropped with it: authorization is reached in-cluster, and binding 50051 on the host takes a port from whatever else wants it for no benefit. Co-Authored-By: Claude <noreply@anthropic.com>
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
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.
The selectors named
app.kubernetes.io/instance=authorization, but the umbrella labels every subchart with the release name —instance=agyn-platform. Nothing matched, sodevspace devfailed on the patch hook with a jsonpath error against an empty list, and after that waited indefinitely for a pod its own selector could never find. Selecting by service name alone matches under either deployment.Both places needed it: the
AUTHORIZATION_SELECTORused by the patch hook, and thedev:block's ownlabelSelector.The host port forward goes with it — authorization is reached in-cluster, and binding 50051 on the developer's machine takes a port from whatever else wants it for no benefit.
Found while running authorization from source to verify the
can_list_sandboxesmodel fix; without this, devspace cannot start this service at all.