New answers tagged

0

A helm hook pretty much has to be a Job or Pod. Thus choosing between using a hook or using a Job doesn't make much sense - you are usually best off using a Job which is annotated as a pre-upgrade hook. And yes, the timeout probably needs to be increased by the users. Unfortunately it's not possible to define the timeout in the chart itself. In some cases it ...


-1

Actually, I should have searched more: NodePort is what I want, letting me expose ports on my local machine.


0

Answering my own question here. Eventually, I went with OpenKruise, which is a pretty simple but cool open-source framework for, amongst other things, creating a centralised way of managing sidecars and init-containers in a cluster, without needing to concern application developers.


0

I suggest you create a Deployment of caddy:2 Pods which a Caddyfile mounted from a Secret, something like this: http://elastic-proxy.default.svc.cluster.local:9243 { reverse_proxy https://xxx.yyy.eu-west-3.aws.elastic-cloud.com:9243 { header_up Authorization: Basic Zm9vOmJhcgo= } } The create a Service named elastic-proxy in the namespace (...


0

This is a little off. You are comparing a "Time Series Database" to a "Log Shipper". How Prometheus Works Any service/entity prometheus wants to run monitor has to provide an "exporter". An exporter is just a http endpoint that has metrics in a simple text format. The exporter can be a standalone app, a web sever linking to a ...


0

You can now use the DaemonSet to load self-signed CAs when using containerd: https://github.com/samos123/gke-node-ca-importer Credit to @nstogner: https://github.com/samos123/gke-node-ca-importer/commit/756674ee595e1cf86df4b3181bb3cf687bd72c97


0

I want to add a quick and dirty solution to this. I often add sleep 600 to the end of a command that's failing unexpectedly so that I can exec in and poke around to see what happened. With that said, Karthick's answer is better, this is just a simple solution that doesn't follow best practices. I encourage you not to use sleep infinity, because it's very ...


0

here is the solution I found in stack overflow link here what I did here please create vi /etc/docker/daemon.json and inside added below: } "exec-opts": ["native.cgroupdriver=systemd"] } after run this command and solve the problem sudo systemctl daemon-reload sudo systemctl restart docker sudo systemctl restart kubelet


1

Add any tiny http-server wrapper to your script and deploy your docker image as a Cloud Run service and use Cloud Scheduler that will invoke it by cron. https://cloud.google.com/run/docs/triggering/using-scheduler


0

Chinmay Mandal answer is legend. Basically this saved me a lot of time kubectl describe pods -n namespace. Just read through the file and in my case I had the k8s "taints" wrong, and for some reason was impacting on how the pods gather resources from node.


Top 50 recent answers are included