Open denis-tingaikin opened 2 years ago
Controller is in progress https://github.com/kubernetes-sigs/about-api
@edwarnicke This is blocked while about api in progress.
Should we just wait for the about-api release?
@denis-tingaikin https://github.com/kubernetes/enhancements/tree/master/keps/sig-multicluster/2149-clusterid#property-idk8sio is a CRD. It is either already set when we run our admissions controller, in which case we simply use it's value, or it isn't in which case we should setup the CRD and set it to a value ourselves.
Its not at all clear to me what the https://github.com/kubernetes-sigs/about-api controller would do, or when it would expect to be in GA.
@denis-tingaikin https://github.com/kubernetes/enhancements/tree/master/keps/sig-multicluster/2149-clusterid#property-idk8sio is a CRD. It is either already set when we run our admissions controller, in which case we simply use it's value, or it isn't in which case we should setup the CRD and set it to a value ourselves.
Yeah, that what we are planning to do when https://github.com/kubernetes-sigs/about-api will be ready.
Currently, as I can see CRD is not ready and is not using in k8s. Correct me if I wrong.
See at cluster propery defenition in https://github.com/kubernetes-sigs/about-api/blob/master/clusterproperty/config/crd/bases/about.k8s.io_clusterproperties.yaml
@denis-tingaikin Yes... but what is the controller doing other than adding the CRD? Is there any reason for us not to add the CRD if its not already present?
Description
Currently
clientinfo
chain element can work with CLUSTER_NAME env https://github.com/networkservicemesh/sdk/blob/main/pkg/tools/clientinfo/clientinfo.go#L30But we dont use it yet, because k8s at this moment doesn't have an option to get cluster name without any special complex steps.
Solution