-
Notifications
You must be signed in to change notification settings - Fork 380
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
balena os and device type support policies #3117
base: master
Are you sure you want to change the base?
Conversation
Website deployed to CF Pages, 👀 preview link https://35058e01.balenacloud-docs.pages.dev |
Find more information below about our version support policy. | ||
|
||
__Note:__ {{ $names.os.upper }} 1.x to 2.x updates limit the amount of data you can have in your application's `/data` folder to about 170MB (compressed). If you have more data, the update will fail and your device won't be modified. | ||
|
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.
This note is probably no longer relevant as we should have no devices lower than v2.14 on the fleets.
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.
Agreed
At balena, we’re here to make sure balenaOS runs smoothly on actively maintained hardware models. This policy lays out what we support, what you can expect, and how we handle devices when they reach the end of their lifecycle. | ||
|
||
**What We Offer for Official Supported Hardware Models** | ||
- balenaOS Image: A tested and ready-to-use version of balenaOS, available in our documentation. |
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.
available in our documentation
is ambiguous, not sure what it is referring to. Does it mean available to download through the official channels? What has the documentation to do with balenaOS images?
**When Does a Device Get Discontinued?** | ||
We’ll discontinue a device type if: | ||
- The Manufacturer Stops Support: If the hardware maker stops supporting or selling the device. | ||
- It’s No Longer Used: No new devices of this type have been added to balenaCloud in the past 6 months. |
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.
Has this always been the case? If I were a customer and I'm paying for my fleet of devices, even if the number is stable, I would strongly argue the device is actively used.
I personally don't see a reason to state something like this - if a device is really no longer being used we can discontinue it and no-one will realize.
**What if You’re Using a Discontinued Device?** | ||
Here’s what you can expect: | ||
- Support Wrap-Up: Updates, patches, and bug fixes will no longer be provided. We’ll still do our best to help with workarounds or recommend alternative devices. | ||
- Custom Support Options: Need continued support? We can explore custom options on a case-by-case basis, which may involve additional fees. |
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.
There is also forum based, community and best effort support. Should we not mention that?
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.
That would be a different entry in the FAQ regarding how to get support on a community device
Find more information below about our version support policy. | ||
|
||
__Note:__ {{ $names.os.upper }} 1.x to 2.x updates limit the amount of data you can have in your application's `/data` folder to about 170MB (compressed). If you have more data, the update will fail and your device won't be modified. | ||
|
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.
Agreed
- The device type will stop appearing as an option for creating new fleets or adding new devices in the dashboard. | ||
- Any devices already provisioned will keep working, but they won’t get any more OS updates. | ||
|
||
**When Does a Device Get Discontinued?** |
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.
Clarify what discontinuation means in the balenaCloud sense which is very different to real terms
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.
I don't think we currently discontinue devices from BC - we commit to keeping them working as they were on the last release. That is made possible by API versioning and the introduction of new features on new versioned API. This is obviously great for the product as a value add for customers, and up to date we have been able to afaik, but it may be something the backend guys object to.
Co-authored-by: Vipul Gupta <[email protected]>
Co-authored-by: Vipul Gupta <[email protected]>
Pull request was converted to draft
Co-authored-by: Vipul Gupta <[email protected]>
Co-authored-by: Vipul Gupta <[email protected]>
Co-authored-by: Vipul Gupta <[email protected]>
Co-authored-by: Vipul Gupta <[email protected]>
Co-authored-by: Vipul Gupta <[email protected]>
Co-authored-by: Vipul Gupta <[email protected]>
Clarifying our support policies around balenaOS releases and device types