Package manager support: RPM

[craigbox]

Support at least yum and zypper installations by building an RPM package with every Kubescape release and updating package indexes.

[HollowMan6]

Package installation should now be available already with dnf/zypper (according to the guides here):

zypper addrepo https://download.opensuse.org/repositories/home:kubescape/openSUSE_Tumbleweed/home:kubescape.repo
zypper refresh
zypper install kubescape

dnf config-manager --add-repo https://download.opensuse.org/repositories/home:kubescape/Fedora_37/home:kubescape.repo
dnf install kubescape

(yum actually has been superseded by dnf)

[craigbox]

Great! The end state should be a public project called 'kubescape', taking binaries that come from our release pipeline and automatically updating them when we do a release.

(Then we can look at SLSA compliance too 😁)

I suggest that you create some pages on the GitHub wiki that explain how the build pipeline works, from release through OpenSUSE and then to a user's installation.

kubescape.spec should be in this repo and synced to the build service if possible.

[HollowMan6]

Hi @craigbox ! Yeah, we can create an account with the user name kubescape as the org account (I wonder if the org admin would like to help create this account, as I guess it requires some email verification) https://idp-portal.suse.com/univention/self-service/#page=createaccount

After we have the account, I will begin transfering the package located in my project to the org project (https://build.opensuse.org/package/show/home:hollowman/kubescape -> https://build.opensuse.org/package/show/home:kubescape/kubescape)

In addition, as you mentioned "kubescape.spec should be in this repo", I'm actually open to two options that whether to merge everything at https://github.com/HollowMan6/kubescape-deb-rpm into this kubescape main repo, or just keep it in a separate repo just like the homebrew tap one. If it's the former one, I can help submit a PR, and if it's the later, I can help transfer that repo into the kubescape org.

For SLSA compliance, I think the build process now is at least SLSA 2 and maybe already SLSA 3 compliant, as it's fully scripted and can synced to the open build service automatically with the help of the CI here: https://github.com/HollowMan6/kubescape-deb-rpm/actions/runs/4402322353

After everything above have settled down, I will create some pages on the GitHub wiki to explain how the build pipeline works, from release through OpenSUSE and then to a user's installation.

[craigbox]

I've registered an account named kubescape and I'm awaiting guidance from someone at SUSE as to how I can use this account without home: as a prefix.

[HollowMan6]

GitHub wiki is now ready to explain how the build pipeline works, from release through OpenSUSE and then to a user's installation.

• https://github.com/kubescape/kubescape/wiki/Publishing
• https://github.com/kubescape/kubescape/wiki/Installation

[craigbox]

great: lets get the packaging repo under kubescape and we can close this out!

[HollowMan6]

@craigbox Just like #1143 , I think we can close this as well.

[craigbox]

Tested OK with Fedora 37 and 38 images.