-
Notifications
You must be signed in to change notification settings - Fork 959
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
Include conditions in nodes data source #2430
Comments
Thanks for bringing this up. We think it would make for a useful improvement to the nodes datasource and will add it to our backlog for triage. In the mean time, you can achieve similar results by using the generic Here's an example of how that would work:
|
Thank you for your reply and adding it to your backlog. The |
Can you share the crash log? |
Sure, here is the crash log.
|
Which cluster type and version did you use this on? I will try to reproduce it. The example works fine for me on a kind cluster. |
I am using a kubeadm cluster build with cluster-api on version 1.24.14 and Terraform 1.7.3 with kubernetes-provider version 2.26.0. |
Could you also provide us with a core dump of the crash, please? Instructions for getting core dumps from Go processes are here: https://github.com/dailymotion/hands-on-diagnosing-golang-apps/blob/master/core-files/README.md |
Don't share the core file here directly as it might contain credentials to your cluster. |
@simonostendorf Do you think you'd be able to share a core file from the crash? I haven't been able to reproduce the same crash so far. |
Sorry for the late reply. I don't have much time this week. I will look at the crash next week. |
Sorry, I don't have enough time to look at the bug and reproduce it. |
No worries. I'm also on vacation this week and didn't advance my research very much. |
Description
I would like to get the node conditions inside the
kubernetes_nodes
data source.Currently only
addresses
,allocatable
,capacity
andnode_info
are exported.Potential Terraform Configuration
References
none
Community Note
The text was updated successfully, but these errors were encountered: