Skip to content
This repository was archived by the owner on Apr 17, 2025. It is now read-only.

Use the default namespace in the kubeconfig #347

Closed
superbrothers opened this issue Nov 15, 2023 · 5 comments · Fixed by #348
Closed

Use the default namespace in the kubeconfig #347

superbrothers opened this issue Nov 15, 2023 · 5 comments · Fixed by #348
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@superbrothers
Copy link
Contributor

hns command will fail to execute if the -namespace option is not specified.

$ kubectl hns create foo
Error: parent must be set via --namespace or -n

On the other hand, kubectl uses the default namespace set in kubeconfig if not specified. I think hns command's behavior should be aligned with kubectl's.

What do you think?

@yanggangtony
Copy link

+1
Make sense for me.

@superbrothers
Copy link
Contributor Author

I'll make a PR.

@yanggangtony
Copy link

I have done it. wait.

@superbrothers
Copy link
Contributor Author

OK. Thanks.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants