We have opened a RFC period for Proposal 2730: Improve visibility into management and workload cluster creation[0]. A detailed design document is referenced within this issue.
Please add any high-level feedback to the issue[0].
Please add any implementation-specific questions or suggestions to the design document PR[1].
Our goal with this proposal is to help end-users make sense of what happens when they create workload and management clusters. Since our first release (v0.9.1), we have seen multiple users struggle to get bootstrapped. At times, errors are buried deep in the logs of the bootstrap cluster. A common example is attempting to bootstrap when AWS service quotas[2] are reached, causing an inability to create a resource. Today, users get little visibility into such failures without digging into the bootstrap cluster and reviewing logs.
The RFC window is initially open until 02/04/2021. We will extend if needed.
Thanks for any and all input!
[0]: https://github.com/vmware-tanzu/community-edition/issues/2730
[1]: https://github.com/vmware-tanzu/community-edition/pull/2769/files
[2]: https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html
---
--
You received this message because you are subscribed to the Google Groups "Tanzu Community Edition" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tanzu-community-e...@googlegroups.com.
To view this discussion on the web visit https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Ftanzu-community-edition%2FCY4PR05MB34314B856B59B469DD51A562B7589%2540CY4PR05MB3431.namprd05.prod.outlook.com&data=04%7C01%7Crossoj%40vmware.com%7Cc5435f7e870f416bc55b08d9dad7c6ff%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637781442565135417%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=8wBqa4pkKjq8o30GEXLLQIAOWgXxt6inMdpfz2fzdR0%3D&reserved=0.