erabii
erabii
> Either way, I am not sure I see a reason here not to do this based on what you have said. I took a fresh pass over the code...
this will go into `3.1.x`?
after further discussion, we came to the conclusion that having `includeProfileSpecificSources` + labeled search is not correct. As such, this combination will be dropped in the next major and this...
@ryanjbaxter this can be closed now. thank you
what versions / dependencies are you using?
it's not really a show stopper for me, still working on a PR in this direction. We can easily get around it and when the time comes, just upgrade
let me get the issue straight a bit please. So, because _you_ use : ``` ... resourceNames: [ "
There are issue with this approach that needs further thinking imho. For example: - `LIST` is indeed required, atm. In the future, we will support getting individual configmaps, by name:...
This looks interesting to look at. I'll see if I find some time this week to look at your sample. Thank you for the report