feat: add GitHub Actions workflow for linting and testing Helm charts

[oujonny]

Pull Request

• Make sure you have followed Kube-OVN Code Style.

What type of this PR

Examples of user facing changes:

• Features
• Bug fixes
• Docs
• Tests

Which issue(s) this PR fixes

Fixes #(issue-number)

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[coveralls]

Pull Request Test Coverage Report for Build 21707915670

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 1841 unchanged lines in 26 files lost coverage.
• Overall coverage increased (+0.2%) to 23.034%

---

Files with Coverage Reduction	New Missed Lines	%
pkg/ovnmonitor/exporter.go	5	0.0%
pkg/controller/pod.go	6	9.91%
pkg/apis/kubeovn/v1/vpc-nat-gateway.go	8	0.0%
pkg/request/cniserver.go	8	0.0%
pkg/ovs/ovn-ic-nbctl.go	9	77.08%
pkg/ovs/ovs-appctl_linux.go	11	0.0%
pkg/daemon/flow_rules_linux.go	14	0.0%
pkg/speaker/eip.go	17	0.0%
pkg/util/vpc_nat_gateway.go	17	86.52%
pkg/controller/network_attachment.go	21	9.8%

Totals
Change from base Build 21161090554:	0.2%
Covered Lines:	12436
Relevant Lines:	53990

---

💛 - Coveralls

[oujonny]

I managed to get the first successful run. This means a successful lint and a helm install
see: https://github.com/kubeovn/kube-ovn/actions/runs/21176042613/job/60905034334#step:10:33

@SkalaNetworks wdyt?

[SkalaNetworks]

Thanks for the PR, have you tested this CI to see its results? I'm in interested in how it fails if linting or deploying doesn't work because of a broken commit.

[SkalaNetworks]

The tests executed during this PR seem to fail but without triggering any error.

[oujonny]

@SkalaNetworks, this is nothing new and the same for all other workflows with kind involved. For example, here: https://github.com/kubeovn/kube-ovn/actions/runs/21705765236/job/62597476753 (Post Install kind)

But I just realized that we have a basic installation (no linting) for the v1 chart in a workflow here: https://github.com/kubeovn/kube-ovn/blob/master/.github/workflows/build-x86-image.yaml#L1696

I think haveing it in a dedicated workflow is maybe better, or should we update the build-x86 to also run the tests for v2 chart?

[SkalaNetworks]

I think a separate workflow makes everything cleaner

[oujonny]

@SkalaNetworks, I resolved your comments and would say this PR is ready now for a merge, or did I miss something?

[SkalaNetworks]

LGTM, thank you, this will get merged shortly

[oujonny]

/gemini summary

[gemini-code-assist]

Summary of Changes

This pull request establishes a new GitHub Actions workflow designed to enhance the continuous integration process for Helm charts. By automating linting and testing, it ensures that changes to the kube-ovn-v2 chart meet quality standards and function correctly before being merged, thereby improving the overall reliability and maintainability of the project's Helm deployments.

Highlights

• New GitHub Actions Workflow: Introduced a dedicated GitHub Actions workflow to automate linting and testing of Helm charts, specifically for kube-ovn-v2.
• Helm Chart Version Update: Updated the kube-ovn-v2 Helm chart version from v1.16.0 to v1.16.1.

Changelog

• charts/kube-ovn-v2/Chart.yaml
  • Updated the chart version from v1.16.0 to v1.16.1.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/helm-testing.yaml

Activity

• gemini-code-assist[bot] noted an inability to generate a summary due to unsupported file types.
• coveralls provided a test coverage report, including a warning about an inaccurate base commit.
• oujonny reported the first successful run of the new workflow (lint and helm install) and requested feedback from SkalaNetworks.
• SkalaNetworks observed that tests appeared to fail without triggering explicit errors.
• oujonny discussed existing kind workflows and proposed keeping the new Helm testing in a dedicated workflow rather than integrating it into build-x86-image.yaml.
• SkalaNetworks agreed that a separate workflow provides a cleaner solution.
• oujonny confirmed that all previous comments were addressed and the PR was ready for merge.
• SkalaNetworks provided an LGTM (Looks Good To Me) and indicated the PR would be merged shortly.
• A discussion occurred regarding the maintainers field in Chart.yaml, leading to its removal and disabling of related validation.
• The workflow's trigger conditions were refined to activate only when changes are made within the charts/* directory, specifically for the v2 chart.
• Clarification was provided on the helm-diff command, confirming it runs on every PR and compares against the default branch as intended.
• A comment was requested to be removed.
• A conversation took place comparing the benefits of a full helm install with a kind cluster versus a simpler helm template dry-run for testing, with the decision to retain the helm install approach.