Cyclops is an open-source dev tool that simplifies Kubernetes with an easy-to-use UI, making it less intimidating. Thanks to our templates, Cyclops turns hours and days of configuring applications into a few clicks.
Hey Product Hunt 👋,
It has been six months since our last launch on this platform, and we are very excited to show you what we have been working on!
What is Cyclops?
We know that Kubernetes can be difficult. That is why we created Cyclops, a truly developer-oriented Kubernetes platform. Abstract the complexities of Kubernetes, and deploy and manage your applications through a UI. Because of its platform nature, the UI itself is highly customizable - you can change it to fit your needs.
How it works?
Cyclops is a platform that allows DevOps teams to quickly and without coding create custom UIs for developers, QA teams, product managers, and other team members who do not necessarily have experience working with Kubernetes.
But don’t worry! If you do not have a DevOps team with you, Cyclops comes with a bunch of predefined templates to get you started!
Under the hood, Cyclops uses Helm charts to create your desired UIs. This means you can try Cyclops with any of your existing Helm charts or any public Helm charts you can find!
What’s new?
🎀 UI redesign and rework of the workflow
📂 Introducing the templates tab and default templates to get you started
🔓 Support for private GitHub repos
⚙️ `cyctl` - our very own command line interface
🔵 Unlock the power of Bitnami charts
Cyclops is fully open-source, your contributions and GitHub stars are very welcome ⭐
@juraj_karadza
Cyclops' focus on simplifying Kubernetes management through a user-friendly interface is a valuable approach. By abstracting complexities and offering customization options, you're addressing a key pain point for many developers and DevOps teams.
Key Questions for Cyclops:
- How does Cyclops handle user authentication, authorization, and role-based access control?
- Does Cyclops integrate with popular CI/CD pipelines and monitoring tools?
- How does Cyclops handle the management of large-scale Kubernetes environments?
Potential for Improvement:
- Incorporating AI to suggest optimal configurations based on workload characteristics could further enhance the platform.
- Providing insights into resource utilization and cost management could be valuable for users.
- Expanding support for multiple cloud platforms (e.g., AWS, GCP, Azure) could increase platform adoption.
As a developer, I'm interested in the technical architecture of Cyclops and its potential for integration with other tools. If these areas align with my skills, I'd be happy to contribute to future development.
Overall, Cyclops offers a promising solution for Kubernetes management. Addressing security, scalability, and integration could further strengthen its value proposition.
Hey @max_savonin1, thanks for the feedback and the awesome questions!
To answer your questions:
- We have a PR open for setting up RBAC via Cerbos here https://github.com/cyclops-ui/cy...
- Recently, we have shipped the cli (cyctl) to go alongside Cyclops. You can use the cyctl to update your apps in a CI step
- Cyclops talks only to your Kubernetes API, so it is portable between clusters and doesn't depend on any architecture
Thanks for the suggested improvements! We were thinking about getting AI into the mix, but at this stage, we fear it might bloat the project and take a lot of time to implement. It's definitely something to think about. The same goes for resource utilization, but it sounds like a great addition.
We have tried running Cyclops on different K8s distros, including managed K8s from AWS, Azure, and GCP, and Cyclops seems to handle it well. It is stateless and has minimal dependencies on your infrastructure—just your K8s API.
To check out the architecture, if you would like to contribute, check out our contributing docs: https://github.com/cyclops-ui/cy.... We love onboarding new contributors, so feel free to pick an issue! :)
Hey Juraj,
Cyclops looks really interesting. I love the idea of simplifying Kubernetes management through a customizable UI.
A few questions:
- How does Cyclops handle security and access controls for the different team members using the custom UIs?
- Are there any limitations on the types of Helm charts that can be used with Cyclops?
- What's your roadmap for adding support for other container orchestration platforms beyond Kubernetes?
Congrats on the launch!
Thanks @kyrylosilin! Love the questions:
- We actually have a PR in place for the implementation of RBAC via Cerbos here https://github.com/cyclops-ui/cy...
- Only limitation we have is that your Helm chart has a `values.schema.json`. That might sound like a hassle, but there are tools that can generate it for you. Cerbos added a schema recently, and you can check the tools they used here https://github.com/cerbos/cerbos...
- We are not currently planning on supporting other orchestrators. Do you have an orchestrator you would like to see supported?
Let us know if you have any other questions!
Congratulations on the launch and thank you for coming up with a great product idea. I am sure cyclops will make life easy for the DevOps engineer like me. Will try it out and get back with my feedback.
Wow, Juraj! Cyclops sounds like a game changer for anyone dealing with Kubernetes. 🙌 I love that you've made it more accessible with customizable UIs and predefined templates—seriously, that’s going to save so much time! The new features look awesome too, especially the support for private GitHub repos. Can't wait to check it out and see how it transforms my workflow! Keep up the great work!
Oh man Cyclops looks like such a lifesaver!! This is so cool. @juraj_karadza thank you so much for building this product. I am definitely gonna recommend it to my team! 🎉🎉
Congrats on the launch! I definitely wish I understood Kubernetes more than I do, but I only have so much time. How much Kubernetes does one need to know in order to use Cyclops?
@jack_michalak the idea is that you do not have to know Kubernetes to be able to use it!
The usual workflow would look something like this:
1) A devops (or someone who does know K8s) creates a template for others to use through Cyclops
2) Then the developers, QAs, Product Managers, or anybody else can use that template to deploy and manage their apps in Kubernetes without having to learn Kubernetes itself
Don't worry if you don't have a DevOps team behind you, Cyclops comes with a bunch of predefined templates to get you started!
Replies
Cyclops
Cyclops
Cyclops
Telebugs
Cyclops
Cyclops
ToyPal
Cyclops
Fleak
Cyclops
suco
Cyclops
suco
Cyclops
Glasskube
Cyclops
Cyclops
Cyclops
Cyclops
Cyclops
Resubscribe
Cyclops
Cyclops
Cyclops
Cyclops
Cyclops
Cyclops
Cyclops
Cyclops