gitlab Archives - Sergey Lysenko https://sergey-lysenko.com/tag/gitlab/ The DevOps Engineer Thu, 05 Feb 2026 16:37:06 +0000 en-US hourly 1 https://wordpress.org/?v=6.4.1 Kaniko Transitions to Chainguard: What It Means for CI/CD https://sergey-lysenko.com/kaniko-transitions-to-chainguard-what-it-means-for-ci-cd/ Fri, 03 Oct 2025 08:25:47 +0000 https://sergey-lysenko.com/?p=314 For years, Kaniko has been a go-to tool for building container images inside CI/CD pipelines, especially in environments where Docker isn’t available. However, active development on Kaniko by Google has now come to an end. The good news is that the project isn’t disappearing. Chainguard has stepped in, forking Kaniko and taking over its ongoing […]

The post Kaniko Transitions to Chainguard: What It Means for CI/CD appeared first on Sergey Lysenko.

]]> For years, Kaniko has been a go-to tool for building container images inside CI/CD pipelines, especially in environments where Docker isn’t available. However, active development on Kaniko by Google has now come to an end.

The good news is that the project isn’t disappearing. Chainguard has stepped in, forking Kaniko and taking over its ongoing development. This move ensures that the tool remains available and continues to evolve, with a strong focus on modern security practices and supply chain integrity — areas where Chainguard has already established deep expertise.

From a DevOps perspective, this transition raises some interesting points. On the one hand, it’s reassuring to see a community-driven fork keep a widely used tool alive. On the other hand, it highlights the fragility of relying on single-vendor projects, especially when they underpin critical workflows in CI/CD systems.

This shift also opens the door for teams to re-evaluate their image build strategy. Should they continue with Kaniko under Chainguard’s stewardship, or consider alternatives like BuildKit, Tekton, or other container-native solutions?

The post Kaniko Transitions to Chainguard: What It Means for CI/CD appeared first on Sergey Lysenko.

]]> Building Multi-Architecture Images with crane index append https://sergey-lysenko.com/building-multi-architecture-images-with-crane-index-append/ Thu, 02 Oct 2025 13:38:45 +0000 https://sergey-lysenko.com/?p=310 When working with containerized applications, it’s common to target multiple platforms such as amd64 and arm64. Instead of publishing separate tags for each architecture, you can create a multi-architecture manifest (also known as an image index). This allows tools like Docker or Kubernetes to automatically pull the correct image for the host architecture. One of […]

The post Building Multi-Architecture Images with crane index append appeared first on Sergey Lysenko.

]]> When working with containerized applications, it’s common to target multiple platforms such as amd64 and arm64. Instead of publishing separate tags for each architecture, you can create a multi-architecture manifest (also known as an image index). This allows tools like Docker or Kubernetes to automatically pull the correct image for the host architecture.

One of the simplest ways to achieve this is by using crane, a command-line tool from Google’s go-containerregistry project.

crane index append \
  -m reg.example.com/project/app:1.0.0-amd64 \
  -m reg.example.com/project/app:1.0.0-arm64 \
  -t reg.example.com/project/app:1.0.0 -v

Here’s what happens step by step:

1. Two platform-specific images already exist in the registry: one built for amd64, the other for arm64.
2. The -m flags specify the manifests to include in the new index.
3. The -t flag defines the final multi-arch tag (1.0.0 in this case).
4. The -v flag enables verbose output, useful for debugging.

After running this command, pulling reg.example.com/project/app:1.0.0 will automatically serve the correct architecture-specific image depending on the client’s platform.

Why This Matters

• Seamless developer experience: Users don’t need to worry about which tag matches their machine.
• Kubernetes compatibility: Clusters with mixed node types (x86 and ARM) can run the same deployment manifest.
• Future-proofing: ARM-based infrastructure is growing rapidly (e.g., AWS Graviton, Apple Silicon), so multi-arch support is becoming essential.

Final Thoughts

Using crane index append is a lightweight yet powerful way to unify platform-specific images under a single tag. It fits naturally into CI/CD pipelines and ensures your container images are portable, modern, and ready for diverse runtime environments.

The post Building Multi-Architecture Images with crane index append appeared first on Sergey Lysenko.

]]>