Marko Mikulicic comments

Results 231 comments of


                                            Marko Mikulicic

Kustomize plugin

By using the `namespace-wide` scope when sealing the secret, the secret can be renamed at will as long as it stays in the same namespace

Kustomize plugin

@tehmoon hi! Thanks. Can you please describe your wider workflow so I can better understand how this step with kustomize fits in?

Find alternative solution for renameio

we can start by reaching out to the upstream project and ask if they're open to contributions to get back windows support.

Find alternative solution for renameio

Ah, basically they're saying that's it's impossible on windows. So let's just not use that library on windows

Find alternative solution for renameio

(by which I mean we should write our own wrapper that uses that library on all platforms except windows, where it just writes to the file non-atomically)

One kubeseal instance to manage secrets in a subset of namespaces

We'd have to add support for this "namespace whitelist". It shouldn't be hard. Contributions welcome!

kubeseal: client library

Makes sense!

When sealing multiple secrets in singe yaml file only first is sealed

What if we use the `{"apiVersion": "v1", "kind": "List", "items": [...]}` to render to and from json?

When sealing multiple secrets in singe yaml file only first is sealed

FTR, per-item encryption has been implemented in [v0.7.0](https://github.com/bitnami-labs/sealed-secrets/releases/tag/v0.7.0)

When sealing multiple secrets in singe yaml file only first is sealed

> Unfortunately currently encrypting side has to know into which namespace it will be deployed as namespace is part of encryption algorithm. This is by design in order to allow...