Skip to content
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

Fix dnsname when joining a different network namespace in a pod #8203

Merged
merged 1 commit into from
Oct 31, 2020

Conversation

Luap99
Copy link
Member

@Luap99 Luap99 commented Oct 30, 2020

When creating a container in a pod the podname was always set as
the dns entry. This is incorrect when the container is not part
of the pods network namespace. This happend both rootful and
rootless. To fix this check if we are part of the pods network
namespace and if not use the container name as dns entry.

Fixes #8194

@rhatdan
Copy link
Member

rhatdan commented Oct 30, 2020

With the DNS network Alias stuff that @baude is working on, could we have multiple aliases for the same pod, when running within a pod?

@mheon
Copy link
Member

mheon commented Oct 30, 2020

We'd need to extend the aliases support from containers to pods - wouldn't be that bad.

@mheon
Copy link
Member

mheon commented Oct 30, 2020

This PR LGTM though
/approve

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99, mheon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 30, 2020
When creating a container in a pod the podname was always set as
the dns entry. This is incorrect when the container is not part
of the pods network namespace. This happend both rootful and
rootless. To fix this check if we are part of the pods network
namespace and if not use the container name as dns entry.

Signed-off-by: Paul Holzinger <paul.holzinger@web.de>
@Luap99
Copy link
Member Author

Luap99 commented Oct 30, 2020

The test caught an error. I also have to make sure we use the pod name for infra containers.

@TomSweeneyRedHat
Copy link
Member

LGTM

@rhatdan
Copy link
Member

rhatdan commented Oct 31, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 31, 2020
@openshift-merge-robot openshift-merge-robot merged commit 5a53c6e into containers:master Oct 31, 2020
@Luap99 Luap99 deleted the fix-8194 branch November 19, 2020 20:33
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DNS using container name fails for containers on user-defined rootless cni network with a pod
6 participants