I have installed the promtail/loki using the helm chart in my Kubernetes cluster by following the below link https://grafana.com/docs/loki/latest/installation/helm/ But By default, it collects only container logs. I want to configure my promtail in a way that it will be able to collect the application log files as well from the container. Example : I ..
I Described the pod using "kubectl describe pod tiller-deploy -n kube-system" , I Found Reason like "Failed to pull image "gcr.io/kubernetes-helm/tiller:v2.16.7": rpc error: code = Unknown desc = failed to pull and unpack image "gcr.io/kubernetes-helm/tiller:v2.16.7": failed to resolve reference "gcr.io/kubernetes-helm/tiller:v2.16.7": failed to authorize: failed to fetch anonymous token: unexpected status: 401 Unauthorized" Anyone help me ..
I have a problem with overwriting the entrypoint in my Dockerfile. For this (as I know) docker run with –entrypoint option is used, e.g.: docker run –entrypoint "python3 main_script.py DEV" However, in my case I can’t use the docker run command because I have to use Helm charts for the deployments. Is there an alternative ..
I have created a Docker image and is in my local repository like this: docker build -t myimage:latest . When I list my images I can see it just fine: docker image ls –all REPOSITORY TAG IMAGE ID CREATED SIZE myimage latest a91ac47487d4 28 minutes ago 370MB Now I want to run this in Kubernetes, ..
I am trying to build a multi arch Docker image with some tools for kubernetes using alpine as the base image, but on Arm64, some binaries are just missing and on amd64 they are there and executing. Here are the Dockerfiles amd64: FROM alpine:latest RUN apk –no-cache add curl openssl RUN curl -LO "https://dl.k8s.io/release/$(curl -L ..
I’m trying to install elasticsearch on gke based on this tutorial but it’s giving me imagepullbackoff err Events: Type Reason Age From Message —- —— —- —- ——- Normal Scheduled 43s default-scheduler Successfully assigned elastic-system/elastic-operator-0 to gke-cls-test-default-pool-fb827c76-vj15 Warning Failed 26s kubelet Failed to pull image "docker.elastic.co/eck/eck-operator:1.7.1": rpc error: code = Unknown desc = Error response ..
I’m facing a problem with the image groundnuty/k8s-wait-for. Project at github and repo at dockerhub. I’m pretty sure that error is in command arguments, as the init container fails with Init:CrashLoopBackOff. About image: This image is used for init containers, which need to postpone a pod deployment. The script that is in the image waits ..
I followed these instructions to deploy a Dask cluster on Kubernetes/Minikube with Helm. I installed and the deployed with the following command: helm install dask-chart dask/dask Running kubectl get services I see the scheduler, however the EXTERNAL-IP is none and I cannot connect to the scheduler: NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE dask-chart-scheduler ClusterIP 10.107.222.251 ..
I have a local kubernetes cluster, that is trying to load images from my local Docker repo. When I do a "docker images", I get: cluster.local/container-images/app-shiny-app-validation-app-converter 1.6.9 cluster.local/container-images/app-shiny-app-validation 1.6.9 Given I know the above images are there, I run some helm commands which uses these images, but I get the below error: Events: Type Reason ..
I have docker image/ACR running successfully in my AKS cluster. Docker Image has configuration file with all credentials saved in it. I want to change values of .config file at the time of kubernetes deployment creation. I am using helm chart for deployment. Do I need to mention these values in values.yaml file ? How ..