You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i think it should take cloud provider into consideration, after oci spec, more and more developer started to use oci registry to hosted private charts instead of standard chart repo
Thank you for pointing this out! Considering the growing adoption of the OCI specification, it makes sense to account for cloud provider integration and support for OCI registries. With more developers leveraging OCI registries to host private charts, incorporating this into the design would align with modern best practices. I'll explore how we can extend support for OCI-based workflows while maintaining compatibility with standard chart repositories. Let me know if you have any specific suggestions or use cases in mind! 🚀
For example: a button on Repositories section allowing to look up the repository with chart that I remember, and add it.
Kinda part of onboarding flow, something that would be useful for a user with completely empty cluster (but not only).
The text was updated successfully, but these errors were encountered: