Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1624475

Summary:	Calico requires a role be added that runs stand-alone kube-proxy and DNS
Product:	OpenShift Container Platform	Reporter:	Marc Curry <mcurry>
Component:	Networking	Assignee:	Ricardo Carrillo Cruz <ricarril>
Status:	CLOSED ERRATA	QA Contact:	Meng Bo <bmeng>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.10.0	CC:	aos-bugs, ricarril, shiywang, zzhao
Target Milestone:	---
Target Release:	3.10.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-11 09:30:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marc Curry 2018-08-31 17:54:44 UTC

Description of problem:
OCP 3.10 moved the default openshift-sdn network plugin implementation to daemonSets, and kube-proxy functionality was moved into the "sdn" daemonSet along with openshift-sdn and DNS. Calico still requires the kube-proxy to be loaded in the kubelet process space.

Version-Release number of selected component (if applicable):
3.10

How reproducible:
Every time.

Steps to Reproduce:
1.Deploy Calico + OpenShift 3.10.

Actual results:
kube-proxy and DNS are not started.

Expected results:
kube-proxy and DNS are started on the node when using Calico CNI plug-in.

Additional info:
$ openshift start network --disable=plugins --enable=proxy,dns

Comment 1 Casey Callendrello 2018-09-04 13:53:25 UTC

I believe this is fixed in https://github.com/openshift/openshift-ansible/pull/9878

Comment 4 shiyang.wang 2019-04-17 03:05:30 UTC

Sorry, attached to the wrong advisory move back to MODIFIED

Comment 8 errata-xmlrpc 2019-06-11 09:30:48 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0786