docs(best practices): add best practices doc #171
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pull Request Test Coverage Report for Build 8100015433Details
💛 - Coveralls |
| ## versioning | ||
|
|
||
| - We should never drift further than one minor version behind sigs.k8s.io/karpenter | ||
| - We can have commit version references in-between our releases, but for any `karpenter-provider-azure` release we will tie ourselves down to a whole version of `sigs.k8s.io/karpenter`. |
There was a problem hiding this comment.
This requires more thought, and development of our release cadence and slo before we can make a decision
|
Would love for us to get back to this, maybe this can be brought up in working group as well for the azure docs working group. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #
Description
We've had discussions on multiple points which I think need defined guidance, and best practices.
This is adding a living doc that will be built out with best practices we develop with, and build off of.
How was this change tested?
NA
*
Does this change impact docs?
Release Note