Argocd Deployment Testing with Kubechecks

✨ Best Self-Hosted Tools for Developers in 2026 Discover the best self-hosted tools for developers, including Git, CI/CD, Docker, monitoring, and deployment platforms. Git Hosting: Gitea or GitLab Self-Managed CI/CD: Built-in Git CI or Argo CD Deployment: Coolify Container Registry: Harbor Observability: Prometheus + Grafana + Loki + OpenTelemetry Authentication: authentik Documentation: BookStack Developer Portal: Backstage Backend Platform: Supabase https://lnkd.in/gCkVzCVq

Running container scans one image at a time? That doesn't scale. Most real-world projects don't ship a single container, they ship several. And scanning them sequentially slows down your pipeline and delays feedback. GitLab multi-container scanning lets you scan all your images in parallel from a single config file. Define your targets, push your changes, and let the pipeline handle the rest. In this video, I walk through how to set it up and what it looks like in action. 🎥 https://lnkd.in/gGithg_i #DevSecOps #ContainerSecurity #GitLab #AppSec #CloudNative

Deploying with Deployer and GitLab Pipelines This post explains how to set up a deployment workflow for a project using Deployer and GitLab Pipelines, including steps to build a new release, package it, and deploy it to a server via SSH. The article outlines creating a custom Docker image, configuring SSH access, and defining a .gitlab-ci.yml file to automate the deployment process. It serves as a guide for developers looking to implement similar workflows. https://lnkd.in/eXf6ug_j

Deploying with Deployer and GitLab Pipelines This post explains how to set up a deployment workflow for a project using Deployer and GitLab Pipelines, including steps to build a new release, package it, and deploy it to a server via SSH. The article outlines creating a custom Docker image, configuring SSH access, and defining a .gitlab-ci.yml file to automate the deployment process. It serves as a guide for developers looking to implement similar workflows. https://lnkd.in/eXf6ug_j

GitOps changed how we deploy to Kubernetes. Instead of running kubectl commands manually, we now commit YAML to Git and ArgoCD handles the rest. Every deployment is versioned, auditable, and reversible. Here is our production setup: ArgoCD watches our Gitea repo. On every push to main, it compares desired state vs actual state. If they differ, it syncs automatically. Benefits we have seen: - Zero-downtime deployments

GitOps changed how we deploy to Kubernetes. Instead of running kubectl commands manually, we now commit YAML to Git and ArgoCD handles the rest. Every deployment is versioned, auditable, and reversible. Here is our production setup: ArgoCD watches our Gitea repo. On every push to main, it compares desired state vs actual state. If they differ, it syncs automatically. Benefits we have seen: - Zero-downtime deployments

Manual deployment = risky deployment. In this part, we build a CI pipeline using GitHub Actions: Push → Build Docker images → Push to registry Automated builds change everything. 🔗 Read here: https://lnkd.in/d9Q6DzFW

Claude can fix bugs by itself In one of the newer versions, there is Slack MCP shipped with Claude Code. Connect it to your account, paste the Slack message, and tell Claude to fix the issue. Or, if you have CI issues, on the other hand, connect with your CI. At TradeLocker, we use GitLab and the `glab` CLI can fetch pipeline logs. Simply paste the pipeline link and observe the magic.

GitHub Actions vs GitLab CI/CD: Complete CI/CD Comparison (2026) Created by 楊東霖 Choosing the right CI/CD platform is one of the highest-leverage decisions a development team makes. It shapes how you test, build, and ship software every single day. In 2026, the two dominant platforms — GitHub Actions and GitLab CI/CD — have both matured into powerful, production-ready systems... link https://lnkd.in/eqsbxntm pubDate Fri, 20 Mar 2026 03:52:03 +0000

Just completed Claude Code in Action by Anthropic — and honestly, this one changed how I think about development! 🚀 Here's what I learned: 🪝 Hooks — Automatic triggers that run your scripts at specific moments in Claude's workflow. For example, auto-running your linter or tests every time Claude edits a file — without you doing anything manually. ⚙️ MCP Servers (Model Context Protocol) — Connecting Claude Code to external tools and services so it can interact with real APIs, databases, and systems beyond just your codebase. 💻 Custom Commands — Building reusable slash commands so Claude handles repetitive tasks your way, every time. 🔗 GitHub Integration — Delegating real development tasks to Claude directly through GitHub workflows. #AnthropicAI #ClaudeCode #SDET #QAEngineer #AITools #Automation #MCP #DevTools #LearningEveryDay