Adel Zaalouk
Adel Zaalouk
Thanks @wawa0210, I have incorporated your comments, and amended the context. Thank you for your collaboration and swift responses on the review.
I see two distinct problems: 1. Identify the means _`"for disparate groups to collaborate around a common problem"`_ (cc @dims). A concrete example here is [#hosted-controlplanes](https://cloud-native.slack.com/archives/C06QKJ209NH/p1714494821570939). Those groups typically have...
looks good. Thanks @xenolinux
To add to what @danielfoehrKn wrote, we are using calico v3.13.4.
> Separate from this issue, do you guys know why you're encountering this? Sounds like it could be a bug. Might be worth opening another issue just to discuss this...
@yanxi0830 these might be related: - https://github.com/meta-llama/llama-stack/issues/1232 - https://github.com/meta-llama/llama-stack/pull/1290
@ronaldpetty, it's currently under workload observability. It makes sense if we don't introduce new categories, but asking now if we want to introduce a new category around remediation and troubleshooting?
Background. We broke up the paper into two, originally it was just one.
if we are calling them connectors, should this be called "connectors_registries" to be consistent, in the future we something other than MCP pops up we can add a "type"?