monokle-core
monokle-core copied to clipboard
kubeshop
Monokle validation engine, CLI and shared UI components
After introducing tenant isolation and changing some of the routes (e.g. `dashboard` -> `console`), deeplinks generated by `synchornizer` package no longer works. Related code: https://github.com/kubeshop/monokle-core/blob/183c36bec26570bc4a1d39d60b4d41f0df2dc473/packages/synchronizer/src/utils/synchronizer.ts#L169-L183
As described in https://github.com/kubeshop/monokle-saas/issues/2231: > Origin conflict between integration - when CLI logged in to enterprise, VSC ext will try to use those auth credentials (e.g. refresh token) for default...
We want to handle `matchResources` correctly for both VAP handling and in admission controller MonoklePolicyBinding. Both should follow k8s specs so it will be the same mechanics for both. You...
I would like to validate my resources using the Kubernetes 1.28 ValidatingAdmissionPolicy-related CRDs - see https://kubernetes.io/docs/reference/access-authn-authz/validating-admission-policy/ Initially I am fine with the validator automatically detecting any corresponding resources in my...
Authenticator (part of synchronizer package) stores auth data in a dedicated file. This file is updated when user state changes (login / logout / token refresh) and then in-memory user...
At this stage, when error occurs in synchronizer, it will be thrown (or rethrown) to consumer to catch it. There are places where we also throw our own (kind of)...
This relates to "strict-mode" rule introduced in recent #374 PR. The rule should also trigger for misspelled (or just gibberish) `apiVersion` values. However, for some resources it does not. This...
The SARIF output results array produced by validation package uses `SRCROOT` for each result location like: ```json { "ruleId": "KSV001", "rule": {...}, "taxa": [...], "level": "warning", "message": { "text": "Disallow...