Shyam Sankaran
Shyam Sankaran
> How about we create separate GitHub issues for each service? More like sub tasks. GitHub supports that. Example - [pingcap/tidb#28010](https://github.com/pingcap/tidb/issues/28010) (issue) , [pingcap/tidb#26747](https://github.com/pingcap/tidb/issues/26747) (super issue for tracking), [pingcap/tidb#26022](https://github.com/pingcap/tidb/issues/26022) (super...
I think you'll need to maintainer access to do that. The issues have links to pr, do you want to add the pr links here directly as well?
/remove-lifecycle stale
/remove-lifecycle stale
+1 to moving it out of experimental, but since capz managed clusters cannot run without machine pool, should we wait for machine pool to be moved out of exp?
/remove-lifecycle rotten
/remove-lifecycle stale
/remove-lifecycle stale
/remove-lifecycle rotten
/remove-lifecycle stale