Austin Macdonald

@fbladilo Have you tried using finalizers? If so, can you elaborate on why they are insufficient?

It is appropriate to use finalizers for k8s resources as well, this is what we recommend for cleaning up cluster scoped resources that belong to a CR (for example). Closing...

I've added this as a release blocker. This has been deprecated for some time, and I am guessing that this will prevent some more problems for @camilamacedo86 with operatorframework/api version...

After speaking with @camilamacedo86 this is not ready to be done yet. I am moving to the backlog under priority/important-soon so this will be discussed at the next backlog grooming...

This seems like it could be reasonable, but IMO it will need some design discussion prior to implementation. If anyone needs this, please feel free to propose a design.

We need to add https://github.com/operator-framework/operator-sdk/issues/6031

I'll bring this up at the chairs meeting, it would be nice to share this style guide with OLM, so it might make sense in the community repo.

I completely agree that we should use the k8s style guide, but I also advocate that we should have our own to supplement. Our supplement should not ~reinvent the wheel...

Getting started tips from slack. Ty to @ryantking ``` package metrics type Server struct { Addr string Port uint } func NewServer(addr string, port uint) Server { /* ... */...

Removed the milestone for re-triage. @jmrodri thoughts?