Not pulling in etcd v3 client as dependency about apiserver HOT 8 CLOSED

/sig apimachinery

cc: @deads2k @sttts

from apiserver.

cc: @lavalamp

from apiserver.

Thanks for the issue, I agree it's good to avoid extra dependencies.

Tagging @deads2k since I'm not sure how much attention folks pay to the issues in this repo (as opposed to the main one).

from apiserver.

Thanks for the issue, I agree it's good to avoid extra dependencies.

Tagging @deads2k since I'm not sure how much attention folks pay to the issues in this repo (as opposed to the main one).

Extra is relative. I'd be open trying to associate it with etcd options in a subpackage, but I think that it needs to remain in apiserver.

from apiserver.

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

from apiserver.

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

from apiserver.

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

from apiserver.

@fejta-bot: Closing this issue.

from apiserver.