Matthias Bertschy
Matthias Bertschy
Yes go ahead, do you know how it works?
/assign @claudiubelu
> there are some linter errors https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/125489/pull-kubernetes-linter-hints/1802667440652423168 and one comment left > > ``` > > 16m54s > -- > { ScriptError test/images/agnhost/liveness/server.go:65:12: Error return value of `c.Close` is not...
@hshiina this is awesome, let's wait for #125489 to run the test Do you plan to fix the livenessProbe behavior in this PR too?
> It's being prepared for release. I reviewed the workflow file. What's the issue? The issue is that a GITHUB_TOKEN pushing a tag doesn't trigger another action (apparently by design)....
> Should I then create a PR to merge the Krew workflow with the release? https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows Yeah, it's probably enough to modify [04-publish-krew-plugin.yaml](https://github.com/kubescape/kubescape/blob/master/.github/workflows/04-publish-krew-plugin.yaml) triggers to react on release like https://github.com/kubescape/kubescape/blob/master/.github/workflows/03-post-release.yaml#L4-L8...
issue still there, we'll take another approach
hi @fayak how big is your cluster? (number of pods, nodes, other CRDs?)
this is very strange... could you try to run kubescape with `-l debug` to maybe understand why it's doing that? also what's the CPU/memory config of the machine running the...