Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kubewarden 2025 goals #31

Open
flavio opened this issue Jan 7, 2025 · 3 comments
Open

Kubewarden 2025 goals #31

flavio opened this issue Jan 7, 2025 · 3 comments
Milestone

Comments

@flavio
Copy link
Member

flavio commented Jan 7, 2025

Write your proposals for Kubewarden. What should the project attempt to reach during 2025?

Leave your ideas as comments to this issue, we will then collect and discuss them together.

@flavio flavio transferred this issue from kubewarden/kubewarden-controller Jan 7, 2025
@kkaempf kkaempf added this to the 1.21 milestone Jan 7, 2025
@flavio flavio removed the status in Kubewarden Jan 8, 2025
@flavio flavio moved this to Todo in Kubewarden Jan 8, 2025
@jvanz jvanz moved this from Todo to In Progress in Kubewarden Jan 8, 2025
@jvanz
Copy link
Member

jvanz commented Jan 8, 2025

@flavio
Copy link
Member Author

flavio commented Jan 10, 2025

Improve reliability and usability

  • Detect wrong policies as soon as possible. With "wrong" I mean: policies that reference wasm modules that cannot be fetched, have non-valid settings
  • Provide more insights to the user about the policy status: is it enforced properly, if not what happened? The user should be able to debug common issues without having to request the assistance of the cluster administrator
  • Reduce start-up time: this is particularly sensible when "fat" policies (like the ones using the official Go compiler - like CEL, Kyverno) are used
  • Better integration with CI: kwctl can already be used inside of CI systems, but it does that at a "lower" level. It would be more useful to be able to kwctl run not only the bare .wasm modules, but also .yml files containing Kubewarden's Custom Resources declarations.

Community

  • Work to graduate to CNCF incubation level
  • Keep working to increase community size, spread awareness of the project

@jhkrug
Copy link
Contributor

jhkrug commented Jan 14, 2025

  • CNCF documentation improvement suggestions to support CNCF incubation efforts.
  • Asciidoc community docs, replacing Docusaurus.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

No branches or pull requests

8 participants