Add v1.Secret to go-flow-levee analysis targets

[tksm]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR adds v1.Secret to the list of go-flow-levee analysis targets.

The internal version of Secret (k8s.io/kubernetes/pkg/apis/core) was added datapolicy tag in #95992 , but v1.Secret (k8s.io/api/core/v1) is not tagged. v1.Secret is more widely used than the internal one, so it should be checked.

Which issue(s) this PR fixes:

Special notes for your reviewer:

I know KEP-1753 deprecation does not deprecate datapolicy tag, but the related PRs such as #95998, #95994, and #96008 were not merged, so I only added it to levee-config.yaml for now.

I confirmed that a log line intentionally added a v1.Secret object was detected with this config.

$ hack/verify-govet-levee.sh
# ...

# k8s.io/kubernetes/pkg/volume/secret
pkg/volume/secret/secret.go:193:12: a source has reached a sink
 source: pkg/volume/secret/secret.go:192:28
make: *** [vet] Error 1

diff --git a/pkg/volume/secret/secret.go b/pkg/volume/secret/secret.go
index 8226b2209ee..6fd5cd279e8 100644
--- a/pkg/volume/secret/secret.go
+++ b/pkg/volume/secret/secret.go
@@ -190,6 +190,7 @@ func (b *secretVolumeMounter) SetUpAt(dir string, mounterArgs volume.MounterArgs

        optional := b.source.Optional != nil && *b.source.Optional
        secret, err := b.getSecret(b.pod.Namespace, b.source.SecretName)
+       klog.Infof("This line should be detected %v", secret)
        if err != nil {
                if !(errors.IsNotFound(err) && optional) {
                        klog.Errorf("Couldn't get secret %v/%v: %v", b.pod.Namespace, b.source.SecretName, err)

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

• KEP: KEP-1933: Defend Against Logging Secrets via Static Analysis

[k8s-ci-robot]

@tksm: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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]

Hi @tksm. Thanks for your PR.

I'm waiting for a kubernetes 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/test-infra repository.

[tksm]

/assign PurelyApplied
as the author of KEP-1933

[PurelyApplied]

/lgtm

[tksm]

/retest

[k8s-ci-robot]

@tksm: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[PurelyApplied]

/ok-to-test

[tksm]

/assign @IanColdwater

[tksm]

/assign @tabbysable

[tabbysable]

/approve
/honk

[k8s-ci-robot]

@tabbysable:

In response to this:

/approve
/honk

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: tabbysable, tksm

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:

• hack/testdata/levee/OWNERS [tabbysable]

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