I am trying to deploy kubernetes on "CentOS Linux release 7.0.1406"
using "yum install kubernetes"
Which installs "kubernetes-0.17.1-4.el7.x86_64".
I am unable to understand how I can get the latest stable release (which I believe is 0.20.xxx)
I was also unable to "--enablerepo=updates-testing" which results in error as
below are the available repositories in my computer
base/7/x86_64 CentOS-7 - Base 8,652
extras/7/x86_64 CentOS-7 - Extras 149
updates/7/x86_64 CentOS-7 - Updates 928
repolist: 17,876
The CentOS packages can be found at http://cbs.centos.org/kojifiles/packages/kubernetes.
They are maintained by a community contributors which, unfortunately, means that they sometimes lag behind the latest release until they are rebuilt.
Related
I am trying to install Kubernetes on Ubuntu 20.04 but the latest release is for Ubuntu 16.04. I am following the official tutorial by kubernetes https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/
Is it discontinued for Ubuntu?
As #jordanm and #mdaniel mentioned
likely the upstream disagreements in Debian about vendoring k8s dependencies. Lot of dev discussion about whether or not k8s should even be included in a stable release. OS provided packages are probably the least-common way to provision a cluster.
Related to that, kubernetes binaries are statically linked golang
programs, and thus have very little in the way of "dependency upon. Ubuntu whatever" so it's likely fine to just use the 16.04 repo.
Read: minikube-ubuntu-20.04.
See also: kubernetes-on-ubuntu.
I am trying to install GlusterFS on CentOS 8 Vmware workstation, i am on a bridged network but everytime i attempy to download it i get this messsage. Is there another way to do this or to fix this issue?
at time of this post Gluster 8 (https://www.gluster.org/release-schedule/) is the current maintained version. So to install it you would do
dnf -y install centos-release-gluster8
Please note that you can find other versions in the extras repository which, as you see above, is enabled.
I have a google VM instance which was running flawlessly. It has Centos-7 and Plesk installed in it.
I just stopped it, upgraded machine type (to better CPU and RAM) and started it again. My server stopped responding at all. No websites are running, I can't connect to SSH & Google Cloud SDK Shell is unable to reach server. It says NETWORK ERROR, CONNECTION TIMED OUT. My all other instances works well.
I tried rebooting & resetting multiple times. Reading out stuff from internet since last 6 hours but for no luck. I also tried to clone disk of the instance and creating new instance with the cloned disk but for no luck. Same network connection issue. May be something in OS got corrupted? Please suggest. I have a number of websites hosted on the server which are down due to this. Thanks a lot in advance.
I took screenshot of my VM using Google Cloud Shell. It is as follows:
I connected with serial console which is as follows:
While creating a ticket with google, I found that they've posted some information under "Known Issues". I am pasting the whole stuff as there is no direct link to reach there. The symptoms they told were exactly what was happening to me:
Below is Known Issue Posted by Google:
Description:
We are experiencing an issue with Google Compute Engine instances running RHEL and CentOS 7 and 8. More details on this issue are available in the following article and bugs: https://access.redhat.com/solutions/5272311 https://bugzilla.redhat.com/show_bug.cgi?id=1861977 (RHEL 8) https://bugzilla.redhat.com/show_bug.cgi?id=1862045 (RHEL 7) Symptoms: Instances running RHEL and CentOS 7 and 8 that run yum update may fail to boot after restart with errors messages referring to a combination of: "X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID", "FXSAVE_STATE" or "Find image based on IP". This issue affects instances with specific versions of the shim package installed. To find the currently installed shim version, use the following command: rpm -q shim-x64 Affected shim versions: CentOS 7: shim-x64-15-7.el7_9.x86_64 CentOS 8: shim-x64-15-13.el8.x86_64 RHEL 7: shim-x64-15-7.el7_8.x86_64 RHEL 8: shim-x64-15-14.el8_2.x86_64 Workaround: Do not update or reboot instances running RHEL or CentOS 7 and 8. If you are on an affected shim version, run yum downgrade shim\* grub2\* mokutil to downgrade to the correct version. This command may not work on CentOS 8. If you have already rebooted, you will need to attach the disk to another instance, chroot into the disk, then run the yum downgrade command. We will provide an update by Thursday, 2020-07-30 14:00 US/Pacific with current details.
Start time:
July 30, 2020 at 9:08:34 PM GMT+5
How to diagnose:
Instances running RHEL and CentOS 7 and 8 that run yum update may fail to boot after restart with errors messages referring to a combination of: "X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID", "FXSAVE_STATE" or "Find image based on IP". This issue affects instances with specific versions of the shim package installed. To find the currently installed shim version, use the following command: rpm -q shim-x64 Affected shim versions: CentOS 7: shim-x64-15-7.el7_9.x86_64 CentOS 8: shim-x64-15-13.el8.x86_64 RHEL 7: shim-x64-15-7.el7_8.x86_64 RHEL 8: shim-x64-15-14.el8_2.x86_64
Workaround:
Do not update or reboot instances running RHEL or CentOS 7 and 8. If you are on an affected shim version, run yum downgrade shim\* grub2\* mokutil to downgrade to the correct version. This command may not work on CentOS 8. If you have already rebooted, you will need to attach the disk to another instance, chroot into the disk, then run the yum downgrade command.
As explained in the article Controlling the fabric version that runs on your Cluster, you can choose which version of Service Fabric you want Azure to create for you.
The ServiceFabric nuget package seem to have the same version numbers as the clusters, but older versions of the packages work just fine with newer versions of the cluster.
Now, the release notes for version 5.4.145 state a list of improvements, and mentions that some older versions won't be supported anymore.
What I'm failing to understand is -
Will I get the list of improvements just by upgrading my cluster, or do I also have to upgrade my nuget packages?
Similarly, does it mean I have to upgrade my nuget packages soon, otherwise I'm at risk of running deprecated code?
Would also be nice to get some clarification of what exactly is upgraded when I upgrade a cluster, what's upgraded when I upgrade my packages, and how the two upgrades relate to each other.
There's a difference between the Runtime and the SDK. When the cluster is upgraded, it gets a new runtime. Any improvements in that runtime will be available to existing services running in the cluster.
Upgrading the SDK (or the Nuget packages) will result in new functionality to become available to applications (services/actors) built on top of the cluster runtime.
I'd recommend updating Nuget packages soon after upgrading the cluster to keep them in sync.
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.