Refactor kubectl proxy command to have similar design pattern as other kubectl commands.

Few days ago I watched this kubectl code base tour on Youtube
(https://www.youtube.com/watch?v=uz8TS3V9qqY). It talks about a design
pattern that almost every command follows. But I found out that
`kubectl proxy` command does not follow this pattern. So, I'm
refactoring this command to use similar design pattern as other kubectl
commands.
This commit is contained in:
Anish Shah
2019-09-21 10:52:42 -07:00
parent 2bc9f45512
commit 0bd41a300f
3 changed files with 112 additions and 58 deletions

View File

@@ -513,6 +513,7 @@ staging/src/k8s.io/kubectl/pkg/cmd/logs
staging/src/k8s.io/kubectl/pkg/cmd/patch
staging/src/k8s.io/kubectl/pkg/cmd/plugin
staging/src/k8s.io/kubectl/pkg/cmd/portforward
staging/src/k8s.io/kubectl/pkg/cmd/proxy
staging/src/k8s.io/kubectl/pkg/cmd/replace
staging/src/k8s.io/kubectl/pkg/cmd/rollingupdate
staging/src/k8s.io/kubectl/pkg/cmd/rollout