Skip to content

Commit 9204ee4

Browse files
authored
Add blurb about backwards compatability to upgrading-sdk-version docs (#5185)
Signed-off-by: Jonathan Berkhahn <[email protected]>
1 parent bc8aedd commit 9204ee4

File tree

1 file changed

+6
-0
lines changed
  • website/content/en/docs/upgrading-sdk-version

1 file changed

+6
-0
lines changed

website/content/en/docs/upgrading-sdk-version/_index.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,3 +3,9 @@ title: Upgrade SDK Version
33
weight: 4
44
description: Guide to upgrading sdk version for your operator
55
---
6+
7+
## Backwards Compatibility when Upgrading Operator-sdk version
8+
9+
When upgrading your version of Operator-sdk, it is intended that post-1.0.0 minor versions (i.e. 1.y) are backwards compatible and strictly additive. Therefore, you
10+
only need to re-scaffold your operator with a newer version of Operator-SDK if you wish to take advantage of new features. If you do not wish to use new features,
11+
all that should be required is bumping the operator image dependency (if a Helm or Ansible operator) and rebuilding your operator image.

0 commit comments

Comments
 (0)