Closed flavio closed 2 months ago
Hi @flavio and/or @jvanz . Regarding this. The instructions in the blog post seem ok. They can be expanded with an example. My question though is where to put this information in the docs?
As a developer using Kubewarden, where would you expect to see this workaround documented?
In the Howtos? The Secure Supply Chain Section? Somewhere in the 'Configuring policy servers' Howto.
WDYT?
What about adding a new sidebar item: "Howtos/Limitations"?
As we have some sort of cert-manager integration - I guess we should add the info on how to use cert-manager for this purpose as well?
We cannot use cert-manager for that, not without some work on our codebase. We plan to tackle the whole certificate topic really soon (by next KW release)
I like @flavio 's idea of a new section to keep stuff like this separate. I think I want to call it 'Howtos/Workarounds' though. It's a minor point. It;s how to work round a current limitation. If we called it limitations I think it would fit better under Explanations, but as in it we are going to explain how to work around something ...... Hmmm? Anyway, for the moment I'm going with workarounds.
@jhkrug is this complete with https://github.com/kubewarden/docs/pull/423?
I would say so. Closing as fixed
Currently our root CA and the internal certs generated by it have a lifetime of 10 years. We are not doing rotation of these resources yet.
We should update our docs to: