-
Notifications
You must be signed in to change notification settings - Fork 8
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
Custom dns policy makes sdp-dnsmasq crash #38
Comments
Right now we detect it but the error is really far from relevant :D Since we don't support that option (I don't really know if there is a user case for it) we can just let the injector to fail the validation of the POD in that case. |
Yes let's just make it clear the |
#61 This PR made the injector to override the dnsConfig always into something like this
|
what does your |
Have you tried adding something like: spec:
hostname:
subdomain:
containers:
- image: # image ref
name: sdp # name reference to corresponding service `metadata.name`
---
# associated service
apiVersion: v1
kind: Service
metadata:
name: sdp # or something similar
spec:
selector:
name: sdp
clusterIP: None
ports:
- name: foo # Actually, no port is needed.
port: 1234
targetPort: 1234 using approach outlined here |
FIX:: can't use reserved port...ie: 53. use 50053 or something that ur non-root user can open without needing privs ... or got back to running as root. |
Given a pod including the following spec:
Results in the sdp-dnsmasq sidecar failing to start:
We should at least detect the issue and emit a relevant error.
The text was updated successfully, but these errors were encountered: