Update all tools

Updates requested from BigBang to match the latest available in BB 1.25.0:

• Flux -> 0.24.0 (will be in BB 1.26.0)
• Istio -> 1.11.3
• Argo -> 2.1.7

Plus latest for:

• Helm -> 3.7.2
• Kubectl -> 1.23.1
• YQ -> 4.16.2
• Sops -> 3.7.1
• SopsSecretGenerator -> 1.4.0
• k9s -> 0.25.18
• Kustomize -> 4.4.1
• Stern -> 1.21.0 (different upstream used)

Removed older (unused) tooling:

• Popeye
• ClusterLint
• Polaris
• Kube-Linter

For #7 (closed)

assigned to @micah.nagel

mentioned in merge request !31 (closed)

added 1 commit

• 89a0df1a - Fix mis-copied sha, switch to semver 1.0.0

Compare with previous version

@micah.nagel Do you have access to VAT? Can you please justify the new High finding: https://vat.dso.mil/vat/container/17560?branch=bb-base-tool-update

A nil pointer dereference in the golang.org/x/crypto/ssh component through v0.0.0-20201203163018-be400aefbc4c for Go allows remote attackers to cause a denial of service against SSH servers.

I recommend marking it mitigated with the note that BB does not host an SSH server from this container.

Container Hardening Team

This merge request has been identified as not having an associated Gitlab issue.

In order to better facilitate you, we ask that you open up a Gitlab issue within the corresponding project using the appropriate issue template. See below for a list of issue types.

Issue types:

• Application - Initial - Use this template if the container has never been approved.
• Application - Update - Use this template if the container was previously approved, but is being updated to a newer version.
• New Findings - Use this template if the container has not been updated but continuous monitoring has discovered new findings.
• Bug - Use this template for any approved container that has identifed a bug and/or potential fixes.
• Feature - Use this template for any approved container that is receiving a feature enhancement such as turning a feature on, not a version update.

Once you have created the issue, you must relate the merge request to the issue. You can do this by:

• Editing the merge request, and typing the # character and then either type the issue number or select the issue from the list.
• Do not prefix the # character with anything, it should start on a line by itself. Particularly, do not use closes # as the Gitlab issue may live on after this merge request has been resolved.

Note: Do not relate the merge request and issue any other way as those relationships will not be detected and this reminder will continue.

A reminder from the Container Hardening Team to create your related issue as detailed in previous comments.

changed the description

added 1 commit

• c26db5f4 - Update other tools

Compare with previous version

changed the description

added 1 commit

• e7b01c5a - Fix Polaris URL

Compare with previous version

added 1 commit

• b7303ac6 - Remove unnecessary tooling

Compare with previous version

added 1 commit

• ea1dbcc5 - Switch upstream stern

Compare with previous version

changed the description

added 1 commit

• a4a3f93f - Remove deprecated from dockerfile

Compare with previous version

changed the description

changed title from Update flux, istio, argo, helm to Update all tools

resolved all threads

mentioned in commit d776c4f1

merged