test: add e2e for --filtered-watch-secret=false

[aramase]

Signed-off-by: Anish Ramasekar anish.ramasekar@gmail.com

What this PR does / why we need it:

• Adds test for --filtered-watch-secret=false

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 #

Special notes for your reviewer:

[aramase]

/cc @nilekhc

[k8s-ci-robot]

@aramase: GitHub didn't allow me to request PR reviews from the following users: nilekhc.

Note that only kubernetes-sigs members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @nilekhc

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/test-infra repository.

[aramase]

/hold for #593 to be merged

[aramase]

/hold cancel

[nilekhc]

/lgtm

[k8s-ci-robot]

@nilekhc: changing LGTM is restricted to collaborators

In response to this:

/lgtm

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/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aramase, nilekhc

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [aramase]

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

[tam7t]

To make sure I understand, filteredWatchSecret=true in the next release, but we want to make sure everything continues to work if everything is deployed with filteredWatchSecret=false?

Is there a targeted release where filteredWatchSecret=false will be unsupported?

[aramase]

To make sure I understand, filteredWatchSecret=true in the next release, but we want to make sure everything continues to work if everything is deployed with filteredWatchSecret=false?

That's right!

Is there a targeted release where filteredWatchSecret=false will be unsupported?

We'll make it unsupported in the release after. We'll deprecate the flag and remove it in future releases.

[tam7t]

/lgtm