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.

Sign up for GitHub

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

Jump to bottom

Support for kubectl like --context flag in odo #6820

Open
valaparthvi opened this issue May 16, 2023 · 4 comments
Open

Support for kubectl like --context flag in odo #6820

valaparthvi opened this issue May 16, 2023 · 4 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.

Comments

@valaparthvi
Copy link
Contributor

valaparthvi commented May 16, 2023 •
edited by rm3l
Loading

/kind feature

Which functionality do you think we should add?

Just like kubectl provider --context flag to fetch a Kubernetes context specific information, odo could also support such a feature.

Why is this needed?

It can be a nice to have feature when you don't want to explicitly change the Kubernetes context for all terminal sessions.
@openshift-ci openshift-ci bot added the kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation label May 16, 2023
@valaparthvi valaparthvi added priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done. and removed kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation labels May 16, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label May 16, 2023
@feloy
Copy link
Contributor

feloy commented May 17, 2023

@valaparthvi Can you elaborate which odo context would you like to pass with this flag? The directory on which it will work? The Kubernetes context it will use?

@valaparthvi
Copy link
Contributor Author

@valaparthvi Can you elaborate which odo context would you like to pass with this flag? The directory on which it will work? The Kubernetes context it will use?

The Kubernetes context.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 31, 2023
@rm3l rm3l removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. labels Aug 31, 2023
@redhat-developer redhat-developer deleted a comment from github-actions bot Aug 31, 2023
@github-actions GitHub Actions
Copy link
Contributor

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 30, 2023
@rm3l
Copy link
Member

rm3l commented Dec 1, 2023

/remove-lifecycle stale
/lifecycle frozen

@openshift-ci openshift-ci bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.
Projects
odo Project
Status: No status
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rm3l @feloy @valaparthvi