Danny

@ademariag your right. > We're using self-signed certificates with our vault. Since we only use the container, we have to find ways to either provide our own CA into every...

With #844 I was able to manage at least to change the behavior. I now get the following, which can be deployed via kubectl. ```yaml [...] status: acceptedNames: kind: ''...

**Whats the issue?** The ref controller runs after the `helm template` command. Threrfore (depending on the chart) the `ref` might already be base64 encoded. This is the reason why kapitan...

Any update here?

Because the db error relats to the fields in the database. These files are related to the files the "backup app" creates. And when deleting it, it does not cleanup...

Using 0.31.0rc0 I now get My adoption can be found here: https://github.com/Moep90/kapitan-reference/commit/0fb8bab95a61777dae265786c1d8fc00d5d7b47f ```python $ kapitan compile Rendered inventory (0.25s) Unknown (Non-Kapitan) Error occurred multiprocessing.pool.RemoteTraceback: """ Traceback (most recent call last):...

From my perspective it can be resolved. Inventory is still more strict. But in a fair amount I guess. Actions for `kapitan-reference` can be found here: https://github.com/kapicorp/kapitan-reference/pull/127 --> Still not...

Do we have to update the suggested changes here as well [kap_0_kadet.md](https://github.com/kapicorp/kapitan/blob/master/docs/kap_proposals/kap_0_kadet.md)?

@chlins it works if I provide credentials. If I dont provide credentials to the registry, it still has this: ```json [...] "dest_registry": { "creation_time": "0001-01-01T00:00:00.000Z", "credential": { "access_secret": "*****",

Also for * `harborAdminPassword` * `database.internal.password` * etc etc.... you get the idea