kubeshark: 41.3 -> 41.6

[r-ryantm]

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

meta.description for kubeshark is: The API Traffic Viewer for Kubernetes

meta.homepage for kubeshark is: https://kubeshark.co/

meta.changelog for kubeshark is: https://github.com/kubeshark/kubeshark/releases/tag/41.6

Updates performed

• Ran passthru.UpdateScript

To inspect upstream changes

• Release on GitHub

• Compare changes on GitHub

Impact

Checks done (click to expand)

---

• built on NixOS
• The tests defined in passthru.tests, if any, passed
• found 41.6 with grep in /nix/store/nz2a7hw3frvpjn59nyxpr6wjwhi72vhy-kubeshark-41.6
• found 41.6 in filename of file in /nix/store/nz2a7hw3frvpjn59nyxpr6wjwhi72vhy-kubeshark-41.6

---

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
kubeshark

Instructions to test this update (click to expand)

---

Either download from Cachix:

nix-store -r /nix/store/nz2a7hw3frvpjn59nyxpr6wjwhi72vhy-kubeshark-41.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.

Or, build yourself:

nix-build -A kubeshark https://github.com/r-ryantm/nixpkgs/archive/fc5ec9004e7cfc7c9a6648d1af4be03700443566.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/nz2a7hw3frvpjn59nyxpr6wjwhi72vhy-kubeshark-41.6
ls -la /nix/store/nz2a7hw3frvpjn59nyxpr6wjwhi72vhy-kubeshark-41.6/bin

---

Pre-merge build results

We have automatically built all packages that will get rebuilt due to
this change.

This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.

Result of nixpkgs-review run on x86_64-linux 1

1 package built:

• kubeshark

---

Maintainer pings

cc @bryanasdev000 @qjoly for testing.

[qjoly]

➜  bin ./kubeshark version
41.6
➜  bin ./kubeshark tap    
2023-08-01T11:23:01+02:00 INF tapRunner.go:50 > Using Docker: registry=docker.io/kubeshark/ tag=latest
2023-08-01T11:23:01+02:00 WRN tapRunner.go:61 > Storage limit cannot be modified while persistentstorage is set to false!
2023-08-01T11:23:01+02:00 INF tapRunner.go:66 > Kubeshark will store the traffic up to a limit (per node). Oldest TCP/UDP streams will be removed once the limit is reached. limit=200Mi
2023-08-01T11:23:01+02:00 INF versionCheck.go:23 > Checking for a newer version...
2023-08-01T11:23:01+02:00 INF common.go:69 > Using kubeconfig: path=/home/kiko/.kube/config
2023-08-01T11:23:01+02:00 INF tapRunner.go:80 > Targeting pods in: namespaces=[""]
...

Waiting for ofborg, but changes and binary LGTM