k3s/build/visible_to/OWNERS

reviewers:
  - brendandburns
  - dchen1107
  - ixdy
  - jbeda
  - lavalamp
  - mikedanese
  - monopole
  - pwittrock
  - smarterclayton
  - thockin
approvers:
  - bgrant0607
  - brendandburns
  - dchen1107
  - ixdy
  - jbeda
  - lavalamp
  - mikedanese
  - monopole
  - pwittrock
  - smarterclayton
  - thockin
  - wojtek-t
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-04-21 23:59:59 +00:00			`reviewers:`
			`- brendandburns`
			`- dchen1107`
			`- ixdy`
			`- jbeda`
			`- lavalamp`
			`- mikedanese`
Fix my incorrect username in #46649 My mistake - used goog username rather than github. 2017-06-06 19:39:40 +00:00			`- monopole`
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-04-21 23:59:59 +00:00			`- pwittrock`
			`- smarterclayton`
			`- thockin`
			`approvers:`
			`- bgrant0607`
			`- brendandburns`
			`- dchen1107`
			`- ixdy`
			`- jbeda`
			`- lavalamp`
			`- mikedanese`
Fix my incorrect username in #46649 My mistake - used goog username rather than github. 2017-06-06 19:39:40 +00:00			`- monopole`
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-04-21 23:59:59 +00:00			`- pwittrock`
			`- smarterclayton`
			`- thockin`
			`- wojtek-t`