# Helm Published articles for Helm. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Running OpenBao on Kubernetes with a CloudNativePG PostgreSQL backend DevFeed: [Running OpenBao on Kubernetes with a CloudNativePG PostgreSQL backend]() Original publisher: [Read original article]() Author: Gabriele Bartolini (EnterpriseDB) and CNCF Ambassador, Rob Kenefeck (ControlPlane) Published: 2026-09-16T11:30:00Z Content type: tutorial Language: en Sources: [Cloud Native Computing Foundation]() Topics: [CloudNativePG](), [Kubernetes](), [PostgreSQL](), [Open Source](), [vendor lock-in]() Tags: [blog](), [cloudnativepg](), [docker](), [hashicorp-vault](), [helm](), [infrastructure](), [kubernetes](), [linux-foundation](), [open-source](), [postgresql](), [secrets](), [vendor-lock-in]() ### AI overview A tutorial describes deploying OpenBao on Kubernetes with a three-instance CloudNativePG PostgreSQL cluster as its storage backend. It explains certificate-based authentication and a local Kind-based test environment. ### Source excerpt Managing infrastructure secrets on Kubernetes needs a backend that is self-healing and free of vendor lock-in, and that is exactly what OpenBao (the Linux Foundation's open-source fork of HashiCorp Vault) and CloudNativePG give you: an entirely... ## Best Kubernetes Infrastructure as Code Tools in 2026 DevFeed: [Best Kubernetes Infrastructure as Code Tools in 2026]() Original publisher: [Read original article]() Author: Pulumi Content Team Published: 2026-08-14T00:00:00Z Content type: comparison Language: en Sources: [Pulumi]() Topics: [Infrastructure as code](), [Kubernetes](), [Terraform](), [argo-cd](), [Helm charts](), [GitOps](), [flux](), [opentofu](), [Amazon EKS](), [AWS CloudFormation](), [VPC](), [AWS IAM]() Tags: [argo-cd](), [cloudformation](), [code](), [comparisons](), [devops](), [flux](), [general](), [gitops](), [helm](), [helm-charts](), [iam](), [infrastructure](), [infrastructure-as-code](), [kubernetes](), [opentofu](), [platform-engineering](), [terraform](), [vpc]() ### AI overview This comparison explains that Kubernetes infrastructure as code spans cluster and cloud provisioning, in-cluster workload definition, and continuous delivery and reconciliation. It presents Pulumi and Terraform or OpenTofu as general-purpose provisioning options, Helm and Kustomize for workload templating, and Argo CD and Flux for GitOps reconciliation. ### Source excerpt There is no single best Kubernetes infrastructure as code tool, because "Kubernetes IaC" actually spans three different jobs. For provisioning the cluster and its cloud dependencies, Pulumi and Terraform (or OpenTofu) are the strongest general-purpose options. For templating and packaging workloads, Helm and Kustomize dominate. For continuous reconciliation once things are running, Argo CD and Flux lead the GitOps category. The right stack usually combines one tool from each layer, not a single tool that claims to do all three. What counts as infrastructure as code for Kubernetes? Kubernetes infrastructure as code work splits into three layers that get conflated constantly, and the confusion is where most tool comparisons go wrong. The cluster and cloud layer provisions the things Kubernetes itself sits on top of: the managed control plane (EKS, GKE, AKS), node pools, the VPC and subnets, IAM roles, load balancers, and cluster add-ons. Terraform, Pulumi, and cloud-native tools like CloudFormation operate here. The in-cluster workload layer defines what runs on the cluster once it exists: Deployments, Services, ConfigMaps, CustomResourceDefinitions, and the Helm charts or Kustomize overlays that template them. This is where Helm, Kustomize, and Crossplane's custom resources live. The delivery and reconciliation layer keeps what's declared in Git in sync with what's actually running on the cluster, continuously, rather than as a one-shot apply. Argo CD and Flux own this layer, and they consume the output of the other two rather than replacing them. Most real Kubernetes platforms use tools from at least two of these layers together. A team might provision EKS with Terraform, package its application with Helm, and let Argo CD reconcile it continuously. Knowing which layer a tool actually addresses, rather than treating "Kubernetes IaC" as one shopping list, is the first decision that matters. Pulumi provisions the cluster and the workloads on it in the same language Pul ## How to Automate Artifact Cleanup in Harness Artifact Registry Without Breaking Production DevFeed: [How to Automate Artifact Cleanup in Harness Artifact Registry Without Breaking Production]() Original publisher: [Read original article]() Author: Shibam Dhar Published: 2026-08-04T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [container images](), [Docker](), [Maven](), [npm](), [Helm charts](), [Python](), [CI/CD](), [sdlc](), [Microservice]() Tags: [ci-cd](), [cleanup](), [container-images](), [cost](), [deployment](), [docker](), [helm](), [npm](), [python](), [sdlc]() ### AI overview This hands-on walkthrough explains how Harness Artifact Registry lifecycle rules can automate cleanup across Docker, npm, Maven, Python, and Helm repositories while reducing the risk of deleting artifacts still used in production. It describes dry-run previews, governance tiers, recovery, and the limits of age-, count-, and tag-based rules. ### Source excerpt A hands-on walkthrough of Lifecycle Rules across Docker, npm, Maven, Python, and Helm. Includes dry-run preview, three-tier governance, and one-click recovery. | Blog ## How to scale GitOps in the enterprise: From single cluster to fleet management DevFeed: [How to scale GitOps in the enterprise: From single cluster to fleet management]() Original publisher: [Read original article]() Author: Artem Lajko Published: 2026-07-23T05:40:01Z Content type: tutorial Language: en Sources: [Platform Engineering Blog]() Topics: [GitOps](), [Tooling](), [Git](), [YAML](), [flux]() Tags: [complexity](), [config](), [deployment](), [developers](), [git](), [guide](), [helm](), [how-to](), [kubectl](), [learn](), [operational](), [platform](), [reconciliation](), [scale](), [secrets](), [secrets-management](), [workflow](), [workflows]() ### AI overview This guide explains how to scale GitOps from a single cluster to enterprise fleet management across 50 or more clusters. It focuses on architectural patterns, state store strategies, multi-cluster topology, secrets and policy management, configuration sprawl, repository performance, reconciliation delays, and the organizational discipline required for reliable operations. ### Source excerpt Learn how to scale GitOps from 1 to 50+ clusters using advanced state store patterns (OCI, ConfigHub), multi-cluster topology, and enterprise secrets/policy management ## wasmCloud 2.5.0: Wasmtime 46, WASI 0.3, and multiplexed WebAssembly host plugins DevFeed: [wasmCloud 2.5.0: Wasmtime 46, WASI 0.3, and multiplexed WebAssembly host plugins]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [WebAssembly](), [wasm](), [Streaming]() Tags: [helm](), [release](), [streaming](), [wasi](), [wasm](), [webassembly]() ### AI overview wasmCloud 2.5.0 is released with Wasmtime 46 and WASI 0.3 enabled by default. It adds configurable top-level WebAssembly proposals, multiplexed host-plugin interfaces, async-shaped and WIT improvements, Helm chart hardening, a host-controller refactor, and quality-of-life fixes. ### Source excerpt wasmCloud 2.5.0 ships with Wasmtime 46, WASI 0.3 on by default, configurable WebAssembly proposals, and `(implements ..)` multiplexing for host plugins. ## wasmCloud 2.4.0: HPA + KEDA autoscaling, multi-handler workloads, pluggable NATS DevFeed: [wasmCloud 2.4.0: HPA + KEDA autoscaling, multi-handler workloads, pluggable NATS]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-06-17T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [wasm](), [Kubernetes](), [autoscaling](), [Messaging](), [Security]() Tags: [autoscaling](), [handler](), [helm](), [kubernetes](), [messaging](), [net-11-preview-7](), [opentelemetry](), [prometheus](), [security](), [wasmcloud]() ### AI overview wasmCloud 2.4.0 adds Kubernetes-native autoscaling for Wasm workloads through HPA and KEDA, multi-handler messaging workflows, expanded Helm configuration, a redesigned host plugin API, and a Wasmtime 45.0.2 security update. ### Source excerpt wasmCloud 2.4.0 brings Kubernetes-native autoscaling for Wasm workloads via HPA and KEDA, multi-handler messaging in wash dev, a Helm chart NATS overhaul with split scheduler/data URLs, a NATS-backed operator liveness probe, and a Wasmtime 45.0.2 security bump. ## Temporal Helm Charts 1.0.0 reaches stability and requires externally provided databases and optional components DevFeed: [Temporal Helm Charts 1.0.0 reaches stability and requires externally provided databases and optional components]() Original publisher: [Read original article]() Author: Tom Wheeler Published: 2026-04-21T00:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [Helm charts](), [Kubernetes](), [configuration](), [Apache Cassandra](), [MySQL](), [PostgreSQL](), [elasticsearch](), [Grafana](), [Prometheus]() Tags: [cassandra](), [configuration](), [elasticsearch](), [grafana](), [helm](), [helm-charts](), [kubernetes](), [migrate](), [mysql](), [product-news](), [prometheus](), [stable]() ### AI overview Temporal's Helm Charts reached version 1.0.0 with a stable API and no expected breaking changes in subsequent releases in the series. The release removes bundled database and optional-component sub-charts, so users must provide those services and configure their connection details. ### Source excerpt Temporal's Helm Charts hit 1.0.0 with a stable API, streamlined architecture, and new configuration options. Learn what changed and how to migrate. ## Expanding Chainguard's Helm chart coverage and deepening user experiences DevFeed: [Expanding Chainguard's Helm chart coverage and deepening user experiences]() Original publisher: [Read original article]() Published: 2026-02-13T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Kubernetes](), [DevOps](), [container images](), [Security](), [SRE](), [Deployment](), [YAML]() Tags: [bitnami-alternative](), [bitnami-helm-charts](), [chainguard](), [chainguard-containers](), [chainguard-helm](), [chainguard-helm-charts](), [container-images](), [deployment](), [devops](), [helm](), [helm-charts](), [kubernetes](), [provenance](), [secure-by-default](), [secure-container-images](), [security](), [sre](), [yaml]() ### AI overview Chainguard is expanding its Helm chart catalog to include community charts and improve the user experience. The charts are designed to work with Chainguard container images, reducing manual YAML configuration, troubleshooting, provenance checks, and security risks in Kubernetes deployments. ### Source excerpt Chainguard's expanded Helm charts deliver signed, tested, secure-by-default deployments that eliminate YAML toil and simplify Kubernetes at scale. ## Tips for running Temporal on Kubernetes DevFeed: [Tips for running Temporal on Kubernetes]() Original publisher: [Read original article]() Author: Cubby Sivasithamparam Published: 2025-12-15T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Kubernetes](), [Helm charts](), [Deployment](), [autoscaling](), [Resilience](), [Latency]() Tags: [autoscaling](), [charts](), [deployment](), [helm](), [how-to](), [kubernetes](), [performance](), [practical](), [production](), [scaling](), [temporal](), [tips]() ### AI overview This article provides practical guidance for deploying and operating Temporal on Kubernetes. It explains how Temporal adds durable state persistence, retries, and recovery, and recommends using Helm charts with external production dependencies rather than bundled development configurations. ### Source excerpt Learn practical tips for deploying and scaling Temporal on Kubernetes. Covers Helm charts, KEDA autoscaling, and production performance tuning. ## Introducing New Updates to the Chainguard Images Directory DevFeed: [Introducing New Updates to the Chainguard Images Directory]() Original publisher: [Read original article]() Published: 2025-11-12T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [chainguard images](), [container images](), [Containers](), [Kubernetes](), [Deployment](), [Open Source]() Tags: [bitnami-helm-charts](), [chainguard](), [chainguard-catalog](), [chainguard-console](), [chainguard-containers](), [chainguard-helm-charts](), [chainguard-images](), [chainguard-images-directory](), [compare](), [container-images](), [containers](), [cost](), [cve](), [demo](), [deployment](), [helm](), [helm-charts](), [kubernetes](), [oci](), [registry](), [secure-by-design](), [updates](), [zero-cve-containers]() ### AI overview Chainguard has updated its Images Directory with an embedded ROI calculator, Helm Charts for Kubernetes deployments, and refreshed data about the Chainguard Factory. The calculator compares CVE counts and remediation costs, while the Helm Charts provide drop-in replacements for popular open source applications using Chainguard Containers and OCI delivery. ### Source excerpt We've improved the Chainguard Images Directory with Helm charts for faster deployments, an ROI calculator, and more refreshed data to improve your experience. ## Cluster Autoscaler on Rancher RKE2 DevFeed: [Cluster Autoscaler on Rancher RKE2]() Original publisher: [Read original article]() Author: Abhimanyu Saharan Published: 2025-09-06T00:00:00Z Content type: tutorial Language: en Sources: [Abhimanyu Saharan]() Topics: [rancher](), [Deployment]() Tags: [deployment](), [guide](), [helm](), [learn](), [rancher](), [zero-to-hero-rancher]() ### AI overview A step-by-step guide to setting up a cluster autoscaler on Rancher RKE2, including Helm deployment, scaling benefits, limitations, and troubleshooting. ### Source excerpt Step-by-step guide to RKE2 autoscaler setup with Rancher. Learn cluster autoscaler Helm deployment, scaling benefits, limits & troubleshooting. ## Helm Upgrade Failure: When Managed Fields Bite Back DevFeed: [Helm Upgrade Failure: When Managed Fields Bite Back]() Original publisher: [Read original article]() Author: Abhimanyu Saharan Published: 2025-08-20T00:00:00Z Content type: tutorial Language: en Sources: [Abhimanyu Saharan]() Topics: [Kubernetes]() Tags: [errors](), [helm](), [how-to](), [kubernetes](), [learn](), [upgrade]() ### AI overview This article explains how Kubernetes managedFields conflicts can cause Helm upgrades to fail even when the resource specification appears correct. ### Source excerpt Helm upgrade failed due to Kubernetes managedFields conflict. Learn why spec looked fine, yet patching caused errors, and how to fix it. ## Introducing First-Party Helm Charts for Chainguard Containers DevFeed: [Introducing First-Party Helm Charts for Chainguard Containers]() Original publisher: [Read original article]() Published: 2025-07-08T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [Helm charts](), [chainguard containers](), [Kubernetes](), [container images](), [Deployment]() Tags: [chainguard-containers](), [containers](), [deployment](), [helm](), [helm-charts](), [kubernetes](), [oci](), [open-source-software](), [release]() ### AI overview Chainguard announces the beta launch of first-party Helm Charts designed to work with its continuously updated container images. The charts aim to simplify Kubernetes deployment and management and are provided as OCI artifacts in customers' private registries. ### Source excerpt Chainguard first-party Helm Charts are designed to work seamlessly with our continuously updated container images. Discover more about our Helm Charts. ## Detect Deprecated Kubernetes APIs Before Upgrading DevFeed: [Detect Deprecated Kubernetes APIs Before Upgrading]() Original publisher: [Read original article]() Author: Abhimanyu Saharan Published: 2025-05-27T00:00:00Z Content type: tutorial Language: en Sources: [Abhimanyu Saharan]() Topics: [Kubernetes]() Tags: [apis](), [helm](), [helm-charts](), [kubernetes](), [upgrade]() ### AI overview A tutorial about using Pluto to detect deprecated or removed Kubernetes APIs in manifests and Helm charts before a cluster upgrade. ### Source excerpt Use Pluto to identify deprecated or removed Kubernetes APIs in your manifests and Helm charts before upgrading, ensuring smooth and predictable cluster upgrade. ## What is Koreo? DevFeed: [What is Koreo?]() Original publisher: [Read original article]() Published: 2025-05-08T15:12:33Z Content type: article Language: en Sources: [Brave New Geek]() Topics: [Kubernetes](), [Platform Engineering](), [configuration-management](), [Orchestration](), [Helm charts](), [VPC](), [Amazon Web Services]() Tags: [aws](), [configuration](), [configuration-management](), [controllers](), [devops](), [engineering](), [helm](), [helm-charts](), [iac](), [infrastructure-as-code](), [koreo](), [kubernetes](), [orchestration](), [platform-engineering](), [resource-orchestration](), [vpc]() ### AI overview This article explains Koreo, an open-source platform engineering toolkit for Kubernetes. It describes Koreo's approach to Kubernetes configuration management and resource orchestration, and compares it with Helm and Kustomize, including their limitations for complex or dependent deployments. ### Source excerpt The platform engineering toolkit for Kubernetes Last month we open sourced Koreo, our "platform engineering toolkit for Kubernetes." Since then, we've seen a lot of interest from folks in the platform engineering and DevOps space. We've also gotten a lot of questions from people trying to better understand how Koreo fits into an already crowded landscape of Kubernetes tools. Koreo is a fairly complex tool, so it can be difficult to quickly grasp just what exactly it is_,_ what problems it's designed to solve, and how it compares to other, similar tools. In this post, I want to dive into these topics and also discuss the original motivation behind Koreo. ## New Chainguard Images December 2024: Adoptium, AWX, CouchDB DevFeed: [New Chainguard Images December 2024: Adoptium, AWX, CouchDB]() Original publisher: [Read original article]() Published: 2025-01-16T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [Adoptium](), [openjdk](), [Ansible](), [Java](), [NoSQL](), [Open Source](), [Erlang](), [.NET MAUI](), [Process]() Tags: [adoptium](), [ansible](), [apache](), [awx](), [chainguard](), [chainguard-images](), [container-images](), [couchdb](), [erlang](), [helm](), [java](), [jdk](), [linkerd](), [net-11](), [nosql](), [open-source](), [opentofu]() ### AI overview Chainguard describes its December 2024 batch of 39 new Chainguard Images, highlighting images for Adoptium, AWX, and Apache CouchDB. The article notes FIPS-enabled variants and summarizes the intended uses and image characteristics. ### Source excerpt Chainguard released several new images in December 2024, including images for Adoptium, AWX, CouchDB, and others. Check out the full list. ## Automating Keycloak Deployments for Fun and Profit DevFeed: [Automating Keycloak Deployments for Fun and Profit]() Original publisher: [Read original article]() Author: brakmic Published: 2024-12-24T22:31:29Z Content type: tutorial Language: en Sources: [Harris Brakmic - Coding]() Topics: [Deployment](), [Kubernetes](), [Helm charts](), [Docker](), [DevOps](), [Testing](), [PostgreSQL](), [sealed secrets](), [kubectl](), [Debian]() Tags: [bash](), [build](), [coding](), [debian](), [deployment](), [devops](), [docker](), [examples](), [ha](), [helm](), [helm-charts](), [high-availability](), [iam](), [java](), [keycloak](), [kubectl](), [kubernetes](), [nginx](), [postgresql](), [sealed-secrets](), [testing]() ### AI overview A practical tutorial for automating a local Keycloak deployment designed to resemble a production environment. It uses Certificate Manager, Sealed Secrets, PostgreSQL high availability, and provides both a Bash script and Helm charts for redeployment. ### Source excerpt This article will be a practical one as I intend to showcase a fully automated setup of Keycloak for local testing. However, unlike so many examples out there, this article aims to deploy a production-level Keycloak deployment that uses a Certificate Manager, Sealed Secrets, and PostgreSQL HA (high-availability variant). The goal is to create a [...] ## Blog: Falco Talon v0.2.0 DevFeed: [Blog: Falco Talon v0.2.0]() Original publisher: [Read original article]() Published: 2024-11-27T00:00:00Z Content type: release Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [Google Cloud Platform (GCP)](), [Kubernetes](), [Cloud]() Tags: [announce](), [authentication](), [authorization](), [blog](), [falco](), [gcp](), [google-cloud](), [helm](), [kubernetes](), [release](), [talon]() ### AI overview Falco Talon 0.2.0 is a minor release adding GCP function actions, Google Cloud Storage output, new Kubernetes action parameters, a smaller tcpdump action image, and a fix that removes the requirement for an existing config.yaml file when checking rule syntax. ### Source excerpt Today we announce the release of Falco Talon 0.2.0 🦅! Falco Talon 0.2.0 is a minor release that includes new actionners and outputs, add parameters to existing actionners, along one small fix on the check and print commands. Features Add gcp:function actionner: Now users can call GCP function to automate GCP tasks, with authentication and authorization out of the box. - action: Invoke GCP function actionner: gcp:function additional_contexts: - aws parameters: gcp_function_name: simple-http-function gcp_function_location: us-central1 Add gcp:gcs output Now users can send output directly to GCP Google Cloud Storage, same way as s3 and minio existing outputs. Add ignore_standalone_pods parameter for kubernetes:terminate actionner Allow to wait until the completion of kubernetes:drain by configuring max_wait_period and wait_period_excluded_namespaces Use smaller image for the kubernetes:tcpdump actionner Fixes An existing config.yaml file is not required anymore to check the syntax of your rules files. Try it! 🏎 In case you just want to try out the Falco Talon 0.2.0, you can install the helm chart following the instructions on the documentation Let's meet 🤝 We meet every Wednesday in our community calls, if you want to know the latest and the greatest, you should join us there! If you have any questions Join the #falco channel on the Kubernetes Slack Join the Falco mailing list Thanks to all the amazing contributors! Enjoy 😎, Igor ## Blog: How to Deploy Falco with k8s-metacollector + k8smeta Plugin DevFeed: [Blog: How to Deploy Falco with k8s-metacollector + k8smeta Plugin]() Original publisher: [Read original article]() Published: 2024-10-14T00:00:00Z Content type: tutorial Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [Kubernetes](), [container-security](), [Security](), [Deployment](), [Kubernetes clusters](), [monitor]() Tags: [clusters](), [container-security](), [deployment](), [enrichment](), [falco](), [helm](), [k8s-metacollector](), [k8smeta](), [kubernetes](), [monitor](), [plugin](), [security](), [tutorial]() ### AI overview This tutorial explains how to deploy Falco with the k8s-metacollector and k8smeta plugin on Kubernetes. It shows how these components add Kubernetes metadata such as pod names, namespaces, and deployment details to Falco security alerts, and how Falco's append_output feature can add extra metadata fields without modifying rules. ### Source excerpt In today's cloud-native world, securing Kubernetes environments has become increasingly critical as containerized workloads gain complexity. Falco is designed to monitor and detect anomalous activities in Kubernetes clusters and container environments. By continuously observing system calls and enriching event data with metadata, Falco ensures that any suspicious behavior is detected in real-time, protecting against threats like privilege escalations, file tampering, and network anomalies. In this tutorial, we will guide you through deploying Falco with two powerful components: k8s-metacollector and the k8smeta plugin. These tools significantly enhance Falco's security event detection by adding important Kubernetes context, such as pod names, namespaces, deployment details, to the alerts. Additionally, we will explore how to leverage the new append_output feature introduced in Falco version 0.39.0. This feature allows you to append extra metadata fields to Falco's output, without the need to modify your rules. By the end of this guide, you will have a Falco setup capable of detecting security issues in Kubernetes with enriched metadata output, ensuring you get a complete picture of your cluster's security posture. Whether you're an experienced Kubernetes administrator or just starting to explore container security, this guide will help you make the most of Falco's capabilities in a Kubernetes environment. What You'll Learn: The purpose and benefits of using the k8s-metacollector and k8smeta plugin to enrich Falco alerts with Kubernetes-specific data. How to deploy Falco with the k8smeta plugin on a Kubernetes cluster. How to configure and use the append_output feature to enhance Falco alerts with additional metadata fields. Prerequisites: A working Kubernetes cluster and some familiarity with Kubernetes concepts. Basic knowledge of Falco and how it works. Helm installed on your system (for easy deployment of Falco). Let's dive in and set up a Falco deployment that w ## A Kubernetes operator for Trino? DevFeed: [A Kubernetes operator for Trino?]() Original publisher: [Read original article]() Author: Manfred Moser, Martin Traverso Published: 2024-10-10T00:00:00Z Content type: article Language: en Sources: [Trino Blog]() Topics: [Kubernetes](), [Containers](), [Cloud](), [hosting]() Tags: [cloud](), [community](), [containers](), [helm](), [hosting](), [images](), [kubernetes](), [open-source](), [operator](), [servers](), [slack]() ### AI overview The article discusses the proposal for a Kubernetes operator for Trino. It reviews existing internal and open-source operator efforts, suggests combining them into a modular operator aligned with Trino and potentially compatible with Trino Gateway, and invites contributors to discuss implementation and maintenance questions. ### Source excerpt Trino is deployed everywhere - on-premise, in private data centers, in the cloud with hosting providers, on bare metal servers, on virtual machines, and with containers. With all these options for deployments, a Kubernetes-based platform with a container emerged as the most widely used approach. The Trino project caters for this usage with our container images for every release and our Helm chart. However we keep hearing from people who want to use a Kubernetes operator... ## Chainguard Releases 58 New Container Images in March 2024 DevFeed: [Chainguard Releases 58 New Container Images in March 2024]() Original publisher: [Read original article]() Published: 2024-04-04T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [container images](), [supply-chain-security](), [Security](), [Kubernetes](), [.NET](), [VLC]() Tags: [chainguard](), [chainguard-images](), [conda](), [container-images](), [fips-compliance](), [helm](), [kubernetes](), [kyverno](), [net](), [security](), [software-supply-chain](), [velero]() ### AI overview Chainguard released 58 new container images in March 2024, including publicly available images for Velero and .NET. The article highlights FIPS compliance, smaller image size for Velero, daily builds from source, and performance optimizations for .NET images. ### Source excerpt Discover the latest Chainguard Images in March 2024, offering unparalleled security with low-to-zero CVEs for fortified software supply chain. ## Blog: Track the Bitcoin transactions with Falco DevFeed: [Blog: Track the Bitcoin transactions with Falco]() Original publisher: [Read original article]() Published: 2024-03-13T00:00:00Z Content type: tutorial Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [Bitcoin](), [WebSocket](), [Blockchain](), [Monitoring]() Tags: [bitcoin](), [falco](), [helm](), [kubernetes](), [plugin](), [websocket]() ### AI overview This tutorial presents a Falco plugin that receives Bitcoin transactions from a public WebSocket stream and shows how to install it, configure its default rules, and monitor transaction events in real time. ### Source excerpt The number of plugins available for Falco continues to grow thanks to our wonderful community. Thank you all for your help! You can find the list of available plugins here. The vast majority of plugins developed allow Falco to ingest logs from different sources and raise alerts when suspicious elements are identified by its rules. In order to show that any event stream can be a source if you have the right plugin, and to have something fun to show users during my talks, I developed a Falco plugin to track Bitcoin transactions. How does it work? I discovered the site https://www.blockchain.com/ exposes a public flux, accessible via a websocket, by subscribing to it you can retrieve transactions carried out on the blockchain in real time. This is perfect for a Falco plugin as it allows you to test the ingestion of events via a websocket, and serve as a basis for other plugins. I am not going to describe the internal workings of the plugin here, nor how it was developed. If you are interested, you can look at the code here. Alternatively, read our documentation explaining how to create a plugin from A to Z: https://falco.org/docs/concepts/plugins/developers-guide/how-to-develop/. Default rules The plugin comes with its default set of rules, we will use them as a working example. You are free to play with it for your own needs, such as monitoring suspicious movements of your wallet. You can find the Falco rules file provided here. Installation of the plugin We will see the 3 classic ways to install the plugin: via sources with falcoctl in kubernetes via Helm Via sources The prerequisites are: Golang >= 1.19 make Falco >= 0.36 Git We will start by installing download the sources, build and install the plugin: git clone https://github.com/Issif/bitcoin-plugin.git cd bitcoin-plugin sudo make install We will create a falco.yaml file containing: plugins: - name: bitcoin library_path: /usr/share/falco/plugins/libbitcoin.so init_config: '' open_params: '' load_plugins: [bitcoi ## Keep your Chainguard Images up to date with digestabot DevFeed: [Keep your Chainguard Images up to date with digestabot]() Original publisher: [Read original article]() Published: 2023-12-18T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [chainguard](), [GitHub Actions](), [Pull Request](), [Security]() Tags: [also](), [chainguard](), [chainguard-images](), [container](), [continuous-integration](), [digestabot](), [dockerfiles](), [github-action](), [helm](), [make](), [merge](), [oidc](), [security](), [vulnerability-automation](), [vulnerability-management]() ### AI overview Chainguard's digestabot is a free GitHub Action that helps keep Chainguard Images and other container assets current. It detects outdated image digests, opens pull requests, and supports testing and secure updates through continuous integration and optional ephemeral OIDC tokens. ### Source excerpt Experience hassle-free updates with Chainguard's digestabot, ensuring your Images stay secure and up-to-date daily. ## The incremental path to container images: Chainguard Images DevFeed: [The incremental path to container images: Chainguard Images]() Original publisher: [Read original article]() Published: 2023-11-28T00:00:00Z Content type: tutorial Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [container images](), [Vulnerabilities](), [Kubernetes](), [vulnerability management](), [Exploit]() Tags: [alpine](), [apk](), [chainguard-images](), [container-image](), [container-images](), [distroless-containers](), [hardened-images](), [helm](), [kubernetes](), [kyverno](), [prometheus](), [sigstore](), [vulnerabilities]() ### AI overview This article explains an incremental approach to migrating existing container images to Chainguard Images. It recommends starting with hardened Application Images that can often be adopted as drop-in replacements, then progressing toward Base Images. ### Source excerpt Explore how easy it is to migrate existing container images to Chainguard Images, whether you are adopting Application Images or Base Images. [Next page]()