Skip to content

docs: Add example for dealing with compromised key#34

Open
fhoekstra wants to merge 6 commits into
getsops:mainfrom
fhoekstra:patch-1
Open

docs: Add example for dealing with compromised key#34
fhoekstra wants to merge 6 commits into
getsops:mainfrom
fhoekstra:patch-1

Conversation

@fhoekstra

Copy link
Copy Markdown

The order of operations in this scenario is very specific and error-prone. It would make sense to document this right here in this project.

I would appreciate any feedback and/or corrections!

The order of operations in this scenario is very specific and error-prone. It would make sense to document this right here in this project.

Signed-off-by: fhoekstra <32362869+fhoekstra@users.noreply.github.com>
@netlify

netlify Bot commented May 23, 2026

Copy link
Copy Markdown

Deploy Preview for getsops ready!

Name Link
🔨 Latest commit d2ea451
🔍 Latest deploy log https://app.netlify.com/projects/getsops/deploys/6a2275fbc4bbe5000854632c
😎 Deploy Preview https://deploy-preview-34--getsops.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Signed-off-by: fhoekstra <32362869+fhoekstra@users.noreply.github.com>

@felixfontein felixfontein left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contribution! I think it is a great idea to have a section on this in the docs. I've added two comments below, which are my personal ones; maybe someone else from @getsops/maintainers might want to comment on them?

Also note that currently there's a large reorganization happening (#31) which conflicts with tihs PR (and in fact with any other PR changing the documentation). I don't know how long it will take @getsops/maintainers to review that PR, so whether it makes sense to merge this one first and rebase the other, or the other way around.

Comment thread content/en/docs/_index.md Outdated
Comment thread content/en/docs/_index.md Outdated
Co-authored-by: Felix Fontein <felix@fontein.de>
Signed-off-by: fhoekstra <32362869+fhoekstra@users.noreply.github.com>
@fhoekstra

Copy link
Copy Markdown
Author

Also note that currently there's a large reorganization happening (#31) which conflicts with tihs PR (and in fact with any other PR changing the documentation). I don't know how long it will take @getsops/maintainers to review that PR, so whether it makes sense to merge this one first and rebase the other, or the other way around.

I am interested in this subject right now because of the move to post-quantum encryption. Currently waiting for FluxCD 2.9 to be released, and then a lot of Kubernetes users of SOPS will be looking at moving to post-quantum. I'm looking to do a simple how-to blog post on it either way, it would be nice if I could point at the official documentation for this process.

But I understand there's "always something" and I wouldn't want to slow down the docs improvement project.

Comment thread content/en/docs/_index.md Outdated
@felixfontein

Copy link
Copy Markdown
Contributor

Also would you mind changing the commit message above to remove the @? I don't want to get a notification every time the commit is pushed somewhere on GitHub :) Thanks.

fhoekstra and others added 3 commits June 5, 2026 09:08
…s and clarify checking in of the updated file.

Signed-off-by: fhoekstra <32362869+fhoekstra@users.noreply.github.com>
Signed-off-by: fhoekstra <32362869+fhoekstra@users.noreply.github.com>
Co-authored-by: Felix Fontein <felix@fontein.de>
Signed-off-by: fhoekstra <32362869+fhoekstra@users.noreply.github.com>
@fhoekstra

Copy link
Copy Markdown
Author

Ah sorry, I keep forgetting about Github's enthusiastic notification policy 😅
Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants