Also the Kubernetes operator docs could use a litt...
# infisical-feedback
r
Also the Kubernetes operator docs could use a little love. Honestly, just a fully worked multi-manifest yaml with inline comments is all that is needed. I'm sure these exist somewhere. It’s all very simple and intuitive when you see it all put together. I'd just put a link to some sample recipes in github.
p
Hi Rob, thank you for reaching out! This is great feedback. We've recently revamped the operator documentation as apart of the V2 operator API rollout. I do agree that it would be beneficial if we had a ready-to-use recipe for the
InfisicalStaticSecret
 as an example. I'll bring this up with the team internally right away!
r
A few more pieces of feedback on this having just gone through it: • The LLM assist (i'm using codex) is very good. So you are doing something right in exposing the right docs that the LLM can understand.
• I'd probably have done better with the setup just handling it all to codex to figure out. • Most of the confusion on my part with the docs is around the alpha1->beta1 transition. The docs have it kind of co-mingled in the examples.
Codex was quite good at using the infisical API. It wrote a tool (unprompted) to upload the token reviewer JWT and CA cert into the machine identity. You might consider either rolling some of this into a tool/skill of your own.
d
Hi @Rob Schoening, thank you for the feedback!
• Most of the confusion on my part with the docs is around the alpha1->beta1 transition. The docs have it kind of co-mingled in the examples.
Are you referring to finding references to the v1alpha resources throughout the docs, rather than the more updated v1beta API?