Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

kubernetes_secret and kubernetes_storage_class unable to refresh state #97

Open
apeabody opened this issue Apr 23, 2022 · 4 comments
Open

kubernetes_secret and kubernetes_storage_class unable to refresh state #97

apeabody opened this issue Apr 23, 2022 · 4 comments
Labels
bug Something isn't working triaged Scoped and ready for work

Comments

@apeabody
Copy link
Contributor

TL;DR

The kubernetes_secret and kubernetes_storage_class are unable to refresh state. This manifests as the kubernetes provider attempting to dial tcp 127.0.0.1:80 rather than the configured cluster. This may be a result of the order in which Terraform evaluates the provider block vs the resources as noted in the Kubernetes Provider documentation and GKE example.

This also blocks #90 as with TF 0.15+ a refresh state is attempted prior to the destroy phase.

Expected behavior

No response

Observed behavior

No response

Terraform Configuration

CI

Terraform Version

TF 0.15+

Additional information

No response
@apeabody apeabody added the bug Something isn't working label Apr 23, 2022
@apeabody
Copy link
Contributor Author

@bharathkkb related to comment

@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Aug 30, 2022
@apeabody apeabody removed the Stale label Sep 6, 2022
@github-actions
Copy link

github-actions bot commented Nov 5, 2022

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Nov 5, 2022
@apeabody apeabody removed the Stale label Nov 7, 2022
@github-actions
Copy link

github-actions bot commented Jan 6, 2023

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the Stale label Jan 6, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 13, 2023
@bharathkkb bharathkkb removed the Stale label Jan 14, 2023
@bharathkkb bharathkkb reopened this Jan 14, 2023
@bharathkkb bharathkkb added the triaged Scoped and ready for work label Jan 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working triaged Scoped and ready for work
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bharathkkb @apeabody