chore: fixed vulns - bump Go version

[khulnasoft-bot]

Addresses issue: #

Changes proposed in this pull request:

• Change 1
• Change 2
• Change 3

Summary by Sourcery

Update the project to support K3s CIS benchmark version 1.8, including new configuration files for various components. Fix issues with AWS Security Finding publish results. Update Go version and dependencies, and improve audit commands for better log retrieval.

New Features:

• Introduce a new CIS benchmark version 1.8 for K3s, including configuration files for master, node, etcd, control plane, and policies.

Bug Fixes:

• Fix the handling of AWS Security Finding publish results by correctly dereferencing pointers for FailedCount and SuccessCount.

Enhancements:

• Update Go version to 1.22.7 in build and release workflows.
• Update dependencies in go.mod, including AWS SDK, testify, and others, to newer versions.
• Improve audit commands in various configuration files to use journalctl with the -m flag for better log retrieval.

Build:

• Bump Go version to 1.22 in the go.mod file.

CI:

• Update Go version to 1.22.7 in GitHub Actions workflows for build and release.

Chores:

• Remove unnecessary entries from the configuration files, such as redundant kubeconfig paths.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the K3s CIS benchmark configuration and checks to align with version 1.8 of the benchmark. It includes changes to various configuration files, updates Go dependencies, and adjusts audit and remediation steps for multiple security checks across different components of K3s.

Class diagram for updated K3s CIS benchmark configuration

classDiagram
    class Master {
        -containerd[] bins
        -/var/lib/rancher/k3s/server/cred/scheduler.kubeconfig kubeconfig
    }
    class ControllerManager {
        -containerd[] bins
        -/var/lib/rancher/k3s/server/cred/controller.kubeconfig kubeconfig
    }
    class Etcd {
        -containerd[] bins
        -/var/lib/rancher/k3s/server/db/etcd/config confs
    }
    class Node {
        -kubelet, proxy components
    }
    class Kubelet {
        -containerd[] bins
        -/var/lib/rancher/k3s/agent/kubelet.kubeconfig defaultkubeconfig
        -/var/lib/rancher/k3s/agent/client-ca.crt defaultcafile
    }
    class Proxy {
        -containerd[] bins
        -/var/lib/rancher/k3s/agent/kubeproxy.kubeconfig defaultkubeconfig
    }
    class Policies {
        -policies components
    }
    Master --> ControllerManager
    Master --> Etcd
    Master --> Node
    Node --> Kubelet
    Node --> Proxy
    Node --> Policies

Loading

File-Level Changes

Change	Details	Files
Added new configuration files for K3s CIS 1.8 benchmark	Added master.yaml for control plane security configuration Added node.yaml for worker node security configuration Added policies.yaml for Kubernetes policies Added etcd.yaml for etcd node configuration Added controlplane.yaml for control plane configuration Added config.yaml with version-specific settings	cfg/k3s-cis-1.8/master.yaml cfg/k3s-cis-1.8/node.yaml cfg/k3s-cis-1.8/policies.yaml cfg/k3s-cis-1.8/etcd.yaml cfg/k3s-cis-1.8/controlplane.yaml cfg/k3s-cis-1.8/config.yaml
Updated existing K3s CIS benchmark files	Modified audit commands to use journalctl with -m flag Updated remediation steps to reflect K3s-specific configurations Adjusted file paths and default settings for K3s components	cfg/k3s-cis-1.24/master.yaml cfg/k3s-cis-1.24/node.yaml cfg/k3s-cis-1.24/policies.yaml cfg/k3s-cis-1.24/etcd.yaml cfg/k3s-cis-1.24/controlplane.yaml cfg/k3s-cis-1.7/master.yaml cfg/k3s-cis-1.7/node.yaml cfg/k3s-cis-1.7/policies.yaml cfg/k3s-cis-1.7/etcd.yaml cfg/k3s-cis-1.7/controlplane.yaml
Updated Go dependencies and build configurations	Upgraded Go version to 1.22.7 Updated various AWS SDK dependencies Changed kubectl version to 1.31.0	go.mod .github/workflows/build.yml .github/workflows/release.yml makefile
Modified AWS Security Finding Format (ASFF) handling	Updated FailedCount and SuccessCount handling to use pointers Changed Confidence field to use aws.Int32 instead of dereferencing	internal/findings/publisher.go check/controls.go check/controls_test.go

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, khulnasoft-bot!). We assume it knows what it's doing!