How should I approach a RabbitMQ upgrade?
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
ReadMeFeed / Community knowledge
CI/CD, Terraform, Kubernetes, containers and observability.
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
I have a problem with helm deployment. It has happend after I have added a new environment variable to the deployment. When I execute: helm upgrade [RELEASE] [CHART] I get the following error: Error: The order in patch list: [ map[name:APP_ENV value:prod] map[name:MAILER_URL value:...] map[name:APP_VERSION value:v0-0-3] map[name:APP_COMMIT_SHA value:...] ] d
I'm running a fairly resource-intensive service on a Kubernetes cluster to support CI activities. Only a single replica is needed, but it uses a lot of resources (16 cpu), and it's only needed during work hours generally (weekdays, 8am-6pm roughly). My cluster runs in a cloud and is setup with instance autoscaling, so if this service is scaled to zero, that
Compare suitability, operational responsibilities and limits before choosing this technology for a project. Which trade-offs should guide the decision?
I need to configure Ingress Nginx on azure k8s, and my question is if is possible to have ingress configured in one namespace et. ingress-nginx and some serivces in other namespace eg. resources? My files looks like so: # ingress-nginx.yaml apiVersion: extensions/v1beta1 kind: Deployment metadata: name: nginx-ingress-controller namespace: ingress-nginx spec:
Recovery needs to recreate the working service and its required data after a machine or process is lost. Which artifacts and state need protection, and how should the restore be checked?
I use Kubernetes which v1.19.7, when I run the CronJob sample apiVersion: batch/v1 kind: CronJob metadata: name: express-learn-cronjob spec: schedule: "*/1 * * * *" jobTemplate: spec: template: spec: containers: - name: hello image: busybox command: - /bin/sh - -c - date; echo Hello from the Kubernetes cluster restartPolicy: OnFailure get unable to recognize
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
I have read the docker documentation about restart policy of containers. However, I failed to understand the difference between on-failure and unless-stopped . When will I use one over the other? In which situations will a certain policy lead to starting a container and the other policy not?