Closed lilic closed 6 years ago
This error was due to my kubectl
release being too new to support such an old cluster. I tested running on 1.6.0
k8s cluster with older kubectl
version and the resources were created correctly, so closing this issue.
This happened on 1.6.0 version before the DNS check was merged. So right now in master we do error out when DNS is not working and the following error happens after DNS check and I have not fully tried it with 1.6.0 cluster and DNS working. But something worth looking into, as we are supporting 1.6+ clusters and we want to make sure this works for those clusters.