Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed last month.
Improve this question
I am pretty new to AKS and helm. I need to install filebeat and metricbeat on AKS cluster using Helm Chart. Request any guidance or pointer to get started.
Once you have kubernetes cluster up & running and set on AKS you can install the helm locally or the bastion you are using.
Get and set context of the kubeconfig file of AKS cluster on local or bastion so you can now access the cluster.
Now, Here is the ready-made helm chart of filebeat
Run the command : helm repo add elastic https://helm.elastic.co
it will add the helm repo automatically and after that run command
helm install my-filebeat elastic/filebeat --version 8.5.1
here we are installing version 8.5.1 you can update other environments and configuration by following the documentation.
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 months ago.
Improve this question
I'm trying to install certain version of kubernetes, using yum package manager (In give example I'm trying to install 1.21.8, however yum does not find given package version)
yum install kubelet-1.21.8-0 kubeadm-1.21.8-0 kubectl-1.21.8-0
I also tried like this:
yum install kubelet-1.21.8 kubeadm-1.21.8 kubectl-1.21.8
Output:
No package available
If your trying to install a specific version of the package it is enough to define it during the yum install command as below :
yum install -y kubelet-<version> kubectl-<version> kubeadm-<version>
Please check when you are installing kubernetes version 1.21.8-00, kubernetes-cni package should be (>= 0.8.7) version to satisfy dependency requirements.
So, the final command looks like this:
yum install -y kubelet-1.21.8-00 kubectl-1.21.8-00 kubeadm-1.21.8-00 kubernetes-cni-0.8.7
To verify the version the below command
kubelet --version / kubeadm version / kubectl version.
Note : Add kubernetes source in /etc/yum.repos.d/kubernetes.repo file. And also make sure your Kubernetes version is compatible with the Docker containers engine version to avoid compatibility problems.
How can I change microk8s kubernetes storage location on Windows?
This question was asked a few years ago but the answer is for Linux. They offer a Windows version and I'm wondering if there's a solution. I saw no option of it in the command line help options or on Google. Do I just need to switch to Linux for this option?
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
My IBM Bluemix version is out of date,
Is it possible to update my version without doing a complete reinstallation
The documentation describes how to upgrade Node-RED on IBM Cloud here - https://nodered.org/docs/platforms/bluemix#upgrading-the-version-of-node-red
You need to set the NODE_MODULES_CACHE environment variable via the IBM Cloud console and they cause you application to restage using the command-line. That will cause it to reinstall the node modules from npm, rather than use the locally cached versions.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
What is the best-practice in terms of migrating grafana (configuration, dashboards etc.) to a a newer version ?
I want to migrate a v3 grafana installation to a new server which will be running the v4 codebase with alerting!
According to the docs, grafana v4 will automatically update the database schema once you start it so I assume this process is essentially:
Install grafana v4 on new server.
Copy the /var/lib/grafana/grafana.db from old server to the new one.
Merge the /etc/grafana/grafana.ini file.
Install any plugins
Restart grafana-server
Is their anything I'm missing?
UPDATE:
What if grafana it's deployed as a docker container ? Bellow there's a docker-compose file which spins up a grafana 7.3.5 container, what files should I migrate to the container via mount volume ?
version: "3.1"
services:
grafana_seven:
image: "grafana/grafana:${NEW_TAG}"
user: "${UID}:${GID}"
container_name: newgrafana
ports:
- "3001:3000"
volumes:
- ./tmp_volume/graf_volume/new_grafana/:/var/lib/grafana
That should do it.
If your using sqlite you can just copy the data/grafana.db file to the new server.
One Update:
works like charme
do not forget to update the password(!) of your data sources - that is not copied.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
Our team is starting to use Vagrant for development on Mac OS X machines so we can better simulate our Red Hat Enterprise Linux production environment. Our operations group says our Red Hat License only covers instances being run on our VMWare cluster. How do other people deal with RHEL licensing using Vagrant?
We were in the same situation and decided to use CentOS on our developer boxes. https://www.centos.org/
I downloaded basic rhel server I found online and built a vagrant box with Packer for use in Vagrant/Test Kitchen. I'm forced to use various other repositories (CentOS/EPEL/RPMFusion etc) instead of the RHN repos which I don't have access to without licensing. I actually wrote a small chef cookbook to write all the custom /etc/yum.repos.d/*.repo files after initial install. It definitely works for a dev environment. If you have access to different ISOs then you can built whatever versions of rhel that you need with Packer.
http://dtucker.co.uk/hack/creating-a-vagrant-base-box-for-rhel-with-bento.html
https://github.com/xacaxulu/packer-boxes/blob/master/README.md <----a box to use if you want.
Have you tried this?
https://access.redhat.com/downloads/content/293/ver=1/rhel---7/1.0.0/x86_64/product-downloads
Have you also checked the developer subscriptions?
https://access.redhat.com/support/offerings/developer/
There is a blog specifying how to use vagrant with RHEL... but I can't post 3 links :(
Here is a proposal (I am using this approach since I am also working with rhel vagrant boxes for running ansible scripts)
Create a red hat developers account here (click on register).
Download an rhel vagrant box from here (you will have to log in with your previously created account.
Fire up your box and ssh into it.
Follow these instructions to register your vm