You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the current implementation of KSOPS, it does not support the use of remote targets directly. The plugin operates on local files, as evidenced by the decryptFile function in the ksops.go file, which reads files from the local file system using ioutil.ReadFile(file). This function is used to decrypt both the main manifest files and any additional files specified in the secretFrom field.
However, you can still use remote targets by manually cloning the repository and keeping it up-to-date. Here's an example of how you might modify your YAML to use a remote target:
In this example, ./path/to/cloned/repo/secret.enc.yaml would be the path to the encrypted file in the cloned repository. You would need to replace this with the actual path to your encrypted file. You can refer to the test/krm/binaryfile/generate-resources.yaml file for more examples.
If you need to automate the process of cloning and keeping the repository up-to-date, you might consider using a GitOps tool like ArgoCD or Flux.
I want to be able to use remote targets with ksops.
Something like this should work, but it seems that it does not:
I would expect ksops to just use the kustomize feature: https://github.com/kubernetes-sigs/kustomize/blob/master/examples/remoteBuild.md
The text was updated successfully, but these errors were encountered: