Bryce Palmer
Bryce Palmer
> Hi @everettraven, I did `go mod tidy` but it seems that DCO is still failing. Any idea why? @assafad Looks to me like it passed. Must've just needed the...
Hi @ivandov, My understanding of the core problem here is the inability to "scope" down operator permissions to only have the permissions they need to operate. In your particular case...
I agree with @ivandov that the current limitation in controller-runtime shouldn't warrant closing this issue, but I think this issue would rather be better suited to be added to the...
@ivandov You are correct that there are currently some limitations in `controller-runtime` that makes it difficult for an operator to be able to handle this scenario. > Or - are...
/assign
So I did some digging and here are my findings: When using: ``` operator-sdk run bundle quay.io/community-operators-pipeline/flux:v0.25.2 ``` It was able to successfully install the operator on the cluster. When...
So the [above comment ](https://github.com/operator-framework/operator-sdk/issues/5773#issuecomment-1246951229) is definitely an issue at the moment because when a fix is applied I am able to use `operator-sdk run bundle` and `operator-sdk run bundle-upgrade`...
> What is the plan for dealing with this action? Are we going to fail PRs because of them? Are we going to maintain these? > > I like the...
Here is the current report that I was able to get from the CodeQL scan on my fork: https://github.com/everettraven/operator-sdk/security/code-scanning Looks pretty clean from what I can tell
/assign @everettraven