Replace opencensus vanity url to avoid expired cert

[mselim00]

Adds a go.mod directive then go mod tidy

This repo has a dependency on go.opencensus.io, which has been archived since July, 2023. The certificates for that vanity URL have expired, causing downstream CI failures (and general build issues).

This is intended as a temporary fix until the dependencies here that require it can fully migrate off.

See

• aws-otel-collector build fails caused by expired certificate in go.opencensus.io aws-observability/aws-otel-collector#2946
• certificate issue at go.opencensus.io googleapis/google-cloud-go#11481 (comment)

Edit

This is probably not safe to merge, or makes things worse anyway. Tested go install github.com/mselim00/kubetest2@latest and got:

The go.mod file for the module providing named packages contains one or
more replace directives. It must not contain directives that would cause
it to be interpreted differently than if it were the main module.

It seems packages that have replace directives must be installed from source (git clone + cd + go install .), which would be a breaking change for probably any downstream.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mselim00
Once this PR has been reviewed and has the lgtm label, please assign jbpratt 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 @mselim00!

It looks like this is your first PR to kubernetes-sigs/kubetest2 🎉. 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-sigs/kubetest2 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. 😃

[k8s-ci-robot]

Hi @mselim00. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[cartermckinnon]

/ok-to-test

normally want to avoid replace, but this particular module is dead and I wouldn't expect future releases, so carrying the replace isn't so bad.

It's a transitive dependency of cloud.google.com/go/storage which is used in k8s.io/release/build.

[cartermckinnon]

/close

replace will break go install :(

[k8s-ci-robot]

@cartermckinnon: Closed this PR.

In response to this:

/close

replace will break go install :(

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.