werf.io
Open in
urlscan Pro
54.38.250.137
Public Scan
Submitted URL: http://werf.io/
Effective URL: https://werf.io/
Submission: On October 21 via api from US — Scanned from FR
Effective URL: https://werf.io/
Submission: On October 21 via api from US — Scanned from FR
Form analysis
1 forms found in the DOMName: searchform — GET https://www.google.com/search
<form action="https://www.google.com/search" class="topsearch__form" method="get" name="searchform" target="_blank">
<input name="sitesearch" type="hidden" value="werf.io">
<input autocomplete="on" class="page__input topsearch__input" name="q" placeholder="Search the documentation" required="required" type="text">
<button type="submit" class="page__icon page__icon_search topsearch__btn"></button>
</form>
Text Content
* Documentation * Kubernetes guide * About * Publications * Release channels * Backward compatibility * Changelog * English * English * Русский * * * * * ✕ Join the party at CNCF Slack Step 1: Get an invite to CNCF Slack Step 2: Join #werf channel We've chosen CNCF Slack since most of the Kubernetes community members are there. Missing part of your CI/CD system 3783 werf is a Cloud Native Computing Foundation sandbox project * Ease of use Create your Dockerfile and Helm chart, and let werf handle all the rest * A single, all-in-one tool Build images, run tests, distribute release artifacts, and deploy the application to Kubernetes using a unified, all-in-one tool * Advanced features Take advantage of automatic caching, content-based tagging, resource tracking in Helm, and more * Gluing technologies Rely on Git, Buildah, Helm, Kubernetes, and your CI system of choice What werf brings to your CI/CD 1 Predictable and reliable delivery process * Deterministic CI/CD What you Git is what you get. werf introduces Giterminism that encourages an IaC approach and the use of Git as a single source of truth * Reproducible builds Synchronization with the container registry. Once built, the image is immutable, while builders use the container registry in a coordinated fashion * Predictable deployment A successful deployment means that an application is up and running Redeploying only the components that have been modified. Application image tags are independent (this solves the issue of image tagging in monorepos) * Easier troubleshooting Linking release artifacts to Git and CI/CD Instant and detailed feedback when deploying to Kubernetes 2 Efficiency * Incremental builds Rebuilding only the components that have been modified Reusing the existing layers found in the container registry * Deployment time Redeploying only the components that have been modified Instant termination of a troubled deployment process How it works * werf.yaml configVersion: 1 project: hello --- image: hello dockerfile: ./Dockerfile * Dockerfile FROM node WORKDIR /app COPY . . RUN npm ci CMD ["node", "server.js"] * .helm/templates/deployment.yaml apiVersion: apps/v1 kind: Deployment metadata: name: hello spec: selector: matchLabels: app: hello template: metadata: labels: app: hello spec: containers: - image: {{ .Values.werf.image.hello }} * build * test * deploy * distribute * cleanup * $ werf build --repo k3d-registry.sample-app.test:5000/sample-app Version: dev Using werf config render file: /tmp/werf-config-render-1156703103 ┌ ⛵ image app 00:04-00:27 Latest publications Learn more about tool's features and hands-on experience from new publications * Simple End to End GitOps with Werf 13-07-2023 * Werf: Pioneering the Future of CI/CD — A Close Look at the CNCF’s Noteworthy Addition to the DevOps Landscape 11-07-2023 * Why werf for CI/CD in Kubernetes? 15-06-2023 * New werf mode: combining werf & Argo CD into a unified CI/CD process 17-05-2023 Read more Friendly and rapidly growing community werf’s developers are always in contact with the community. You can reach us in Telegram, Twitter and GitHub Discussions. Telegram Twitter GitHub Discussions werf is a Cloud Native Computing Foundation sandbox project werf was originally created by Flant The Linux Foundation® (TLF) has registered trademarks and uses trademarks. For a list of TLF trademarks, see Trademark Usage. Site last generated: Oct 18, 2023 at 17:02 +0300