Catalog plugin

Shows Cyclops module data as part of the Backstage catalog. This plugin allows you to add the page for Module details and edit your Modules through a new tab in your Component details page.

You can view Kubernetes resources deployed for a Module (check status, list logs) as well as perform actions like reconciling Modules or restarting workloads.

If you click the Edit button, you will be able to see the UI for editing that specific Module.

Module plugin communicates with an existing Cyclops backend instance running in your cluster. All requests going from your Backstage app to the Cyclops backend are proxied through the Backstage backend, so all of the requests are authenticated.

By default, the Module plugin will fetch the Module called the same as the component. In this case, the component is called example-website, and the Cyclops plugin will fetch a Module called example-website.

In case your Module is called differently from the Backstage component, you can set the cyclops-ui.com/module-name-override annotation that would override the Module fetched for your component. In the example below, the component is called my-component, but the Module that would be fetched is the demo-module.

apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
  name: my-component
  annotations:
    cyclops-ui.com/module-name-override: demo-module # specify which Cyclops module should be fetched
spec:
  type: website
  lifecycle: experimental
  owner: guests
  system: examples
  providesApis: [example-grpc-api]

Install

Steps for setting up the plugin on your Backstage app:

Have a running Cyclops instance:
- If you don't have a running instance, you can install one by following this two-command tutorial
- Make sure that Cyclops backend (cyclops-ctrl pod) is running and is reachable. If you installed with the commands above, your Cyclops instance would be reachable from within the same Kubernetes cluster on http://cyclops-ctrl.cyclops:8080
Add the plugin to your Backstage instance, you need to add to packages/app:
```
yarn --cwd packages/app add @cyclopsui/backstage-plugin-cyclops-modules
```

Add proxy configuration to your Backstage configuration in app-config.yaml

proxy:
  endpoints:
    '/cyclops':
      target: 'http://cyclops-ctrl.cyclops:8080'
      changeOrigin: true

Add Module plugin component to your catalog. Go to file packages/app/src/components/catalog/EntityPage.tsx and import Cyclops component:
```
import {ModuleDetailsComponent} from "@cyclopsui/backstage-plugin-cyclops-modules";
```
Now you just need to add the Cyclops component to the entity. For example, if you want to add Cyclops tab for a Website component, find websiteEntityPage and the Cyclops tab by pasting the code below:
```
<EntityLayout.Route path={"/cyclops"} title={"Cyclops"}>
	<ModuleDetailsComponent/>
</EntityLayout.Route>
```

Your Backstage catalog can now view and edit deployed Modules in your cluster.

This plugin can't deploy new Modules and can only give you an overview of existing ones.

The backstage plugin subscribes to the SSE on the Cyclops API to have live data about deployed Kubernetes resources. If you want to turn off streaming and fallback to polling, you can add the following to the app-config.yaml:

cyclops:
  streamingDisabled: true

Catalog plugin

Install​

Install