I think I've finally tamed this #OpenSearch setup on this #Rancher#RKE2 cluster. Today's adventure was schema conflicts. Pods labeled with "app" while others are labeled with app.kubernetes.io cause a problem for inputs as it looks to OpenSearch like there's a string where an object should be and the flatten hashes on the #fluentd output wasn't quite enough to cut it, but the dedot filter brought it in the rest of the way there.
Our #flocktofedora experience has felt very positive. So many productive conversations both from stage and in the "hallway track" as stakeholders of various enterprise Linux communities came together to talk face to face, build relationships, and work to establish a shared vision for the future. Sincere thanks to the Fedora community for holding space for this necessary work. #rockylinux#almalinux#centosstream#rhel
In tech years, I'm pretty old. I started using Linux when it was easiest to get as a boot image and root image on the Banjo FTP server, maybe ftp.funet.fi. Later, SLS, then Slackware, then FreeBSD, OpenBSD (co-wrote the IP Filter howto)... then #RedHat bought my company. I've subsequently spent more than half my life working at RH, and most of that time running Fedora, since Fedora was a thing. This is not impressive, I've just been here, and that means I have some perspective on #opensource.
Which leads me to the last few years. Every 3 years, we make a new #RHEL major release, primarily from a subset of #Fedora content, plus a few other upstreams. From that point forward, each update to that RHEL release isn't necessarily from Fedora, it's from upstream, where Fedora's sources come from. This meant that we couldn't have the kind of community that Fedora formed for RHEL. That's why we created #CentOSStream.
The patch by @jonathanspw has been merged into @centos Stream 8! The c9s patch state is a bit different as the maintainer would rather backport than rebase.
This comes after Red Hat has now rated CVE-2023-38403 a Important, the second highest rating.
> We will also start asking anyone who reports bugs in AlmaLinux OS to attempt to test and replicate the problem in CentOS Stream as well, so we can focus our energy on correcting it in the right place.
"The chase for “bug to bug compatibility” hurts community, hurts RHEL customers and hurts the industry as a whole. The real innovation behind the CentOS Stream is the attempt to change it."
I have to admit that whenever I have weird server problems on #CentOS Stream, there's always a question of whether or not it's Stream or something else and that lack of certainty usually is just enough that I often might not file an issue for Stream, but also just enough that I second guess running CentOS Stream over #AlmaLinux in cases where I don't want/need full on #RHEL. When stuff breaks on AlmaLinux, I'm less likely to question the distro (even though bugs happen everywhere).
@vwbusguy Here's the thing. When using @centos, the main point of value creation is when you participate in the project. Whether that's filing bugs/submitting fixes to #CentOSStream or contributing/supporting SIGs like the Hyperscale and Kmods SIGs, you are taking some ownership of the project to help make it sustainable.
This is also true in @fedora, it's just new to community users of the Enterprise Linux ecosystem.
CentOS Stream should become a product supported by #RedHat.
Red Hat has clearly a service problem, and if they want people to use #CentOSStream instead of rebuilds, they should turn CentOS Stream in a product charging lower prices for live patching and extended support (maybe a subscription?).
They can maintain a clear differentiation between #RHEL and CentOS Stream, with both serving different cases.
This backing of CentOS Stream will immensely increase the trust on the distro and increase its usage.
@evasb@ablackcatstail yep that's you, being a stan for #centosstream. Being condescending to rebuild projects. Clearly either not understanding or deliberately downplaying #redhat's attempted circumvention of #GPL
And now circling back round to support #AlmaLinux for some reason
Red Hat answered a lot of the concerns about their last move. Makes sense to me, reading this.
I’m not saying I totally agree with the move, but I understand why they’re doing it.
@evasb@thelinuxEXP#CentOSStream is an upsteam sandbox for new features that may or may not be included in the next release.
This specifically cant be used by projects such as #AlmaLinux or #RockyLinux or the now unsupported #centos because they wont be able to guarantee 1:1 correspondence with #RHEL
It IS different and the TOS of #Redhat developer program forbid redistribution of rhel source which is against #GPL
@gnarkotics@thelinuxEXP No. All #CentOSStream updates are good enough to be included in #RHEL and most of them are included. The differences are that CentOS Stream will sometimes receive earlier or even more updates (an earlier fix would be released sooner on CentOS Stream in a new package, RHEL would receive later in a later package if it is not critical in a new minor release).
The difference between RHEL and CentOS Stream is not the code or features that will be included in a new release (false), but is the cadence of the update releases.
Most of the people bitching in this thread could use #stream, those bitching about lack of support need to engage with their account managers.
Those suggesting that #redhat is suddenly anti opensource are on some good shit. 2 Upstream fully open distros and then one for commercial purposes is anti-opensource?
@gnuplusmatt Sorry for thinking that you were a RH employee.
But my points stand. #RedHat badmouthed #CentOSStream in their manuals as if CentOS Stream was a competitor, and now they have to retract everything because it is simply not true.
I use CentOS Stream in some personal servers, never had a problem (I only wish something to easily update for the next Stream version) but I know that in many third-world countries people depend on these clones to make the ends meet. Red Hat just shrugged off and this is sad.