Bjørn Hald Sørensen
Bjørn Hald Sørensen
Yes, that would make good sense. It would be nice with a timeout on the last catch up part, as to be able to indicate how long one is willing...
We generally see this as a good fit for the controller. We already duplicate a lot of secrets between namespaces and made some tooling to simplify the task on one...
I very much agree. Kubernetes is all about declaring what you want and let controllers handle the details. In this case declaring `SealedSecret`s and getting `Secret`s.
@katz95 we just had a discussion internally on that idea actually. By default many developers at Lunar expect to see everything by default and the be able to trim it...
Sure thing 👍 I'll give it a go @benjdlambert
I wonder if the `EntityKindPicker` is actually just what needs an implementation ? It was added without an implementation in #5643. WDYT @timbonicus ? Anything I'm missing?
That is actually pretty nice @awanlin . Thanks for sharing. I have something working now with a multiple choice Kind picker but it has some unforseen consequences. Currently it modifies...
@katz95 do you have an opinion here for the Sidebar variant? It defeats the possibility of showing multiple kinds at once, but might just prove to be the better solution...
You can see a draft of the kind picker here: https://github.com/backstage/backstage/pull/12974
I made a rough draft in https://github.com/backstage/backstage/pull/12974 of this but turned out there were some things breaking with the kind filter. Maybe you can help answer some of the concerns...