Skip to content
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

Add "Best Practice" page ? #705

Open
udf2457 opened this issue Feb 9, 2025 · 0 comments
Open

Add "Best Practice" page ? #705

udf2457 opened this issue Feb 9, 2025 · 0 comments

Comments

@udf2457
Copy link

udf2457 commented Feb 9, 2025

It seems to me that the docs are missing a "best practice" page as there are currently lots of hints in the manual (either explicit or implicit) that really should be consolidated onto a "best practice" page.

For example:

  • The implied best practice on the Updates Streams page that you should consider haivng testing and next canaries
  • The implied best practice in relation to Zincati wariness that some nodes should have a more aggressive value for canary purposes
  • Given CoreOS is a rolling distro, details on how to manage configs between releases (e.g. avoid issues with breaking changes in configs)
  • Probably many tips and tricks for managing Butane files, perhaps especially around merge and replace.

I'm sure there's a bunch of things that battle scarred sysadmins have picked up over the years ? i.e. "I wish somebody told me that when I started using CoreOS".

The CoreOS devs also probably know which cupboards the skeletons are hidden in and could hint at things to avoid because they are flaky / not stable. 😉

I'm new to CoreOS but this sort of thing would be very useful when strarting from a greenfield deployment. People should not have to learn the hard way.

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

No branches or pull requests

1 participant