Closed ljmatkins closed 6 years ago
/sig federation /cc @kubernetes/sig-federation-feature-requests
@ljmatkins: Reiterating the mentions to trigger a notification: @kubernetes/sig-federation-feature-requests
/sig multicluster
Sounds like a useful feature. @ljmatkins are you willing/able to submit a design proposal?
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. 😄
@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.
This issue was labelled only for sig/multicluster and is thus moved over to kubernetes/federation#9. If this does not seem to be right, please reopen this and notify us @kubernetes/sig-multicluster-misc. /close
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) Runkubectl apply -f resourcedefinition.yaml
against the federated clusterEnvironment:
kubectl version
): 1.7.6