velero-io/velero

Have the Velero CLI use the active namespace in the current context

Open

#3,194 opened on Dec 16, 2020

View on GitHub
 (17 comments) (0 reactions) (0 assignees)Go (1,550 forks)auto 404
Area/CLIEnhancement/UserGood first issueHelp wantedReviewed Q2 2021kind/requirement

Repository metrics

Stars
 (10,111 stars)
PR merge metrics
 (PR metrics pending)

Description

I thought we had an issue for this but couldn't find it.

Currently, the Velero CLI uses the velero namespace in the current context, unless otherwise specified. This means that if you are operating under a namespace other than velero, you have to specify the namespace with every single command.

As it is common with other tools, invert things and make it so Velero recognizes and uses the active namespace, unless otherwise specified.

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

  • :+1: for "The project would be better with this feature added"
  • :-1: for "This feature will not enhance the project in a meaningful way"

Contributor guide

Research direction
Modify the Velero CLI to default to the active Kubernetes namespace from the current context instead of always using 'velero'. Look at where the namespace flag is defined and how it defaults; then change the default to use the namespace from the kubeconfig context.
Tech stack
go
Domain
clibackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70