Mark Pundsack

This isn't going to be in 1.17. Since we have other ways to do local development, is this even a priority anymore?

@rajivml Thanks for the feedback. To be clear, when you're talking about warnings here, you really mean errors, right? We have a separate issue about not blocking installs based only...

@MikaelSmith Interesting idea. Can you elaborate on the problem and use case? What kinds of labels would you want to apply, where would you want them applied, what are you...

Thanks, that helps.

Tracking internally here: https://app.clubhouse.io/replicated/story/27657 I'm in favor of adding the base kustomization.yaml.

Running preflights *before* installing the admin console could be part of the solution, and could be possible if we made preflights public artifacts that could be fetched without a license,...

IMHO, warnings should not block unattended installations. I was surprised when we blocked web installations for warnings, but understand the decision since it's just a confirmation away. But with unattended,...

Since it's the only setting, maybe we should call it Access; matching the global one? Or would that just add confusion? "Keep these settings in sync" is ambiguous, implying if...

For the checkbox, we'll also have to think through scenarios where the admin console is set up to use a provider that the app doesn't have support for. One suggestion...

Is it being killed because it's exceeding the limit (500Mi), or that it's more than the request, and the cluster doesn't have enough memory?