Jeffrey Regan 7abff879d7 Introduce visibility rules to kubernetes code. ... **What this PR does / why we need it**: Visibility rules allow dependency control. The rules currently in place make all targets public, to override the default state of private. This PR removes public visibility from kubectl code. It uses specially named pacakge groups to identify "bad" dependencies on kubectl code for later refactoring or removal. **Which issue this PR fixes** First in a series of PRs to address kubernetes/community#598 **Release note**: ```release-note NONE ```		2017-05-15 12:50:56 -07:00
..
BUILD	Introduce visibility rules to kubernetes code.	2017-05-15 12:50:56 -07:00
helper.go	pkg/util: move uuid and strategicpatch into k8s.io/apimachinery	2017-01-25 19:45:09 +01:00
set.go	add set rolebinding/clusterrolebinding command	2017-05-05 09:55:35 +08:00
set_image.go	use of --local should completely eliminate communication with API server	2017-05-03 15:57:57 -05:00
set_image_test.go	use of --local should completely eliminate communication with API server	2017-05-03 15:57:57 -05:00
set_resources.go	use of --local should completely eliminate communication with API server	2017-05-03 15:57:57 -05:00
set_selector.go	kubectl/cmd: remove a bunch of unused parameters	2017-04-04 10:36:30 +01:00
set_selector_test.go	start the apimachinery repo	2017-01-11 09:09:48 -05:00
set_subject.go	add set rolebinding/clusterrolebinding command	2017-05-05 09:55:35 +08:00
set_subject_test.go	add set rolebinding/clusterrolebinding command	2017-05-05 09:55:35 +08:00
set_test.go	add --dry-run opt to `kubectl set image`	2016-12-08 15:50:52 -05:00