search

kubernetes-retired / federation

[EOL] Cluster Federation
Apache License 2.0
210 stars 82 forks source link

CustomResourceDefinition support for federation #9

Closed irfanurrehman closed 5 years ago

irfanurrehman commented 6 years ago

Issue by ljmatkins Wednesday Oct 04, 2017 at 12:58 GMT Originally opened as https://github.com/kubernetes/kubernetes/issues/53432

Is this a BUG REPORT or FEATURE REQUEST?: /kind feature

What happened: When I attempt to kubectl apply a CustomResourceDefinition to a federation, I receive the following error:

error: unable to recognize "resourcedefinition.yaml": no matches for apiextensions.k8s.io/, Kind=CustomResourceDefinition

What you expected to happen:

It would be nice if federations supported this resource type, so that we can run applications expecting it on top of federated clusters.

How to reproduce it (as minimally and precisely as possible):

1) Bring up a federated cluster 2) Create a resourcedefinition.yaml file (e.g. https://kubernetes.io/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/) 2) Run kubectl apply -f resourcedefinition.yaml against the federated cluster

Environment:

irfanurrehman commented 6 years ago

Comment by ljmatkins Wednesday Oct 04, 2017 at 13:01 GMT

/sig federation /cc @kubernetes/sig-federation-feature-requests

irfanurrehman commented 6 years ago

Comment by k8s-ci-robot Wednesday Oct 04, 2017 at 13:02 GMT

@ljmatkins: Reiterating the mentions to trigger a notification: @kubernetes/sig-federation-feature-requests

In response to [this](https://github.com/kubernetes/kubernetes/issues/53432#issuecomment-334147584): >/sig federation >/cc @kubernetes/sig-federation-feature-requests Instructions for interacting with me using PR comments are available [here](https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
irfanurrehman commented 6 years ago

Comment by quinton-hoole Tuesday Oct 10, 2017 at 18:44 GMT

/sig multicluster

irfanurrehman commented 6 years ago

Comment by quinton-hoole Tuesday Oct 10, 2017 at 18:45 GMT

Sounds like a useful feature. @ljmatkins are you willing/able to submit a design proposal?

irfanurrehman commented 6 years ago

Comment by ljmatkins Wednesday Oct 11, 2017 at 21:26 GMT

While willing, I'm not yet sufficiently familiar with the k8s federation design to provide much input!

I had some vague sense that this could maybe "just work like ConfigMaps or Secrets" -- although that might just be wishful thinking. 😄

irfanurrehman commented 6 years ago

Comment by quinton-hoole Wednesday Oct 11, 2017 at 22:27 GMT

@ljmatkins I think you're probably right, but someone would need to think through the details. Even if you don't design the internal implementation, if you could describe what you would like it to look like from the outside (i.e. how the API would look and behave, in your ideal world), that would be useful.

fejta-bot commented 6 years ago

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

nikhita commented 6 years ago

/remove-lifecycle stale /lifecycle frozen