We need to introduce filtering for Managed Resources, based on name, kind, API group and provider config. The scope for this issue is only frontend part of that, the backend will be implemented separately.

The effect of filter should reflect in corresponding API call query parameters, names up to dev.

Keep in mind that other Komoplane sections might also need filtering functionality, makes sense to have some reusable component for it.

Create an XRD with no claims and the following error happens on xrd view.

Uncaught TypeError: Cannot read properties of undefined (reading 'kind')
    at Fbe (index-59f92d5a.js:382:16742)
    at bO (index-59f92d5a.js:38:19518)
    at M$ (index-59f92d5a.js:40:44027)
    at w$ (index-59f92d5a.js:40:39763)
    at Q4 (index-59f92d5a.js:40:39691)
    at m_ (index-59f92d5a.js:40:39545)
    at WR (index-59f92d5a.js:40:35913)
    at O$ (index-59f92d5a.js:40:34864)
    at R (index-59f92d5a.js:25:1535)
    at MessagePort.k (index-59f92d5a.js:25:1894)

When graphs are displayed, the composition nodes are misplaced

It has to do with the way we create and configure the graph. It does not happen always, and the cause for it is unknown. Should be simple issue with React hooks and callbacks.

The requirement is for arrows to go left-to-right always, upon initial load and upon navigation between different views.

Composition has a reference to composite resource definition, via compositeTypeRef field. The improvement is to enable "Relations" tab for composition view drawer and XRD drawer and display relation there.

The task needs both backend and frontend work. Can be done via separate PRs by different people.

Backend needs to use same trick with full=1 query parameter, to list:

• for composition, the XRD it refers to
• for XRD, all compositions that refers to it

It will be nice to add any possible composite function status output

The current image komodorio/komoplane is not available in docker.io?

When I deploy the helm chart on EKS 1.24 the liveness/readiness probes fail and the pod is restarted every 30 seconds.

I changed the port: http to port: 8090 for both probes and that seems to have solved the problem. I'm not sure if that's the correct fix?

In each page header of application, there should be short description of what it means. The description should be taken from Crossplane docs. Also, there should be a link to corresponding place in Crossplane documentation.

The goal is to offer less experienced users the direction to learn Crossplane

It is great that now the resource Kind is visible in each component in the graph!

It would also be valuable to see the APIGroup on the component, meaning here:

Maybe it is better for the APIGroup and Kind to be displayed in the box, under the name, something like:
name: <RESOURCE_NAME>
kind: <RESOURCE_KIND>
apiVersion / apiGroup: <RESOURCE_API_VERSION> / <RESOURCE_API_GROUP>

The list views (claims, compositions, managed resources, etc) are not very space-efficient, so once you have more than just a couple of items, you need to scroll, and it's hard to get an overview. Consider instead using a more dense table format, maybe even one that supports sorting/filtering

Currently, when we display a a Composite Resource in Komoplane, status indicators are present to show the different statuses of the managed resources

E.g. : in the following screenshot, we can see that some resources are "Synched" (green) and some are "Not Ready" (red)

It would be make these "status indicators" clickable to be able to filter on status in order to show only "Not Ready" resources for example

Not sure if this is intentional or not but Slack doesn't want to let me join

Due to this assumption https://github.com/komodorio/komoplane/blob/main/pkg/backend/crossplane/crds.go#L38 that the plural form of the CRD has a "s" appended - some of ours don't. Is there a better way to get the plural form of the crd?

Right now when there are many events, their containers are not aligned as columns.

If you have compositions without setting external-name, it's very hard to see what's what without clicking through (which is pretty slow). It could also be showing the crossplane.io/composition-resource-name annotation value.

If more than one version of an composite resource definition exists, the function Controller.GetComposite risk of failing if the first version fetched is an non-active one.

To be more specific, the code fails here:

                gvk := schema.GroupVersionKind{ // TODO: xrd.Status.Controllers.CompositeResourceClaimTypeRef is more logical here
                        Group:   xrd.Spec.Group,
                        Version: xrd.Spec.Versions[0].Name,
                        Kind:    *kind,
                }

I have a suggestion to remedy this problem and will follow this issue up with a pull request

https://helm-charts.komodor.io/index.yaml

Starting with 1.3, the urls in the chart index.yaml are pointing to github:
urls:
- https://github.com/komodorio/helm-charts/releases/download/komoplane-0.1.3/komoplane-0.1.3.tgz

Till 1.3, the urls were relative:
urls:
- komoplane/komoplane-0.1.2.tgz

This is problematic when using Artifactory, the chart location is not resolved correctly.
This worked fine till 1.3.

Right now, there's no indication which area we're at. It should be highlighted somehow, e.g. with BG color or so.

Failed to login using oidc auth

INFO[0000] komoplane, version 0.1.5 (9d75e0d9c32729746fcbec3837c7cbb855a3ad0b @ 2024-01-14T18:46:04Z)
FATA[0000] Failed to start: no Auth Provider found for name "oidc"

solution is simply adding

import (
.....
_ "k8s.io/client-go/plugin/pkg/client/auth/oidc"
)

in controller pkg

The Helm Chart allows setting annotations and labels for some resources but not all. Specifically, I'd like the ability to set annotations and labels for the Service.

#51 submitted for review to:

• add default labels to ClusterRole and ClusterRoleBinding
• add ability to specify annotations for service
• add ability to specify labels for Ingress, Service & ServiceAccount
• add missing serviceAccount.annotations to values.yaml

Can I configure the base URL of the komoplane UI? I am currently using a reverse proxy that's already implemented in my employer's org and want to route traffic to a specific location (ex. myorg.dev.example.com/komoplane).

In case unhandled error happens, we should display nice message, containing:

• technical error details: error message, stacktrace
• application version
• call for user to report the error to the komoplane GH issues
• suggestion to refresh the page

Something similar to this:

Feels like "React error boundary" should be involved

Make a tutorial article or YouTube video guiding how to install komoplane and configure auth proxy for it.

No coding, pure documentation task.

When the komoplane.debug attribute is set to true in values.yaml the following error occurs on deployment:

Error: INSTALLATION FAILED: Deployment in version "v1" cannot be handled as a Deployment: json: cannot unmarshal number into Go struct field EnvVar.spec.template.spec.containers.env.value of type string

The problem is that the value 1 is being used in the template for the ENV var which gets translated as an integer, instead of '1' which would be translated as a string.

Hello can you build arm64 image please. If possible mirroring to Quay and Public ECR would be great also.

Thanks

Hi Team,
Is Komoplane is supporting AD and LDAP Authentication?
@MickaelAlliel Mickael Alliel
@olegsa Oleg Sabov