ReadMeFeed / Community knowledge
CI/CD, Terraform, Kubernetes, containers and observability.
I am using a mac and apparently installing Docker Desktop is mandatory to use Docker in macOS. Why Docker Desktop is required in Mac and Windows OS, and not in Linux? What purpose Docker Desktop serves? I have tried googling it but can't find appropriate answers.
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?
I am creating an InfluxDB deployment in a Kubernetes cluster (v1.15.2), this is my yaml file: apiVersion: extensions/v1beta1 kind: Deployment metadata: name: monitoring-influxdb namespace: kube-system spec: replicas: 1 template: metadata: labels: task: monitoring k8s-app: influxdb spec: containers: - name: influxdb image: registry.cn-hangzhou.aliyuncs.com/go
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?
I had seen official documentation: https://kubernetes.io/docs/tasks/setup-konnectivity/setup-konnectivity/ but I still failed to understand its meaning. I have few questions: If the connectivity service provides TCP level proxy, so what does the proxy include? If I used the service on a cluster, what will happen to My pods, services, quality for communicatio
I created a custom docker image and push it to docker hub but when I run it in CI/CD it gives me this error. exec /usr/bin/sh: exec format error Where : Dockerfile FROM ubuntu:20.04 RUN apt-get update RUN apt-get install -y software-properties-common RUN apt-get install -y python3-pip RUN pip3 install robotframework .gitlab-ci.yml robot-framework: image: ret
In the quest for ever smaller Docker images, it's common to remove the apt (for Debian/Ubuntu based images) cache after installing packages. Something like RUN rm -rf /var/lib/apt/lists/* I've seen a few Dockerfile s where this is done after each package installation ( example ), i.e. with the pattern # Install some package RUN apt-get update \ && ap
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
A failure needs to be narrowed down before settings are changed or operations retried. Which evidence best separates application errors from environment and dependency problems?
docker
python
kubernetes
terraform
debian
ubuntu
opentelemetry