SHA256
1
0
forked from pool/kubeseal
kubeseal/kubeseal.spec

58 lines
1.8 KiB
RPMSpec
Raw Permalink Normal View History

#
# spec file for package kubeseal
#
# Copyright (c) 2024 SUSE LLC
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.
# Please submit bugfixes or comments via https://bugs.opensuse.org/
#
%define __arch_install_post export NO_BRP_STRIP_DEBUG=true
%define archive_name sealed-secrets
Name: kubeseal
Version: 0.27.1
Release: 0
Summary: CLI for encrypting secrets to SealedSecrets
License: Apache-2.0
URL: https://github.com/bitnami-labs/sealed-secrets
Source: %{archive_name}-%{version}.tar.gz
Source1: vendor.tar.gz
BuildRequires: go >= 1.22
%description
Problem: "I can manage all my K8s config in git, except Secrets."
Solution: Encrypt your Secret into a SealedSecret, which is safe to store - even to a public repository. The SealedSecret can be decrypted only by the controller running in the target cluster and nobody else (not even the original author) is able to obtain the original Secret from the SealedSecret.
%prep
%autosetup -p 1 -a 1 -n %{archive_name}-%{version}
%build
go build \
-mod=vendor \
-buildmode=pie \
-ldflags="-X main.VERSION=%{version}" \
-o bin/kubeseal ./cmd/kubeseal
%install
# Install the binary.
install -D -m 0755 bin/%{name} "%{buildroot}/%{_bindir}/%{name}"
%files
%doc README.md
%license LICENSE
%{_bindir}/%{name}
%changelog