image-2020-09-29-20-39-35-378.png
[ICN-474] Implement grpc-based kubeconfig generation Created: 30/Sep/20 Updated: 22/Oct/20 Resolved: 22/Oct/20 |
|
| Status: | Done |
| Project: | Integrated Cloud Native NFV |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Low |
| Reporter: | Igor Duarte Cardoso | Assignee: | Igor Duarte Cardoso |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
image-2020-09-29-20-39-35-378.png
|
| Epic Link: | DCM dev works |
| Story Points: | 3 |
| Description |
|
Instead of generating kubeconfigs when the client calls the API the first time, DCM should wait for a grpc notification from rsync to let it know when the logical cloud is ready, which should then trigger code that will generate kubeconfig(s) in the background and store then in the DB. |
| Comments |
| Comment by Igor Duarte Cardoso [ 22/Oct/20 ] |
|
Migrated to EMCO tracking. |