Cluster API issues about cluster-registry

[perotinus]

cc @madhusudancs

[perotinus]

Updates for the above points:

1. After discussion with SIG-auth, we made the decision to go with a generic type for auth, and to heavily discourage storing credentials in the cluster registry
2. No update
3. We will use an Endpoints object copied from the k8s API.
4. We resolved these discussions in favor of spec/status
5. Assuming lazy consensus, we are going with what's there now.

[madhusudancs]

I made this comment on the PR #31. But I am noticing this issue now. So copying the comment here.

I am really confused. Copying Endpoints object seems incorrect. For example, what purpose would EndpointPort.Protocol serve? If anything, this should mirror what's in federation now. I can't see all the fields in Kubernetes core api/v1.Endpoint being appropriate here.

[madhusudancs]

I think if we are copying anything, what's in federation today is far more useful than copying api/v1.Endpoint.

[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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

[perotinus]

/remove-lifecycle stale

[perotinus]

I believe that all of these issues have been addressed. Closing.