Define a strategy for certs for brokers

[vaikas]

Some brokers (especially internal ones, or testing ones) do not have proper certs and we probably do not even install proper roots in our containers. This issue tracks defining a procedure for doing this:

1. install proper root certs
2. define a process for adding additional ones for organizations

[arschles]

@vaikas-google do you consider the following to be a solution:

1. Install standard CA roots to the controller-manager Dockerfile
2. Default to standard TLS (without InsecureSkipVerify) for all controller-to-broker communication
3. Add a new brokerSecurity field to the Broker resource, which has the following possible values: full (default), skipVerify (which sets InsecureSkipVerify), and none

I haven't closely followed the discussion on what exactly hasn't worked for the various brokers, so please let me know if I'm missing something here.

[arschles]

Punting this to beta to decide.

[vaikas]

Yeah, so I think that this works for certs from roots. I'd be curious if there are organizations that would be running with their own CAs and in that case how we would be adding additional certs for those.

[pmorie]

Idea: control insecure-skip-verify like so:

type BrokerSpec struct {
  // other fields omitted

  Insecure *bool
}

[arschles]

Moving to 1.0.0, since we can already support brokers with root CAs now

[pmorie]

I have a strong need for this in beta. Adding to the agenda to discuss in the July 24 2017 SIG meeting.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[mszostok]

/remove-lifecycle rotten
/lifecycle frozen

[mrbobbytables]

This project is being archived, closing open issues and PRs.
Please see this PR for more information: kubernetes/community#6632