Upstream software project

gitopper

Gitops for non-Kubernetes folks

About gitopper

Gitops for non-Kubernetes folks

This project links 1 native package record across 1 recorded operating-system release. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

gitopper repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.gitopper: recorded package coverageopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
gitopper
Publisher
Not authoritatively mapped
Native package records
1
Operating systems
opensuse-tumbleweed
License expression
Apache-2.0
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Gitopper is GitOps for non-Kubernetes folks it watches a remote git repo, pulls changes and HUP the server (service) process. A sparse (but with full history) git checkout will be done, so each service will only see the files it will actually need. Several bind mounts are then setup to give the service access to the file(s) in Git. If the target directories don't exist, they will be created, with the current user - if specified. This tool does little more than just pull the repo, but the little it brings to the table allows for a GitOps workflow without resorting to Kubernetes like environments. The Git repository that you are using to provision the services must have at least one (sub)directory for each service. Gitopper will install packages if told to do so. It will not upgrade or downgrade them, assuming there is a better way of doing those. The remote interface of gitopper uses SSH keys for authentication, this hopefully helps to fit in, in a sysadmin organisation. The following features are implemented: * Metrics: are included see below, they export a Git hash, so a rollout can be tracked. * Diff detection: possible using the metrics or gitopperctl. * Out of band rollbacks: use gitopperctl to bypass the normal Git workflow. * No client side processing: files are used as they are in the Git repo. * Canarying: give a service a different branch to check out.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

openSUSE Tumbleweed

  1. Package gitopper

    tumbleweed (openSUSE Tumbleweed) (Unspecified): Gitops for non-Kubernetes folks

    0.0.20-1.9: x86_64

    Source: gitopper

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.