Remove empty credentials check

[jrhouston]

Description

This PR removes the check function that generates an error when the kubernetes provider block doesn't seem to have been configured. We are hoping this should remedy some of the issues seen in #647 and #52. The downside of this is you get a confusing error message from client-go if you don't configure the provider block correctly.

Acceptance tests

• Have you added an acceptance test for the functionality being added?

Release Note

Release note for CHANGELOG:

Remove empty credentials check for kubernetes block 

References

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

[dak1n1]

I really liked this check! 😢 But maybe we'll bring it back later, with some additions. I'm planning to test it out in the Kubernetes provider (post 2.0 release) and then cover all the edge cases I can find. So some day, it might be back... Thanks for this PR!

[jrhouston]

Yeah I am hoping we can figure out something useful with warnings rather than errors that doesn't trigger the progressive apply issue.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!