chore(wrapper): removed viper os fallback due to underlying update

[bxrne]

What this PR does / why we need it:

This PR removes a workaround in internal/wrapper.go that was added to handle a bug in viper's ConfigFileNotFoundError (see viper#1783). The workaround used os.Stat as a fallback to check if a config file exists when viper failed to detect it.

Since the viper issue has been resolved, this workaround is no longer needed and can be removed.

Changes made:

• Removed os.Stat fallback for main config file and for custom resource config file
• Removed associated TODO comments referencing the viper issue

How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)

Does not change cardinality - this is a code cleanup with no functional changes, but is in hot path.

Which issue(s) this PR fixes:

#2895

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bxrne
Once this PR has been reviewed and has the lgtm label, please assign catherinef-dev for approval. For more information see the Code Review Process.

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

Details

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]

This issue is currently awaiting triage.

If kube-state-metrics contributors determine 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.

Details

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.

[k8s-ci-robot]

@bhope: The label(s) triage/not-accepted cannot be applied, because the repository doesn't have them.

Details

In response to this:

In KSM we pin to viper v1.21.0. That viper release was cut in Sept 2025 and does not have the fix you are referring to (spf13/viper#2027 ). Unfortunately, we would have to wait until we pin to newer viper release that has that fix (which at the moment there isn't).

/triage not-accepted

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.

[bhope]

In KSM we pin to viper v1.21.0. That viper release was cut in Sept 2025 and does not have the fix you are referring to (spf13/viper#2027 ). Unfortunately, we would have to wait until we pin to newer viper release that has that fix (which at the moment there isn't).

/hold