Options and Advanced aren't covered in the onboarding wizard.

Add license to the project

Mutation tests which throw errors probably don't need the Details icon available since the policy couldn't be evaluated properly. The error should be shown beneath the initial window.

For this to be released in Helm form or other Kubernetes deployment type, it needs to follow certain established practices:

• Image built with best security (non-root, etc)
• Manifest conforms to PSS Restricted profile
• runAsNonRoot if possible
• etc

Add docs for cluster connected mode

Simple button to copy any panel's contents to clipboard would be nice.

Improve our usage of docker for building frontend

Add generate rules support

May be neat to show the version of the Playground in a drop-down menu so users can see that it is being updated.

Add support for in-cluster connection

Create an helm chart

It would be awesome to have a guided tutorial, perhaps in place of the "Examples" button (since this does the same thing as opens the "hamburger" menu on the left).

This guided tutorial or wizard would walk the user through the UI and explain what each section does. Even guides them on exploring their first sample, modifying a resource, modifying the policy, and testing. This would be awesome if done in a really nice way!

Clicking on the main icon or the version in the top left causes it to flash. Seems odd for right now.

Decide if we want to use release branches

Sign docker images

Parse the policy, then parse the variables{} area of the Context window. Warn/fail if a user tries to test when one or more variables are missing (which must be manually defined).

Add instructions to contribute to the project

Add vuln checks

Add some sort of social media sharing function. Like a Twitter icon that, when clicked, allows a pre-defined tweet with something like, "Look what I made in the Kyverno Playground! <insert shortened URL of the "Share" result>" Something like this. Same thing perhaps with LinkedIn? Could maybe do more like create a GitHub gist or something. Lots of possibilities

There needs to be more Template resources available. Pod, Deployment, StatefulSet, DaemonSet, Job, CronJob, Secret, ConfigMap, Ingress, Service, Namespace, PersistentVolume, ReplicaSet, ResourceQuota, ServiceAccount, NetworkPolicy, ClusterRoleBinding, ClusterRole, RoleBinding, Role, PriorityClass.

Suggest renaming "Resource" to "Resources" (plural). It supports multiple YAML documents, not just one.

Title in the center seems like it should be "Kyverno Playground" and not just "Playground". Could use a nicer font/style.

Add instructions to build the project in the README

• API/service call
• ConfigMap context
• UPDATE operation
• DELETE operation
• imageReferences context
• Subject
• ClusterRole
• Namespace labels
• verifyImages signature
• verifyImages attestation
• Custom Resource (like cert-manager or Policy Exception)

I don't understand the Download Policy button that's accessible after the results are shown. It suggests that the policy is somehow materially different from its contents on the main page but it of course isn't. What may make more sense in place of just downloading the policy here is to download the test results along with the policy, resource, and context (including vars).

Low priority, but mobile support would be a nice to have feature.

Suggest renaming "ClusterPolicy" to just "Policies". It is supposed to support both Policy and ClusterPolicy custom resources.

Add helm docs

Current share function implementation:

• Combine Resources, Policies and Context as JSON String
• Compress and encode to base64 string to reduce length using lzstring
• Adding the content as query param and load it on page loading/mounting

Advantages

• No expiration
• Stateless

Disadvantages

• Very long URL
• Could not be send as via tools like Slack

Find a way to somehow shorten the URL and improve the UX

Add kubernetes version in the context

Add instructions to install the project

Add support for custom resources:

• allow providing a folder to the backend with CRDs
• allow providing CRDs from the frontend

Add optional gin logger

• Users are often finding it difficult to write valid Kyverno policies, even sometimes as simple as the schema is wrong before getting to more complex issues like deep JMESPath or syntax validations.
• This has to be prevented and clearly shown to users with like a large red outline around the policy pane. Users shouldn't be able to test policies that aren't schematically valid. See here.

Register helm chart in artifacthub

I suggest being able to collapse the Context panel. Some policies a user may want more screen space to scroll the Resource panel in cases where contexts aren't needed.

Produce SLSA attestations

It would be a great UX for every panel to have a small tooltip item to explain what goes on in there.

In the Context section, since this is YAML strings do not need to be quoted. The CREATE operation, remove single quotes to make simpler.

When sorting ascending Status column for a test with many results, have some result bugs. See test for Disallow Capabilities Strict in PSS Restricted profile.

What latest means ?
How do tag dev images ?

Proposal:

• dev images are tagged with commit hash
• latest is only for stable images

Some navigations cause Resources to not load and scrolling to be stuck. From a fresh window, go to Tutorials => Unique ingress host. Scroll in the Resource to the bottom. Now navigate to Restrict pod count per node. The Resource does not update and scrolling is stuck. Any subsequent navigation from here does not work. Must refresh the page to unfreeze.

imageReferences context vars should work or an error/warning to be thrown. For images which are from private registries or otherwise cannot be resolved from the Playground, vars can be used with an order of precedence: live call => vars. If live call fails and vars not defined, throw an error. Do not score this as a pass, skip, or fail.

Add import/export support (using yaml or json ?)

Names of the policies should be read from the annotation policies.kyverno.io/title

There's no need for additional space between these two rows of buttons:

Add support for policy exceptions

Scrolling should always be reset to the top of each of the windows when navigating to a new sample.

Looks like we need to add a read-only root volume for TUF:

PersistentVolume
PersistentVolumeClaim