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.
Related
Kubernetes (v1.10.8) installed on my cloud by kismatic (v1.12.0). How I can update kubernetes to the latest version with kubeadm?
With such version difference - we currently have v1.23 (see official supported releases) - I would consider creating the cluster from the beginning.
If this is not possible, you should upgrade them step by step (from version to version). Here you can find guide that will help to upgrade kubeadm clusters.
A link to older versions you can find here, but
NOTE:
Kubernetes v1.19 documentation is no longer actively maintained. The version you are currently viewing is a static snapshot.
However, you have to have in mind that upgrading through so many versions can cause other issues, so I recommend using the first option.
I am newly hired engineer who started working with istio recently. My application is currently running on istio 1.4.3 and having issues when i tried to upgrade to latest using istioctl upgrade.
Below are the steps i tried
1) Verified the versions using istioctl version and saw that control plane and data plane are running on 1.4.3 whereas client version is 1.5.1 (the version i planned to upgrade).
2) Tried istioctl upgrade and seen a message “cannot upgrade because of mismatch of versions in istio components”.
3) As it was my dev environment, i decided to reinstall using istioctl manifest apply --profile default
4) Above step cost me a lot of time, because i lost all the settings related to ingress gateway connected to AWS ALB, instead ingress controller created a classic load balancer which is not part of our previous set-up.
5) I also lost setting related to prometheus, grafana, kiali.
6) Now i am planning upgrade my prod without messing the current settings, please suggest a correct way to upgrade istio to latest version with zero downtime.
what is the best way to do this upgrade, can you point out any link to documentation apart from what is mentioned in istio website ? Help is much appreciated
can you point out any link to documentation apart from what is mentioned in istio website
https://istio.io has the most comprehensive information on the topic.
There are some prerequisites for the Istio upgrade as well.
- Istio version 1.4.4 or higher is installed.
- Your Istio installation was installed using istioctl.
It looks like your Istio version is a tiny step below minimum supported one :)
what is the best way to do this upgrade,
Usually it is recommended to go 1.4 --> 1.5 and only then 1.5 --> 1.6.
I have found the following document that describes an "experimental feature, which is intended for evaluation purposes only".
But the minimal version for it is 1.3.3 or higher, which might do the trick for you.
I hope that helps.
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.
I am running a web server based on CentOS 5.8 and I need to upgrade my version of bind to make it PCI compliant. I'm currently running bind 9.3.6 and I need to have bind 9.9.8 or higher. I've tried yum update bind but apparently I already have the latest version according to yum. I did some Googling and I found an RPM file bind-9.10.2-1.el5.i686.rpm which looks like it would work but i don't know if it should try installing it or not. I think I would need bind-devel and bind-libs which I can get from the same site. Am I better off compiling from source? I know CentOS 5 is old but I'm trying to avoid reinstalling the whole server.
Installing binary rpm's from later versions of CentOS is unlikely to work: there are many changes since CentOS5.
Rebuilding a src.rpm locally is one way to see what issues there are.
Meanwhile, upgrading to CentOS6 (at least: CentOS7 uses systemd which takes some study) is often not a whole lot more effort than retrofitting something like bind, and will have other efficiencies. YMMV, everyone's does.
I'm working on a VM centos 6.6 on witch I installed collectd to gather metrics,
Everything is ok, but I want to edit some plugins to test collecting metrics from openstack that I've installed (single machine devstack)
I found this link
but the version was debian.
Is there an alternative solution to my problem?
I finally found ans answer for my question, due to fpm command that converts debian packages to rpm and vice versa.
Try to use this link: https://www.digitalocean.com/community/tutorials/how-to-use-fpm-to-easily-create-packages-in-multiple-formats
fondly