251a1a69f · cryptotaxi247/netdata-1

@@ -27,72 +27,67 @@ The following table shows a general outline of the various support tiers and cat

29

30 -- ‘Bug Support’: How we handle of platform-specific bugs.

31 -- ‘Guaranteed Configurations’: Which runtime configurations for the Agent we try to guarantee will work with minimal

32 - effort from users.

33 -- ‘CI Coverage’: What level of coverage we provide for the platform in CI.

34 -- ‘Native Packages’: Whether we provide native packages for the system package manager for the platform.

35 -- ‘Static Build Support’: How well our static builds are expected to work on the platform.

30 +- 'Bug Support': How we handle platform-specific bugs.

31 +- 'Guaranteed Configurations': Which runtime configurations for the Agent we try to guarantee will work with minimal effort from users.

32 +- 'CI Coverage': What level of coverage we provide for the platform in CI.

33 +- 'Native Packages': Whether we provide native packages for the system package manager for the platform.

34 +- 'Static Build Support': How well our static builds are expected to work on the platform.

35

36 ## Currently supported platforms

37

38 ### Core

39

41 -Platforms in the core support tier are our top priority. They are covered rigorously in our CI, usually

42 -include official binary packages, and any platform-specific bugs receive a high priority. From the perspective

43 -of our developers, platforms in the core support tier _must_ work, with almost no exceptions.

44 -Our [static builds](#static-builds) are expected to work on these platforms if available. Source-based installs are

45 -expected

46 -to work on these platforms with minimal user effort.

47 -

49 -|--------------------------|----------------|----------------------------------------|----------------------------------------------------------------------------------------------------------------|

50 -| Alpine Linux | 3.18 | No | The latest release of Alpine Linux is guaranteed to remain at **Core** tier due to usage for our Docker images |

53 -| Amazon Linux | 2023 | x86\_64, AArch64 | |

54 -| Amazon Linux | 2 | x86\_64, AArch64 | |

55 -| CentOS | 7.x | x86\_64 | |

57 -| Debian | 12.x | x86\_64, i386, ARMv7, AArch64 | |

58 -| Debian | 11.x | x86\_64, i386, ARMv7, AArch64 | |

59 -| Fedora | 40 | x86\_64, AArch64 | |

60 -| Fedora | 39 | x86\_64, AArch64 | |

63 -| Oracle Linux | 9.x | x86\_64, AArch64 | |

64 -| Oracle Linux | 8.x | x86\_64, AArch64 | |

65 -| Red Hat Enterprise Linux | 9.x | x86\_64, AArch64 | |

66 -| Red Hat Enterprise Linux | 8.x | x86\_64, AArch64 | |

67 -| Red Hat Enterprise Linux | 7.x | x86\_64 | |

68 -| Ubuntu | 24.04 | x86\_64, AArch64, ARMv7 | |

69 -| Ubuntu | 22.04 | x86\_64, ARMv7, AArch64 | |

70 -| Ubuntu | 20.04 | x86\_64, ARMv7, AArch64 | |

40 +Platforms in the core support tier are our top priority. They are covered rigorously in our CI, usually include official binary packages, and any platform-specific bugs receive a high priority. From the perspective of our developers, platforms in the core support tier _must_ work, with almost no exceptions.

41 +

42 +Our [static builds](#static-builds) are expected to work on these platforms if available. Source-based installs are expected to work on these platforms with minimal user effort.

43 +

45 +|--------------------------|----------------|-------------------------------|----------------------------------------------------------------------------------------------------------------|

46 +| Alpine Linux | 3.23 | No | The latest release of Alpine Linux is guaranteed to remain at **Core** tier due to usage for our Docker images |

47 +| Alpine Linux | 3.22 | No | |

50 +| Amazon Linux | 2023 | x86\_64, AArch64 | |

51 +| Amazon Linux | 2 | x86\_64, AArch64 | |

52 +| CentOS | 7.x | x86\_64 | |

54 +| Debian | 13.x | x86\_64, i386, ARMv7, AArch64 | |

55 +| Debian | 12.x | x86\_64, i386, ARMv7, AArch64 | |

56 +| Debian | 11.x | x86\_64, i386, ARMv7, AArch64 | |

57 +| Fedora | 43 | x86\_64, AArch64 | |

58 +| Fedora | 42 | x86\_64, AArch64 | |

59 +| Fedora | 41 | x86\_64, AArch64 | |

63 +| Oracle Linux | 10.x | x86\_64, AArch64 | |

64 +| Oracle Linux | 9.x | x86\_64, AArch64 | |

65 +| Oracle Linux | 8.x | x86\_64, AArch64 | |

66 +| Red Hat Enterprise Linux | 9.x | x86\_64, AArch64 | |

67 +| Red Hat Enterprise Linux | 8.x | x86\_64, AArch64 | |

68 +| Red Hat Enterprise Linux | 7.x | x86\_64 | |

72 +| Ubuntu | 25.10 | x86\_64, AArch64, ARMv7 | |

73 +| Ubuntu | 25.04 | x86\_64, AArch64, ARMv7 | |

74 +| Ubuntu | 24.04 | x86\_64, AArch64, ARMv7 | |

75 +| Ubuntu | 22.04 | x86\_64, ARMv7, AArch64 | |

76 +| Ubuntu | 20.04 | x86\_64, ARMv7, AArch64 | |

77

78 ### Intermediate

79

74 -Platforms in the intermediate support tier are those which Netdata wants to support, but cannot justify core level

75 -support for. They are also covered in CI, but not as rigorously as the core tier. They may or may not include

76 -official binary packages, and any platform-specific bugs receive a normal priority. Generally, we will add new

77 -platforms that we officially support ourselves to the intermediate tier. Our [static builds](#static-builds) are

78 -expected to work on these platforms if available. Source-based installs are expected to work on these platforms

79 -with minimal user effort.

80 -

82 -|---------------|------------|--------------------------|------------------------------------------------------------------------------------------------------|

83 -| Alpine Linux | Edge | No | |

84 -| Alpine Linux | 3.17 | No | |

80 +Platforms in the intermediate support tier are those which Netdata wants to support, but cannot justify core level support for. They are also covered in CI, but not as rigorously as the core tier. They may or may not include official binary packages, and any platform-specific bugs receive a normal priority. Generally, we will add new platforms that we officially support ourselves to the intermediate tier. Our [static builds](#static-builds) are expected to work on these platforms if available. Source-based installs are expected to work on these platforms with minimal user effort.

81 +

83 +|---------------|---------|--------------------------|-------------------------------------------------------------------------|

84 +| Alpine Linux | Edge | No | |

87

88 ### Community

89

91 -Platforms in the community support tier are those which are primarily supported by community contributors. They may

92 -receive some support from Netdata, but are only a best-effort affair. When a community member makes a contribution

93 -to add support for a new platform, that platform generally will start in this tier. Our [static builds](#static-builds)

94 -are expected to work on these platforms if available. Source-based installs are usually expected to work on these

95 -platforms, but may require some extra effort from users.

90 +Platforms in the community support tier are those which are primarily supported by community contributors. They may receive some support from Netdata, but are only a best-effort affair. When a community member makes a contribution to add support for a new platform, that platform generally will start in this tier. Our [static builds](#static-builds) are expected to work on these platforms if available. Source-based installs are usually expected to work on these platforms, but may require some extra effort from users.

91

93 |-------------|-----------|--------------------------|-----------------------------------------------------------------------------------------------------------|

@@ -107,47 +102,41 @@ platforms, but may require some extra effort from users.

102

103 ## Third-party supported platforms

104

110 -Some platform maintainers actively support Netdata on their platforms even though we do not provide official

111 -support. Third-party supported platforms may work, but the experience of using Netdata on such platforms is not

112 -something we can guarantee. When you use an externally supported platform and report a bug, we will either ask

113 -you to reproduce the issue on a supported platform or submit a support request directly to the platform maintainers.

105 +Some platform maintainers actively support Netdata on their platforms even though we do not provide official support. Third-party supported platforms may work, but the experience of using Netdata on such platforms is not something we can guarantee. When you use an externally supported platform and report a bug, we will either ask you to reproduce the issue on a supported platform or submit a support request directly to the platform maintainers.

106

107 Currently, we know of the following platforms having some degree of third-party support for Netdata:

108

117 -- NixOS: Netdata’s official installation methods do not support NixOS, but the NixOS maintainers provide their

118 - own Netdata packages for their platform.

119 -- Rockstor: Rockstor provides support for a Netdata add-on for their NAS platform. The Rockstor community and

120 - developers are the primary source for support on their platform.

109 +- NixOS: Netdata's official installation methods do not support NixOS, but the NixOS maintainers provide their own Netdata packages for their platform.

110 +- Rockstor: Rockstor provides support for a Netdata add-on for their NAS platform. The Rockstor community and developers are the primary source for support on their platform.

111

112 ## Previously supported platforms

113

124 -As platforms become end of life upstream, Netdata will stop officially supporting them. We will not actively break

125 -things on these platforms, but we will also not make any effort to ensure that things keep working on them either.

126 -If you report a bug on a previously supported platforms, we will ask you to reproduce the issue on a currently

127 -supported platform. If the issue is not reproducible, it will be closed.

114 +:::note

115 +

116 +We consider a platform to be end of life when the upstream maintainers of that platform stop providing official support for it themselves, or when that platform transitions into an 'extended security maintenance' period.

117

129 -We consider a platform to be end of life when the upstream maintainers of that platform stop providing official

130 -support for it themselves, or when that platform transitions into an ‘extended security maintenance’ period.

131 -Platforms that meet these criteria will be immediately transitioned to the **Previously Supported** category,

132 -with no prior warning from Netdata and no deprecation notice, unlike those being dropped for technical reasons,

133 -as our end of support should already coincide with the end of the normal support lifecycle for that platform.

118 +Platforms that meet these criteria will be immediately transitioned to the **Previously Supported** category. Unlike platforms dropped for technical reasons, there will be no prior warning from Netdata and no deprecation notice. This is because our end of support should already coincide with the end of the normal support lifecycle for that platform.

119

135 -On occasion, we may also drop support for a platform due to technical limitations. In such cases, this will be

136 -announced in the release notes of the next stable release with a deprecation notice. The platform will be supported

137 -for _that release_, and will be removed from nightlies some time before the next release after that one.

120 +:::

121

122 This is a list of platforms that we have supported in the recent past but no longer officially support:

123

124 | Platform | Version | Notes |

125 |--------------|-----------|----------------------|

126 +| Alpine Linux | 3.18 | EOL as of 2024-05-23 |

127 +| Alpine Linux | 3.17 | EOL as of 2023-11-01 |

128 | Alpine Linux | 3.16 | EOL as of 2024-05-23 |

129 | Alpine Linux | 3.15 | EOL as of 2023-11-01 |

130 | Alpine Linux | 3.14 | EOL as of 2023-05-01 |

131 | Debian | 10.x | EOL as of 2024-07-01 |

132 +| Fedora | 40 | EOL as of 2024-11-12 |

133 +| Fedora | 39 | EOL as of 2024-05-14 |

134 | Fedora | 38 | EOL as of 2024-05-14 |

135 | Fedora | 37 | EOL as of 2023-12-05 |

136 +| openSUSE | Leap 15.5 | EOL as of 2024-12-31 |

137 | openSUSE | Leap 15.4 | EOL as of 2023-12-07 |

138 | openSUSE | Leap 15.3 | EOL as of 2022-12-01 |

139 +| Ubuntu | 24.10 | EOL as of 2024-07-01 |

140 | Ubuntu | 23.10 | EOL as of 2024-07-01 |

141 | Ubuntu | 23.04 | EOL as of 2024-01-20 |

142 | Ubuntu | 22.10 | EOL as of 2023-07-20 |

@@ -155,21 +144,23 @@ This is a list of platforms that we have supported in the recent past but no lon

144

145 ## Static builds

146

158 -The Netdata team provides static builds of Netdata for Linux systems with a selection of common CPU

159 -architectures. These static builds are largely self-contained, only requiring a a POSIX-compliant shell on the target

160 -system to provide their basic functionality. Static builds are built in an Alpine Linux environment using musl. This

161 -means that they generally do not support non-local username mappings or exotic name resolution configurations.

147 +The Netdata team provides static builds of Netdata for Linux systems with a selection of common CPU architectures. These static builds are largely self-contained, only requiring a POSIX-compliant shell on the target system to provide their basic functionality. Static builds are built in an Alpine Linux environment using musl. This means that they generally do not support non-local username mappings or exotic name resolution configurations.

148 +

149 +### Build Process

150 +

151 +The entrypoint for the static build process is `packaging/makeself/build-static.sh`. This script uses Docker or Podman to create self-contained static binaries for multiple architectures. The build system uses QEMU emulation to enable cross-architecture builds on x86_64 build hosts.

152 +

153 +### Supported Architectures

154

155 We currently provide static builds for the following CPU architectures:

156

165 -- 64-bit x86

166 -- ARMv7

167 -- ARMv6

168 -- AArch64

157 +- 64-bit x86 (x86_64/amd64)

158 +- ARMv7 (armv7l)

159 +- ARMv6 (armv6l)

160 +- AArch64 (arm64)

161

162 ## Platform-specific support considerations

163

164 ### Systemd

165

174 -Many of our systemd integrations are not supported in our static builds. This is due to a general refusal by the

175 -systemd developers to support static linking (or any C runtime other than glibc), and is not something we can resolve.

166 +Many of our systemd integrations are not supported in our static builds. This is due to a general refusal by the systemd developers to support static linking (or any C runtime other than glibc), and is not something we can resolve.

Update PLATFORM_SUPPORT.md (#21422)