mirror of
https://github.com/optim-enterprises-bv/kubernetes.git
synced 2025-11-01 10:48:15 +00:00
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:
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user