Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
fabric8:debug ignores pod's namespace
See original GitHub issueDescription
Command fabric8:debug always references a pod in the default namespace.
The commad line is missing -n <namespace> argument.
Info
- f-m-p version: 3.5.38
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
fabric8io/kubernetes-client - Gitter
I'm getting some debug logs from the fabric8 k8s client (while using the spring ... Config - Trying to configure client namespace from...
Read more >fabric8io/fabric8-maven-plugin
Labels and annotations applied pod specification as used in ReplicationController , ReplicaSets , Deployments and DeploymentConfigs objects.
Read more >io.fabric8.kubernetes.api.model.apps.StatefulSet.getMetadata ...
Asynchronously perform a rolling update of all the pods in the StatefulSet identified by the given * {@code namespace} and {@code name}, returning...
Read more >Break in fabric8 kubernetes client mock server - Stack Overflow
... /127.0.0.1:49882] DEBUG io.fabric8.kubernetes.client.server.mock.KubernetesAttributesExtractor - fromPath /api/v1/namespaces/test/pods?
Read more >Debug Running Pods | Kubernetes
This page explains how to debug Pods running (or crashing) on a Node. ... Name: nginx-deployment-67d4bdd6f5-w6kd7 Namespace: default ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@gintautassulskus: I agree with @dev-gaur here. I misunderstood it a bit… As far as I know we don’t support debugging in namespaces other than your current namespace,.
fabric8:debugopens debug port so that you can debug the latest pod in the namespace you deployed(which is the default namespace you’re logged into).Would really appreciate if you could elaborate what problem exactly are you facing?
@rohanKanojia, thanks for clarifying. I must have misunderstood the behaviour hence the raised issue. I will close the case.