I have a 2-raspberry Pi 4 kubernetes Cluster. It uses k3s : (https://github.com/rancher/k3s) which is built on k8s 1.16.
I want to install k8s dashboard (https://github.com/kubernetes/dashboard)
However the last arm-compile image is the v1.10.1 which is not compatible with k8s-1.16 .
Is there a (un)official image of K8s dahsboard v2.0.0-betaX compiled for arm ?
Or someone had any tips on how to compile such an arm image ?
thanks in advance.
According to this article on docker blog docker supports multi platform images since September 2017.
Kubernetes dashboard images are already supporting multiple architectures so you don't need to build it by yourself.
Take a look at the image below.
You can use kubernetesui/dashboard tag and your docker daemon should pull appropriate image for your architecture.
Let me know if it helped.
Related
I am using GitLab runner in Kubernetes for building our application. Since ours is a docker in a docker use case, we are using Kaniko to build images from a DockerFile.
I am having a hard time figuring out how to implement horizontal/vertical scaling for pods and instances.
Looking at this article https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runnersmachine-section , it says to use docker+machine image, but
I don't want to have any docker dependency in our build process especially when Kubernetes has deprecated docker support in newer versions.
Any advice?
Are there any examples for creating a blockchain network on top of minikube environment?
Take a look at the following repositories where you can find helm charts which should facilitate the whole deployment process:
https://github.com/hyfen-nl/PIVT
https://github.com/splunk/hyperledger-fabric-k8s
Note that they require helm 2.11 and 2.16 or newer installed in your kubernetes cluster.
I am trying to setup Kubernetes on a s390x machines. Having downloaded packages kubeadm, kubectl and kubelet specific to s390x architecture. I was under the impression that kubeadm init will download the control pane images for the same architecture, which proved to be incorrect.
kubeadm init seems to have downloaded amd64 images which results in the following error standard_init_linux.go:187: exec user process caused "exec format error
Can someone please let me know if there are s390x specific images for the below containers, if yes please provide me the container tags or link to it please
k8s.gcr.io/kube-apiserver:v1.17.2
k8s.gcr.io/kube-controller-manager:v1.17.2
k8s.gcr.io/kube-scheduler:v1.17.2
k8s.gcr.io/kube-proxy:v1.17.2
k8s.gcr.io/pause:3.1
k8s.gcr.io/etcd:3.4.3-0
k8s.gcr.io/coredns:1.6.5
From the docs we can read:
kubeadm deb/rpm packages and binaries are built for amd64, arm (32-bit), arm64, ppc64le, and s390x following the multi-platform proposal.
Multiplatform container images for the control plane and addons are also supported since v1.12.
Only some of the network providers offer solutions for all platforms. Please consult the list of network providers above or the documentation from each provider to figure out whether the provider supports your chosen platform.
Repo for s390x is available here.
I think it might be helpful to follow this guide for Installing Kubernetes 1.12 on SUSE Linux using kubeadm
To solve the problem:
Download the control pane containers specific to s390x (kube-controller-manager-s390x:v1.17.2 etc..,)
Tag to the names in which kubeadm lookup
Run kubeadm init command
More information you can find here: kubernestes-for-s309x, kubeadm-s390x.
Resolved following with the below steps:
1) Downloaded the control pane images for s390x from k8s docker repository (kube-controller-manager-s390x:v1.17.2,, likewise)
2) Had to tag the images to kube-controller-manager:v1.17.2 , because kubeadm manifests looks for this name
3) initialized my cluster and there it is " Your Kubernetes control-plane has initialized successfully! "
We are installing Open Loyalty Program on to the Google Cloud. Please Google Open Loyalty by Divante Ltd.
We have been trying to deploy this application on google cloud using Kubernetes.
The instance used to deploy this application contains Debian v4.9 as its OS. And we installed Docker, GCloud, Kubernetes and Kompose as the tools for deployment. We built two docker images for the frontend and backend and linked them to the docker-compose file. Now in frontend image, we used (node:5) image from docker hub in Dockerfile of the frontend.
We also changed the docker-compose file as seen below:
enter image description here
After changing the docker-compose file, we ran “kompose up” within the same directory.
which created the deployment and service ‘yaml’ file and then proceeded to run it.
We have pods as given below, but the frontend pod shows some error and some logs.enter image description here
It says yarn not found. When we execute the same process on a local machine, it works as expected.
We are also trying to seek help from Google Support but your help and suggestions will also be highly appreciated.
Yarn is available from node:6. Your front-end image is too old.
I'm new in kubernetes and I have some doubts about the installation of kubernetes on centos 7, I have read some documentation on some links:
https://kubernetes.io/docs/getting-started-guides/kubeadm/
https://kubernetes.io/docs/getting-started-guides/centos/centos_manual_config/
But I not undestanding which procedure to follow, on first link it show how to install it using kubeadm but at the end of the article on "Limitations" appear that this tool "is a work in progress and these limitations will be addressed in due course", on second link I need to have at least 2 machines, so my question is which is better to use if I will to install it like production.
Thanks in advance
kubeadm.
kubeadm now can support for multi masters, which is considerable for production.
The kubeadm also supplies a secure deployment. It automatically configs TLS settings or RBAC for the cluster, which is not included in the "manual installation page".
My advice: play kubeadm in your development environment first, so that you see how kubeadm deploys a Kubernetes cluster, many components can be deployed by Kubernetes itself. Then, you decide whether use it in your production.
You can follow up the repository made by one of our developer with an additional thing of Horizontal Pod autoscaling of stateless application.
https://github.com/vevsatechnologies/Install-Kubernetes-on-CentOs