Skip to content

Commit

Permalink
Clarifying a sentence re: backwards compatability
Browse files Browse the repository at this point in the history
I'm pretty sure this is supposed to say `v1` instead of `v2`.
  • Loading branch information
jessemillar authored Mar 5, 2020
1 parent bf3667c commit ec671a5
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/book/src/multiversion-tutorial/api-changes.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ In Kubernetes, **all versions must be safely round-tripable through each
other**. This means that if we convert from version 1 to version 2, and
then back to version 1, we must not lose information. Thus, any change we
make to our API must be compatible with whatever we supported in v1, and
also need to make sure anything we add in v2 is supported in v2. In some
also need to make sure anything we add in v2 is supported in v1. In some
cases, this means we need to add new fields to v1, but in our case, we
won't have to, since we're not adding new functionality.
Expand Down

0 comments on commit ec671a5

Please sign in to comment.