Chanwit Kaewkasi

Thank you @Nalum This design is excellent. It gives us auditable activities for force unlocking. ``` spec: terraformState: forceUnlock: (yes|no|auto) lockIdentifier: [holder-id] ``` There are a few things to improve...

We'll decide about this one later, as it might compromise our security.

Yes, we also observed that behavior but hadn't had a chance to capture it as a bug. Thank you for reporting this @artem-nefedov!

I re-arranged the logic to make the status happen sooner, but if it didn't fix your issue, maybe I had to take a look at other parts of the ready...

Thanks @artem-nefedov I should have done that. The problem seems to be hiding inside other stages of the workflow too.

I would tackle this problem using a simple image-based approach. We had a plan to have `tfctl image build` command, for example, for users to opt-in: - Their custom version...

> I'm going to guess it has to do with the caching, Correct. It uses the namespace-based informers to watch and cache frequently-used objects.

> I would suggest a spike to see how much would need to change if we were to change to client-go. I would also suggest trying "dynamic-client." Its APIs return...

Yes, that one.

**Outcomes:** HNS controller offers excellent flexibility in creating namespaces in a restricted cluster. For example, Team Denim members can only work in the `team-denim` namespace. With the HNS controller installed,...