Marko Mikulicic
Marko Mikulicic
In the following example I created a struct called `Common` with an `AfterApply` hook. When this structure is embedded using Go struct embedding, the AfterApply hook gets invoked as per...
The run method was too long and it was impossible to figure out what each parameter meant. Furthermore a few flags were still accessed via global variables making it hard...
Some users need to migrate their workload to another cluster. The set of all the manifests of their workload include all the SealedSecret manifests. Commonly people simply copy the sealed-secret's...
Currently when a secret is deleted the controller doesn't do anything until something triggers a new run, which can happen either because there is a change in the sealed secret...
Currently we assume a cluster admin will be willing to install sealed secrets controller globally. This assumption doesn't hold for all of our users. Many people end up with a...
We have some old resource versions in our manifests. It's time to fix them: * [x] CustomResourceDefinition (up from v1.19) * [ ] ClusterRoleBinding (v1.22) * [ ] Role (v1.22)
The controller can be configured to watch for resources in it's own namespace only (--all-namespaces=false) or to limit its search to resources matching a given label with `--label-selector` (#521). Currently...
Objective: Simplify the use of `kubeseal --raw`, especially when used to implement editor extensions. Proposal: Add a "context" flag to the "raw" command, so that kubeseal can figure out the...
The suggested backup workflow works a-ok in practice but suffers from a race condition. It also doesn't resonate with a lot of people (possibly because they intuit such a race...
Users should seal their secrets with the latest available certificate. But how do they know which that is? There are a few problems: 1. The certificate has to be _authenticated_,...