https://jira.akraino.org This file is an XML representation of an issue en-us 9.4.5 940005 11-04-2023 https://jira.akraino.org/browse/ICN-383 Integrated Cloud Native NFV <p>In <a href="https://wiki.onap.org/pages/viewpage.action?pageId=76875956" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.onap.org/pages/viewpage.action?pageId=76875956</a>, it is claimed Kubeconfig API is a work in progress. Investigate what is the status of this and prepare next steps.</p> ICN-383

Evaluate "Kubeconfig API (WORK IN PROGRESS)"

Story Medium Done Done Igor Duarte Cardoso Igor Duarte Cardoso Wed, 17 Jun 2020 19:45:15 +0000 Thu, 17 Dec 2020 00:54:42 +0000 Tue, 28 Jul 2020 21:26:28 +0000 0 1 <p>The conclusion is that this API (for obtaining the kubeconfig of a cluster of a logical cloud directly from dcm) is not implemented at all. rsync will get the kubeconfig from dcm, which is enough to get the logical resources installed in each cluster. However, a different kubeconfig needs to be created so that it can be handed to the owners of the logical clouds. This is why we need this specific kubeconfig API in dcm itself. A different task should be created in the future in order to implement a custom kubeconfig (with the right user, permissions, etc) per cluster in logical cloud. Closing story.</p> Development Epic Link ICN-214 Rank 0|i004bo: Sprint ICN Sprint 20 ICN Sprint 21 ICN Sprint 22 Story Points 1.0