-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rudimentary best practices for applications (#157) #180
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a good start.
Added some initial thoughts but I need to read through it a few more times.
## Secret Management | ||
|
||
1. Make sure no secrets are commited to either source code repository, nor gitops repository. | ||
2. Load secrets using Secret Store CSI Driver. It is documented extensively [here](https://xenitab.github.io/docs/xks/developer-guide/secrets-management). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's okay to get secrets from Cloud provider key vault solutions as well. As long as you don't save passwords in git you are okay :)
|
||
Add tracing to your application. We have found that modern trace tools provide pretty good configuration out of the box. You just need to add an appropriate tracing library to your application. Consider reading our extended [extended documentation on tracing](https://xenitab.github.io/docs/xks/developer-guide/observability). | ||
|
||
## Pod disruption budgets |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe change this to availability or something similar. I think this PDB documentation is to in depth for a overview page.
I think you should mention pdb as a part of getting good avaliability in k8s together with things like antiaffinity and link to our other docs for more details.
|
||
Your pod can be shut down by kubernetes. Make sure the following has been configured. | ||
|
||
1. Your application has graceful shutdown that closes connection to database. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mention something about sigterm and that you application needs to capture it and then close the connections.
We probably have some docs about this in some application specific part. Can link to that.
ping @dachrillz |
No description provided.