crabique

I can see it working as a mix of both, similar to the way http01 ingress class is being handled: you can provide the default in the Issuer but you...

> It would not though help with a use case where the user wants to have a common way to configure a subset of an issuer's `Certificate`s that aren't created...

There seems to be a bigger issue where you can't properly inject `iterm2_prompt_mark` into the end-result PS1, Starship does something to it when inserting the `$character` so it never works...

> You can use a custom module to reposition the iTerm prompt marker, but you'll likely also need a custom top-level `format` containing `${custom.iterm_prompt_marker}` Unfortunately, this workaround (just like the...

This does sound like something that can be handled at CSI level, provisioning and deprovisioning volumes are the main things expected of an interface. Things in ceph ecosystem usually handle...

How would the entity responsible for snapshot creation know to delete the snapshots _before_ ceph-csi attempts to delete the volume? As far as I'm aware, there is currently no way...

+1 this would be useful, as more and more things are now available to configure using implicit sprig usage, e.g. kubevirt templates in helm often need some basic IP math

This would be an even more useful feature if it were decoupled from the secret/CM realm. At the moment, there is no operator that could reflect some labels/annotations from one...

Could this be fixed with an optional workaround to send the M signal to the application refusing to give up focus? That's what I do manually and it seems to...

CLA signed, thanks for the heads-up!