Bookmarks with tag "devops", page 5 of 7
A Job creates one or more Pods and will continue to retry execution of the Pods until a specified number of them successfully terminate. As pods successfully complete, the Job tracks the successful completions. When a specified number of successful completions is reached, the task (ie, Job) is complete. Deleting a Job will clean up the Pods it created. Suspending a Job will delete its active Pods until the Job is resumed again.
The lazier way to manage everything docker.
Install the sidecar agent for detailed metric visualizations on Kubernetes objects, like deployment progress for pods, DaemonSets, and StatefulSets.
Documentation for GitLab Community Edition, GitLab Enterprise Edition, Omnibus GitLab, and GitLab Runner.
In this tutorial, learn how to set up and secure an Nginx Ingress Controller with Cert-Manager on DigitalOcean Kubernetes.
Documentation for GitLab Community Edition, GitLab Enterprise Edition, Omnibus GitLab, and GitLab Runner.
Hints, tips and guidelines for writing clean, reliable Dockerfiles
The right way to do templating in Kubernetes
Having an automated deployment process is a requirement for a scalable and resilient application, and it’s especially important to apply CI/CD concepts to Ku…
AWS announced Kubernetes-as-a-Service at re:Invent in November 2017: Elastic Container Service for Kubernetes (EKS). Since ye...
FEATURE STATE: Kubernetes v1.21 [stable] A CronJob creates Jobs on a repeating schedule. CronJob is meant for performing regular scheduled actions such as backups, report generation, and so on. One CronJob object is like one line of a crontab (cron table) file on a Unix system. It runs a job periodically on a given schedule, written in Cron format. CronJobs have limitations and idiosyncrasies. For example, in certain circumstances, a single CronJob can create multiple concurrent Jobs.
High Performance Telemetry Agent for Logs, Metrics and Traces
Fluent Bit Kubernetes Daemonset.