fix: resolve DNS hostnames from within pod in minikube#3609
fix: resolve DNS hostnames from within pod in minikube#3609PaulRepo wants to merge 1 commit intojenkins-x:mainfrom
Conversation
More info on this can be found at this [slack chat](https://kubernetes.slack.com/archives/C9MBGQJRH/p1652161645265129)
|
Kudos, SonarCloud Quality Gate passed!
|
|
Hi @PaulRepo. Thanks for your PR. I'm waiting for a jenkins-x or todo member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/assign @ankitm123 |
| With the recent upgrade of base image of ghcr.io/jenkins-x/jx-boot:3.2.338 to alpine linux v3.15 in some of the local providers like minikube, the pod's DNS nameserver is not able to resolve DNS hostname outside k8s cluster like github.com. | ||
|
|
||
| To resolve this issue you need to add [custom dnspolicy](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-s-dns-policy) on your local cluster repository in below files with this change | ||
| ```yaml |
There was a problem hiding this comment.
Is it possible to change the dns settings in the minikube cluster itself?
There was a problem hiding this comment.
yes it is possible and even I have raised a corresponding PR . But it will be specific to minikube and as you pointed out before, these changes cannot be merged to the jenkins-x versionStream repo.
There was a problem hiding this comment.
I meant if you can change it when creating the minikube cluster (before running jx admin operator and running the boot job).
There was a problem hiding this comment.
With further testing, I found some more bugs and above solution is not enough. I'll work upon it in my free time. As of now please do not merge this PR.
|
/hold |
3 participants
More info on this can be found at this slack chat
Description
with recent upgrade of alpine linux in image
ghcr.io/jenkins-x/jx-boot:3.2.338, minikube boot pod and pipelines are failing with error asCould not resolve host: github.comFixes # (issue)
Need to add custom
dnspolicyto boot and pipeline pods.