chore(ci): add Gosec static analysis for security scanning

[schen6318]

Summary

This pull request adds a GitHub Action workflow that integrates Gosec, a static analysis tool for Golang, into the CI pipeline.

Purpose

The goal is to automatically scan for potential security vulnerabilities during development. These include:

• Use of insecure or dangerous functions (e.g., os/exec, unsafe)
• Hardcoded credentials and secrets
• Weak or misconfigured cryptographic operations
• Insecure HTTP server settings (e.g., missing timeouts, unverified TLS)
• Other common security flaws mapped to CWE (Common Weakness Enumeration)

Implementation

• Added .github/workflows/gosec.yml with configuration to run Gosec on all Go source files.
• The workflow is triggered on every push and pull request targeting the master branch.
• Gosec will automatically report any issues found as warnings directly in the GitHub Actions interface.

Notes

• This lays the foundation for secure coding practices across the project.
• No application logic has been changed in this pull request.

---

I recommend integrating this as a baseline CI security practice for all future contributions.

[linux-foundation-easycla]

• ✅login: schen6318 / (6142973)
• ✅login: schen6318 / (6142973, ba0746e)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: schen6318
Once this PR has been reviewed and has the lgtm label, please assign maciaszczykm for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @schen6318!

It looks like this is your first PR to kubernetes/dashboard 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/dashboard has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃