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
Some K8s components are supported to have a custom UI component, and those can be found here. The scope of this issue is to support ClusterRoles. The new ClusterRole component should be similar to other components we already have, so feel free to check the existing ones out.
The visual representation should look something like this:
You can fetch the data about a cluster role by calling the backend on
Hi @petar-cvit, I’m encountering an issue where the API is returning null for my request. I’ve used the correct information from the resources listed at http://localhost:3000/api/modules/k6-operator/resources and formed the request URL as follows:
Hey @sarthakladhwe, my bad. I mixed up which resources were supported on the backend. ClusterRoles are yet to be supported so this issue will have to wait until then
No worries! Just let me know when it's supported, I'd be eager to tackle it. There’s a workaround by parsing manifest YAML into a JS object, but I believe our resources APIs are better suited for that.
Some K8s components are supported to have a custom UI component, and those can be found here. The scope of this issue is to support
ClusterRoles
. The new ClusterRole component should be similar to other components we already have, so feel free to check the existing ones out.The visual representation should look something like this:
You can fetch the data about a cluster role by calling the backend on
/api/resources?group=rbac.authorization.k8s.io&version=v1&kind=ClusterRole&name=&namespace=
You can test this using the k6-operator default template.
Refer to this PR on adding new UI components #330
Issue similar to #499
The text was updated successfully, but these errors were encountered: