The armhf and arm64 templates are no longer required, since
they are duplicates of the normal templates. What matters more
for arm is using a multi-arch template, or building on the
correct device. There's no explicit need to use the armhf
template as it adds nothing.
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Version change (see: Impact to existing users)
Impact to existing users
Users of armhf templates can simply remove the suffix in their stack.yml file and build with the non-armhf templates on their devices.
java8 users should migrate with immediate effect, or use the older release tag mentioned above when setting up their templates repo.
Signed-off-by: Alex Ellis (OpenFaaS Ltd) alexellis2@gmail.com
Description
Remove Java8 and arm-based templates
Motivation and Context
Users are still using the java8 template despite java8 being deprecated. This should prevent that going forward, the java11 template is compatible.
Users can use an older SHA / tag of the repo if they are still migrating off the deprecated java8 template:
https://github.com/openfaas/templates/releases/tag/1.9.0
The armhf and arm64 templates are no longer required, since they are duplicates of the normal templates. What matters more for arm is using a multi-arch template, or building on the correct device. There's no explicit need to use the armhf template as it adds nothing.
Types of changes
Impact to existing users
Users of armhf templates can simply remove the suffix in their stack.yml file and build with the non-armhf templates on their devices.
java8 users should migrate with immediate effect, or use the older release tag mentioned above when setting up their templates repo.