-
Notifications
You must be signed in to change notification settings - Fork 24
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
Errors and warnings in logs, no domains added to DNS Resolver #3
Comments
Sorry to hear that :( if you revert to the earlier version do they come back? |
Yes, that is what I did for now. |
Interesting, I'll have a look and see what I can see. |
What about 1.7? Just trying to narrow down the code diff. |
Version 0.1.7 seems to work fine! |
I'm guessing it has something to do with k8s version checking to determine new endpoints or related. I use the service plugin without issue however on a 1.15 cluster without issue so that's a bit strange. I may have you send me the output of the same resource using the 2 different endpoints and see what we get. |
You mean ingress resources Update: silly me, I have accessed both resources with a cluster admin account. Impersonating service account shows different picture: 403 on |
Yeah nice find. I didn't see it because I run out of cluster with admin config :( |
0.1.8 with change in ClusterRole does fix most of the error messages, but one persists:
Just tried to delete a service with a hostname and had another one:
|
Do you use dnsmasq? |
I use |
Turn off dnsmasq in your configmap. |
That clear everything up? |
Seems to be the case! |
Using version 0.1.8, just updated from 0.1.5 and all my cluster domain names are gone from DNS resolver settings.
I am seeing warnings and errors in logs of the controller:
ConfigMap
kubernetes-pfsense-controller-store
has{"managed_hosts":[]}
for bothpfsense-dns-ingresses
as well aspfsense-dns-services
.Running kubernetes version 1.15.5
The text was updated successfully, but these errors were encountered: