8000 [bug] pxctl component should allow use of custom namespace · Issue #151 · portworx/pxc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Mar 26, 2025. It is now read-only.

[bug] pxctl component should allow use of custom namespace #151

Open
piyush-nimbalkar opened this issue Jul 8, 2020 · 1 comment
Open

[bug] pxctl component should allow use of custom A99D namespace #151

piyush-nimbalkar opened this issue Jul 8, 2020 · 1 comment
Assignees
@lpabon
Labels
bug Something isn't working

Comments

@piyush-nimbalkar
Copy link

Describe the bug

  • pxc was configured to use cluster in given namespace
    kubectl pxc config cluster set --name=xxx --portworx-service-namespace=portworx

  • pxc pxctl always connects to pods in kube-system namespace ignoring the above

kubectl pxc pxctl status
>> Running pxctl on k8s-node-2
No resources found in kube-system namespace.
error: expected 'exec (POD | TYPE/NAME) COMMAND [ARG1] [ARG2] ... [ARGN]'.
POD or TYPE/NAME and COMMAND are required arguments for the exec command
See 'kubectl exec -h' for help and examples

Version

Client Version: v0.28.0
Client SDK Version: 0.42.22

Additional Information
@piyush-nimbalkar piyush-nimbalkar added the bug Something isn't working label Jul 8, 2020
@lpabon
Copy link
Contributor
lpabon commented Jul 15, 2020

Ah yes, the pxc-pxctl component is pretty 'hacky'. I will have to start making it more of a real component.

@lpabon lpabon self-assigned this Jul 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@lpabon lpabon

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@piyush-nimbalkar @lpabon
0