Guangya Liu
Guangya Liu
Yes, OCP is adding a bunch of extra resources here, like ocp apiserver etc, then in the tenant cluster, it will have not only kube api server, kube controller manager,...
Good, thanks @paurosello and @angelbarrera92 ! @angelbarrera92. your description for org, tenant and space is quite clear, thanks. Look forward to the document from @paurosello :-)
@christopherhein sounds good, thanks!
@christopherhein Awesome! Any document that I can refer? Thanks!
I had same question before at https://github.com/kubernetes-sigs/cluster-api-provider-nested/issues/182 , yes, it will be great if we can support different version of tenant Kubernetes clusters.
@vincent-pli have you ever bump the version of tenant cluster and test? Any suggestions? Thanks!
Thanks @jdef , just append some of my thoughts here: 1) The current revocable resources is kind of "scavenge resources", and the QoS Controller will kill the executors using revocable...
What do you mean of " kill the revocable resources directly for current revocable resources"?
@LeoLiuYan not yet, the SIG-APP has their own CRD for application https://github.com/kubernetes-sigs/application#using-the-application-crd
Thanks @wonderflow and @xiang90 , do you have any recommendations for what is the best user scenario compared between kubernetes-sigs/application and OAM?