fix: Update K8s and Consul API dependencies to address security vulnerabilities

[Ilhan-Personal]

Fixes #37151

This PR addresses two security vulnerabilities by updating dependencies:
K8s Dependencies
Updated k8s.io/api, k8s.io/apimachinery, k8s.io/client-go, and k8s.io/utils to v0.33.0
Fixes high severity DoS vulnerability in k8s.io/apimachinery/pkg/util/runtime (CVE referenced in SNYK-GOLANG-K8SIOAPIMACHINERYPKGUTILRUNTIME-8367153)
Minimum required version for fix: v0.29.0-alpha.3
HashiCorp Consul API
Updated to v1.32.1 to address potential security concerns
Changes have been applied to both the main module and Kubernetes remote state backend module. Build verification confirms Terraform builds successfully with these updates.

[hashicorp-cla-app]

All committers have signed the CLA.

[SarahFrench]

Hi @Ilhan-Personal , thanks for your contribution! Could you please run make syncdeps from the project root, commit, and push those changes? That will make sure the dependency changes are matched in the other Go modules in this repo.

[jbardin]

Note for merging, this also needs the full acceptance tests for k8s and consul

[Ilhan-Personal]

Hi @SarahFrench , Thank you!

I've ran the script and pushed the changes

[SarahFrench]

@hashicorp/tf-eco-hybrid-cloud Could you test the Kubernetes backend following these changes please?

[SarahFrench]

I've figured out how to run the tests for the consul backend and they're all behaving the same way on this PR as they are on main. I've seen that TestConsul_largeState is failing on main, but that's out of scope of this PR and doesn't need to be addressed.

We just need to have the kubernetes backend tested now.

[Ilhan-Personal]

I've figured out how to run the tests for the consul backend

Just curious could you please maybe point me towards how you're testing these tests?

[SarahFrench]

I worked with the Hybrid Cloud team to get the kubernetes backend's tests run on this PR and they all passed, so I'm happy to approve & merge.

[SarahFrench]

I've figured out how to run the tests for the consul backend

Just curious could you please maybe point me towards how you're testing these tests?

That backend is unmaintained, so I found a way to run the tests but it's almost definitely not the best way. What I did was:

• Install Consul, so that the consul CLI is in your PATH
  • The acceptance tests for the consul backend run consul commands to launch an agent
• cd into internal/backend/remote-state/consul
• Run go test commands to run one test at a time, e.g. TF_ACC=1 go test -v -run=^TestBackend$
  • You need TF_ACC set, else the test is skipped
  • I found that if I ran more than one test at a time then they may clash, as each launches its own agent
    • If these errors came up I'd need to kill any still-running consul processes on my machine before running the next test.

There are a bunch of ENVs in the Consul SDK that might make this experience smoother, but I've got minimal Consul knowledge and haven't looked into ways to improve the test performance. Hopefully the instructions above are sufficient to get you started!

[Ilhan-Personal]

Thank you so much @SarahFrench

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.