-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add dnsConfig to runner deployments #764
Conversation
The test the failed isn't clear why it failed. |
@sammcj seems like you need to rerun |
Thanks @mumoshu, I couldn't see that step mentioned in the README.md or CONTRIBUTING.md. |
Have rebased and pushed |
The test failure doesn't sound related:
@mumoshu any chance you could point me in the right direction? |
That might be due to test flakiness. Let me rerun it. |
Looks like it worked, do you think it looks like everything that's required? |
Yep, let's go ahead! Thanks for your contribution |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice
@sammcj has this worked as expected for you? I'm struggling at the moment and wondering if there is a configuration nuance that I'm missing. With the following apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
name: myorg-ephemeral-dns
namespace: actions
spec:
replicas: 1
template:
spec:
organization: myorg
labels:
- myorg-onprem-dns
dnsConfig:
- options:
- name: "ndots"
value: "1" ... The |
I think we may be missing something like this in if len(runner.Spec.DnsConfig ) != 0 {
pod.Spec.DnsConfig = runner.Spec.DnsConfig
} Going to try to test locally and if that's the case submit a new PR. |
#1227 raised for the above, FYI |
Add ability to set dnsConfig for runner deployments.
As per #761 (comment)
Note: I've never touched any golang or helm so just sort of fumbled my way through this - I'm sure I've missed several things.