Cyclops is an open-source tool that allows companies to build Developer Platforms for Kubernetes in days instead of months. It enables DevOps engineers to create custom UIs for Kubernetes, making it accessible for the rest of the developers.
Hey Product Hunt 👋, A whole year has passed since our first launch on this platform, and we are very excited to share what we have been up to since then!
What is Cyclops? Kubernetes is widely used to run applications, but it has a steep learning curve, and developers need to maintain configuration files they often don’t understand. That is why we are building Cyclops, an open-source tool that allows companies to create Developer Platforms for Kubernetes in days instead of months.
How does it work? 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. 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? ⚙️ GitOps Integration ⚡ Helm Release Manager 🧩 Backstage Plugins 🌒 Dark Theme 🌊 Streaming: Logs & Status
I love how Cyclops connects DevOps teams and developers. Does it support RBAC (Role-Based Access Control) to ensure that non technical users have safe access?
@nicholas_anderson0 great question! All Cyclops applications are defined as custom Kubernetes resources (CRDs). Each time you update your application configuration, that change is persisted as a history entry in the CRD and stored in Kubernetes. Cyclops will keep all your changes through time and you can rollback to a previous version in a click :)
@elizabeth_turner4 we designed Cyclops as lightweight as possible. Cyclops doesn't have a database that you need to manage separately and only talks to you Kubernetes API. As you will need more and more UIs, those would just be stored as references to templates on a Git repo, Helm repo or other and will be rendered as the UI when you need to configure your apps. No templates are stored, so no worries about blowing out disks or memory
Creating custom UIs for Kubernetes can be tricky but Cyclops is like a great shortcut. Are there integrations with popular CI/CD tools like ArgoCD or Jenkins?
It's a big win for DevOps teams to have faster Kubernetes platform development. By the way does Cyclops come with pre built UI components or is everything customizable?
Thanks!@kamil_riddle The workflow is like this: 1) DevOps engineers create configuration templates using Helm charts 2) DevOPs engineers import these Helm charts into Cyclops -> which creates UIs from them 3) Developers use these UIs to configure and deploy 4) Developers can manage their apps running on Kubernetes on their own
This way DevOps engineers don't have to play help-desk for developers, and developer don't have to get into the intricacies of configuration manifests and Kubernetes!
Thanks@lucas_parsons! Making Kubernetes much more approachable for developers while freeing up time for the DevOps to work on other things than just supporting devs.
@tyler_wright1 Cyclops runs entirely within your cluster and communicates directly with the Kubernetes API. No configuration data ever leaves your infrastructure
Thanks @scytalelabs_marketing! Under the hood, Cyclops uses your Helm charts to create user interfaces. But we also have our own CRDs called Modules, which live in the cluster like any other Kubernetes resource. We wrote a blog post explaining how this works, check it out 🍏-> https://cyclops-ui.com/blog/2024/05/24/is-k8s-database
p/general
p/ama
p/introduce-yourself
p/self-promotion
p/producthunt
p/kraftful
p/wisprflow
p/screaming-frog-seo-spider
p/xnapper
p/google-chrome
p/fine
p/openai-api
p/bolt-new
p/elevenlabs
p/notion
p/attio
Replies
Cyclops
Hey Product Hunt 👋,
A whole year has passed since our first launch on this platform, and we are very excited to share what we have been up to since then!
What is Cyclops?
Kubernetes is widely used to run applications, but it has a steep learning curve, and developers need to maintain configuration files they often don’t understand. That is why we are building Cyclops, an open-source tool that allows companies to create Developer Platforms for Kubernetes in days instead of months.
How does it work?
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. 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?
⚙️ GitOps Integration
⚡ Helm Release Manager
🧩 Backstage Plugins
🌒 Dark Theme
🌊 Streaming: Logs & Status
@juraj_karadza Cyclops does an amazing job of simplifying the complexities of Kubernetes while boosting developer efficiency.
Cyclops
@jesus_porter 😊
I love how Cyclops connects DevOps teams and developers. Does it support RBAC (Role-Based Access Control) to ensure that non technical users have safe access?
Cyclops
@william_rivera3 good point! It doesn't at the moment, but it's on our radar :)
This tool is time saver for DevOps teams. Cyclops could really change the game for scaling Kubernetes adoption in larger organizations.
Cyclops
@victoria_collins1 yes! Spot on 🙌
The idea is brilliant but how does Cyclops manage versioning as Kubernetes configurations change over time?
Cyclops
@nicholas_anderson0 great question! All Cyclops applications are defined as custom Kubernetes resources (CRDs). Each time you update your application configuration, that change is persisted as a history entry in the CRD and stored in Kubernetes. Cyclops will keep all your changes through time and you can rollback to a previous version in a click :)
Considering the complexity of Kubernetes how does Cyclops maintain optimal performance when managing large clusters with multiple UIs in play?
Cyclops
@elizabeth_turner4 we designed Cyclops as lightweight as possible. Cyclops doesn't have a database that you need to manage separately and only talks to you Kubernetes API.
As you will need more and more UIs, those would just be stored as references to templates on a Git repo, Helm repo or other and will be rendered as the UI when you need to configure your apps. No templates are stored, so no worries about blowing out disks or memory
Creating custom UIs for Kubernetes can be tricky but Cyclops is like a great shortcut. Are there integrations with popular CI/CD tools like ArgoCD or Jenkins?
Cyclops
@sophia_watson3 yes! We actually wrote a blog recently describing how to integrate with similar tools.
Check it out -> https://dev.to/cyclops-ui/how-we-took-gitops-a-step-further-3dbc
It's a big win for DevOps teams to have faster Kubernetes platform development. By the way does Cyclops come with pre built UI components or is everything customizable?
Cyclops
@jesus_porter Cyclops comes with a couple of predefined templates that you can use out of the box!
Here you can learn more about how the UI customizability works -> https://cyclops-ui.com/docs/templates/
What an impressive tool how does Cyclops enhance collaboration between DevOps and developers?
Cyclops
Thanks!@kamil_riddle
The workflow is like this:
1) DevOps engineers create configuration templates using Helm charts
2) DevOPs engineers import these Helm charts into Cyclops -> which creates UIs from them
3) Developers use these UIs to configure and deploy
4) Developers can manage their apps running on Kubernetes on their own
This way DevOps engineers don't have to play help-desk for developers, and developer don't have to get into the intricacies of configuration manifests and Kubernetes!
That's really impressive. What do you think has been Cyclops' biggest impact on development teams up to now?
Cyclops
Thanks@lucas_parsons! Making Kubernetes much more approachable for developers while freeing up time for the DevOps to work on other things than just supporting devs.
Cyclops is amazing for simplifying Kubernetes but how does it address security risks when exposing Kubernetes configurations through custom UIs?
Cyclops
@tyler_wright1 Cyclops runs entirely within your cluster and communicates directly with the Kubernetes API. No configuration data ever leaves your infrastructure
Amazing innovation. How does Cyclops manage those tricky Kubernetes configurations?
Cyclops
Thanks @scytalelabs_marketing! Under the hood, Cyclops uses your Helm charts to create user interfaces.
But we also have our own CRDs called Modules, which live in the cluster like any other Kubernetes resource. We wrote a blog post explaining how this works, check it out 🍏-> https://cyclops-ui.com/blog/2024/05/24/is-k8s-database
Excited to see where you take this!
Cyclops
@jura_milic 😁
Very exsiting project in the k8s ecosystem
Cyclops
Thanks @luka_mercep1 🫶
I am following you for a while, can not wait for you to go global🚀 Gooooo Cyclops
Cyclops
Thanks@matija_makoter!
Mr. Worldwide 😎
Looks super useful! Excited to see how this improves workflow efficiency. 🚀
Cyclops
thanks @edrudo 🙌 🙌
Let's go! Good luck guys ♥️
Cyclops
@domagoj_coric 🧡
Love this tool! Glad to see it climbing up the ranks
Cyclops
@jurica_kenda thanks 🧡
Looking good! Good luck!! <3
Cyclops
@ana_vlahov Thanks 🙏