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.

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

Error: expected spec.0.cluster_ip to contain a valid IP, got: None #1291

Closed
arohter opened this issue Jun 3, 2021 · 2 comments · Fixed by #1292
Closed

Error: expected spec.0.cluster_ip to contain a valid IP, got: None #1291

arohter opened this issue Jun 3, 2021 · 2 comments · Fixed by #1292
Labels

Comments

@arohter
Copy link

arohter commented Jun 3, 2021

#1273
missed the valid None value, and will likely break a whole lot of deployments when people start using the new release https://github.com/hashicorp/terraform-provider-kubernetes/releases/tag/v2.3.0

None is valid in addition to IP address https://github.com/hashicorp/terraform-provider-kubernetes/blob/main/kubernetes/resource_kubernetes_service.go#L61

Error: expected spec.0.cluster_ip to contain a valid IP, got: None

... in resource "kubernetes_service" "svc":
        cluster_ip = "None"
@jrhouston
Copy link
Collaborator

Thanks for reporting this @arohter – I have opened a PR with a fix and added a regression test for this. We'll cut a hotfix release shortly.

@github-actions
Copy link

github-actions bot commented Jul 4, 2021

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants