chore: Use Capabilities.KubeVersion in helm charts

[omerap12]

What type of PR is this?
/kind feature

What this PR does / why we need it:
Use Capabilities.KubeVersion instead of kubernetesReleaseVersion value
Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #61

Special notes for your reviewer:

TODOs:

• squashed commits
• includes documentation
• adds unit tests

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: omerap12
Once this PR has been reviewed and has the lgtm label, please assign enj for approval. For more information see the Kubernetes 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

[aramase]

/retitle chore: Use Capabilities.KubeVersion in helm charts

[aramase]

Please update the yamls in the manifest_staging/charts folder and revert any changes in charts/.

manifest_staging folder is where we host the staging charts and deployment yamls. All the yaml changes will then be promoted into the released charts folder with the next release.

[omerap12]

Please update the yamls in the manifest_staging/charts folder and revert any changes in charts/.

manifest_staging folder is where we host the staging charts and deployment yamls. All the yaml changes will then be promoted into the released charts folder with the next release.

Done

[aramase]

/assign @nilekhc

[nilekhc]

/lgtm

[aramase]

Found #78 as part of testing this.

[nilekhc]

/retest

[nilekhc]

/test all

[AlexanderStocks]

This is failing because we are relying solely on the Kubernetes version to determine the availability of the VAP resources in the tests and not altering the cluster config, which isn't always true because feature gates might not be enabled. To fix this we will need to vary the cluster config provided for each test. Should we document somewhere that if installing with a version before 1.30.0 (when VAPs were classed as stable) a user may need to alter their cluster config? @nilekhc

[nilekhc]

/test all

[aramase]

/retest-required

[nilekhc]

This is failing because we are relying solely on the Kubernetes version to determine the availability of the VAP resources in the tests and not altering the cluster config, which isn't always true because feature gates might not be enabled. To fix this we will need to vary the cluster config provided for each test. Should we document somewhere that if installing with a version before 1.30.0 (when VAPs were classed as stable) a user may need to alter their cluster config? @nilekhc

@omerap12, we need to modify local-setup such that it takes correct feature gate in kind-config.yaml while creating cluster.

[omerap12]

This is failing because we are relying solely on the Kubernetes version to determine the availability of the VAP resources in the tests and not altering the cluster config, which isn't always true because feature gates might not be enabled. To fix this we will need to vary the cluster config provided for each test. Should we document somewhere that if installing with a version before 1.30.0 (when VAPs were classed as stable) a user may need to alter their cluster config? @nilekhc

@omerap12, we need to modify local-setup such that it takes correct feature gate in kind-config.yaml while creating cluster.

Ill take a look into it

[k8s-ci-robot]

New changes are detected. LGTM label has been removed.

[k8s-ci-robot]

@omerap12: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-secrets-store-sync-controller-e2e-provider-k8s-1-30-2	5146fdb	link	true	/test pull-secrets-store-sync-controller-e2e-provider-k8s-1-30-2
pull-secrets-store-sync-controller-e2e-provider-k8s-1-28-11	5146fdb	link	true	/test pull-secrets-store-sync-controller-e2e-provider-k8s-1-28-11
pull-secrets-store-sync-controller-e2e-provider-k8s-1-27-15	5146fdb	link	true	/test pull-secrets-store-sync-controller-e2e-provider-k8s-1-27-15
pull-secrets-store-sync-controller-e2e-provider-k8s-1-29-6	5146fdb	link	true	/test pull-secrets-store-sync-controller-e2e-provider-k8s-1-29-6
pull-secrets-store-sync-controller-e2e-provider-k8s-1-29-8	eaafbb3	link	true	/test pull-secrets-store-sync-controller-e2e-provider-k8s-1-29-8

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.