Skip to content
This repository has been archived by the owner on May 9, 2020. It is now read-only.

use new 'kubectl get all' ? #7

Open
joemiller opened this issue Apr 20, 2017 · 2 comments
Open

use new 'kubectl get all' ? #7

joemiller opened this issue Apr 20, 2017 · 2 comments

Comments

@joemiller
Copy link
Contributor

kubectl get now has an 'all' flag.

@spheromak
Copy link
Contributor

I think so prob should PR that, cause as-is it is going to miss stuff

@joemiller
Copy link
Contributor Author

joemiller commented Jun 7, 2017

a couple issues:

  1. it doesn't actually 'get all' resources, the name is a lie. We know this from our styx and valhalla makefiles 'status-cluster' tasks, although I forget which resources it wasn't pulling. This might be fixed in kubectl 1.6 though. It appears that it still doesn't get TPRs though.

  2. get all means we would lose the ability to split up individually by object. We know from our only recovery event that being able to individually recover objects was critical. If they're all lumped into a giant file then you need to split them up. We can do that at backup time perhaps by adding additional code. I don't want to have to do that at recovery time though when time is a critical, scarce resource.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants