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 DNS policy for host-networked pods #790

Merged
merged 1 commit into from
Jul 31, 2020

Conversation

caseydavenport
Copy link
Member

Description

Otherwise they fail to lookup services within the cluster

For PR author

  • Tests for change.
  • If changing pkg/apis/, run make gen-files
  • If changing versions, run make gen-versions

For PR reviewers

A note for code reviewers - all pull requests must have the following:

  • Milestone set according to targeted release.
  • Appropriate labels:
    • kind/bug if this is a bugfix.
    • kind/enhancement if this is a a new feature.
    • enterprise if this PR applies to Calico Enterprise only.

@caseydavenport caseydavenport requested a review from tmjd July 31, 2020 00:12
Copy link
Member

@tmjd tmjd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think adding a check for that in the UTs would be worth while. (same for the logstorage one)

if c.installation.Spec.KubernetesProvider == operator.ProviderEKS &&
c.installation.Spec.CNI.Type == operator.PluginCalico {
// Workaround the fact that webhooks don't work for non-host-networked pods
// when in this networking mode on EKS, because the control plane nodes don't run
// Calico.
hostNetwork = true
dnsPolicy = corev1.DNSClusterFirstWithHostNet
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we include Otherwise they fail to lookup services within the cluster as a comment here?

Copy link
Member

@tmjd tmjd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not strongly opinionated on my comments so LGTM if you don't agree.
This will need to be picked to release-v1.9 also I assume.

@caseydavenport caseydavenport force-pushed the casey-fix-hostnet-dns branch from 205be3b to 3def5f9 Compare July 31, 2020 21:21
@caseydavenport caseydavenport merged commit 572e864 into tigera:master Jul 31, 2020
@caseydavenport caseydavenport deleted the casey-fix-hostnet-dns branch July 31, 2020 21:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants