Don't fail when unable to find default SA token secret

[alexsomesan]

Both the kubernetes_service_account datasource and resource contain a conveniece attribute to expose the default service account created automatically by the cluster along with the SA. The check for the secret to be deemed the "default" one, includes a matching of the creation timestamps between the SA and the associated Secret.

It's a valid scenario for the default token secret of a Service Account to be replaced throughout the lifecycle of the SA.

When this default secret is deleted, the cluster automatically generates a new one and updates the SA accordingly.

The provider should not fail when the default token is no longer available.

Description

Acceptance tests

• Have you added an acceptance test for the functionality being added?
• Have you run the acceptance tests on this branch?

Output from acceptance testing:

$ make testacc TESTARGS='-run=^TestAccKubernetesDataSourceServiceAccount_*'

=== RUN   TestAccKubernetesDataSourceServiceAccount_basic
--- PASS: TestAccKubernetesDataSourceServiceAccount_basic (4.42s)
=== RUN   TestAccKubernetesDataSourceServiceAccount_default_secret
--- PASS: TestAccKubernetesDataSourceServiceAccount_default_secret (4.44s)
PASS
ok  	github.com/hashicorp/terraform-provider-kubernetes/kubernetes	9.389s

Release Note

Release note for CHANGELOG:

Fix fail when the provider cannot determine `default_secret_name`.

References

Fixes #1104

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[jrhouston]

Perhaps should be a warning diagnostic to tell the user this has happened, rather than simply a log?

[alexsomesan]

Was also considering that as an option. Let's do that instead.

[hashicorp-cla]

All committers have signed the CLA.

[alexsomesan]

@arybolovlev This works great! thanks for picking this up!
Can't approve as I'm the one who created the PR. We need @jrhouston to have a look.

[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 issues.
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.