ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Background: I have a GKE cluster which has suddenly stopped being able to pull my docker images from GCR; both are in the same GCP project. It has been working well for several months, no issues pulling images, and has now started throwing errors without having made any changes. (NB: I'm generally the only one on my team who accesses Google Cloud, though it'
Asked · Jul 23
answered · Jul 23
Below is the describe output for both my clusterissuer and certificate reource. I am brand new to cert-manager so not 100% sure this is set up properly - we need to use http01 validation however we are not using an nginx controller. Right now we only have 2 microservices so the public-facing IP address simply belongs to a k8s service (type loadbalancer) whic
I'm new to GCP and trying to make heads and tails of it. So far, I've experienced with GKE and Cloud Run. In GKE, I can create a Workload (deployment) for a service of any kind under any port I like and allocate resources to it. Then I can create a load balancer and open the ports from the pods to the Internet. The load balancer has an IP that I can use to a
I found specifying like kubectl --context dev --namespace default {other commands} before kubectl client in many examples. Can I get a clear difference between them in a k8's environment?
I have installed rabbitmq using helm chart on a kubernetes cluster. The rabbitmq pod keeps restarting. On inspecting the pod logs I get the below error 2020-02-26 04:42:31.582 [warning] <0.314.0> Error while waiting for Mnesia tables: {timeout_waiting_for_tables,[rabbit_durable_queue]} 2020-02-26 04:42:31.582 [info] <0.314.0> Waiting for Mnesia t
I want to connect service from one GKE cluster to another one. I created service as a internal load balancer and I would like to attach a static ip to it. I created my service.yml apiVersion: v1 kind: Service metadata: name: ilb-service annotations: cloud.google.com/load-balancer-type: "Internal" kubernetes.io/ingress.global-static-ip-name: es-test labels: a
docker
kubernetes