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

nhctl exec don't support app deployed as statefulset #902

Closed
von1994 opened this issue Sep 1, 2021 · 6 comments · Fixed by #903
Closed

nhctl exec don't support app deployed as statefulset #902

von1994 opened this issue Sep 1, 2021 · 6 comments · Fixed by #903

Comments

@von1994
Copy link

von1994 commented Sep 1, 2021

What happened:
My app workload type is statefulset. I use goland and nocalhost plugin to start remote dev. When I click the button "Run"(nocalhost run config), the comand is like "nhctl exec test --deployment test-my-operator --controller-type statefulset --command /bin/zsh --command -c --command "go run cmd/my-operator/ma
in.go" --kubeconfig ~/.nh/intellij-plugin/kubeConfigs/d9ca5ba8-5a30-4dec-a2c9-d8ba313f0218_config --namespace default ",and the return error is " deployments.apps "test-my-operator" not found"

What you expected to happen:
No error returned.

How to reproduce it (as minimally and precisely as possible):
App workload type is statefulset and start remote dev by click "Run"(run configured as nocalhost need)

Anything else we need to know?:
The func ListPodsByDeployment only handle deployment resource.

Environment:

  • OS (e.g: Macos 10.15.5 (19F96) or Windows 10): macOS 11.5.1
  • nhctl version (use nchtl version command): 0.5.1(0.5.4 is also the same)
  • helm version (use helm version command): none
  • kubectl version (use kubectl version command):
  • Others: nocalhost plugin version 0.5.1-211
  • IDE: GoLand 2021-01
@anurnomeru
Copy link
Member

we will supports soon!

@wencaiwulue
Copy link
Contributor

you are right, we will support this feature on next version, please keep on follow us :)

@von1994
Copy link
Author

von1994 commented Sep 1, 2021

you are right, we will support this feature on next version, please keep on follow us :)

Thanks for your reply! Is there a roadmap or plan date?

@anurnomeru anurnomeru pinned this issue Sep 1, 2021
@anurnomeru anurnomeru unpinned this issue Sep 1, 2021
@anurnomeru anurnomeru linked a pull request Sep 1, 2021 that will close this issue
@neaped
Copy link
Contributor

neaped commented Sep 1, 2021

you are right, we will support this feature on next version, please keep on follow us :)

Thanks for your reply! Is there a roadmap or plan date?

Hi, we will release this feature within this week.

@anurnomeru
Copy link
Member

We will release a new version in recent days, and we have a pr to fix this issue. #903

@von1994
Copy link
Author

von1994 commented Sep 8, 2021

Version 0.5.5 has fixed this issue.

@von1994 von1994 closed this as completed Sep 8, 2021
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

Successfully merging a pull request may close this issue.

4 participants