I have a quick question related to "Kubespray".
Does "Kubespray" support CentOS 8?
I wanted to deploy "Kubespray" on "CentOS" and I came to know that the CentOS 8 has Kernel version 4.18 and If I can use "CentOS 8" for "Kubernetes" deployment, maybe I can get rid of the "c-group" issue which we are currently facing for all the CentOS distribution which has Kernal Version less than 4.18.
Thanks in Advance.
According to the official documentation Kubesprawy provides support for CentOS/RHEL 7 only. The problem is that:
Installing Kubespray on a RHEL8 systems does not work since the
default Python version is 3.6 and thus python3-libselinux should be
installed instead of libselinux-python. Even that python2 is still
available, the libselinux-python package is not.
I hope it helps.
Related
If you want you use the new CRS versions you need at least 2.9.6 of libapache2-mod-security2. see:
https://coreruleset.org/installation/
Is this possible on Debian11? I searched for backports but couldn't find any method on getting this version. Default Debian 11 Version 2.9.3
If you want you use the new CRS versions you need at least 2.9.6 of libapache2-mod-security2. see: https://coreruleset.org/installation/
Thanks, we (CRS team) should add some links to this documentation.
Is this possible on Debian11? I searched for backports but couldn't find any method on getting this version. Default Debian 11 Version 2.9.3
We are working on it, that Debian 11 accepts this version too. Actually, the Debian's package source repository already has the patched 2.9.3:
https://salsa.debian.org/modsecurity-packaging-team/modsecurity-apache/-/blob/bullseye/debian/changelog
You can download that and make an own package.
If you want to avoid to make a custom/own package, follow this link, and you can try the Digitalwave's ModSecurity repository. There you can find the 2.9.6 for Debian 10, 11, Ubuntu 18.04, 20,04 and 22.04.
Note: I'm CRS developer, and Debian maintainer. I made the packages for Debian too.
I just installed centOS8 and then the nmap package.
and I cannot find the ndiff binary.
Weird, I could find it in nmap in centOS7
Anyone having the same problem? Thanks
Ester
Actually, ndiff is not a binary, but a Python 2 script. Due to the deprecation of Python 2 in Fedora and RHEL (and thus in CentOS), ndiff is no longer shipped in current versions of Fedora and RHEL/CentOS. See https://src.fedoraproject.org/rpms/nmap/blob/master/f/nmap.spec#_157 regarding the removal.
I am trying to get kubernetes 1.3 intalled on my centos7 environment. Have spent a terrifying amount of time looking at every doc/guide/tutorial out there, and unfortunately they are all a combination of outdated versions or missing instructions.
The two biggest issues:
the RPM package is out of date. it pulls down 1.2, not 1.3
which means i need to figure out how to install from source/tar, but i cannot find any good documentation out there on how to do that manually on centos7.
I have gotten it work installing 1.2, but have failed trying to upgrade 1.2 to 1.3 using the 1.3 tar.
Any help would be appreciated!
Centos RPMs are maintained by volunteers, and it seems nobody has volunteered to build a 1.3 RPM. The 1.2 RPM was generated by https://github.com/coolsvap. You could try mailing him and asking him to make a 1.3 rpm.
The way you upgrade depends on which kubernetes guide you followed to setup your kubernetes cluster initially. I'm not sure how it works on Centos guide.
I just found this guide http://kubernetes.io/docs/getting-started-guides/kubeadm/ it mentions Kubernetes 1.4, so since this is a most recent version at the time of writing this post, this might be what you need.
i would like to know, based on what rpm packages upgrade i can upgrade my RHEL version 5.11 to 6.x
We can't use re-installation of RHEL 6.x, so wanted an option(s) to upgrade to RHEL 6.x from 5.x by upgrading all needful packages.
By upgrading kernal or core rhel release rpm, can we upgrade to latest?
Please let me know details. Thank you.
In place upgrades between 4, 5, and 6 are not supported by RedHat and you risk impacting the support that you pay for by doing so. The only supported upgrade path is from 6 to 7. The expectation is that an upgrade path will continue in future releases.
You state that you cannot re-install but don't state why. Is it because the criticality of the system or is it because of the configuration of the application? I'm guessing the latter and that the system is not all that critical (because otherwise you wouldn't want to impact your support agreement). With that said, there is a way to upgrade and the procedure is provided by RedHat but, again, it is not supported by them.
The link is: In place upgrade
I learn that RHEL and Centos has the exact same source code. So my question here is if one application built for RHEL 6.4, could we just install and make it running on Centos 6.4 without any update?
And another question is RHEL and Centos will always use the same version number for the same source code, right?
Yes, software built on RHEL 6.4 should work as-is on CentOS 6.4 (assuming you don't depend on one of the relatively few RHEL-specific details, mostly to do with branding).
CentOS, except where necessary, uses upstream RHEL sources unmodified. When they need to modify a package they indicate that in the release notes and in the release field of the RPM in question.