Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1691069 - cluster-ingress-operator does not respond to changes in endpointPublishingStrategy
Summary: cluster-ingress-operator does not respond to changes in endpointPublishingStr...
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Routing
Version: 4.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.2.0
Assignee: Dan Mace
QA Contact: Hongan Li
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-20 19:16 UTC by Abhinav Dahiya
Modified: 2019-03-21 15:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)
ingress-operator-logs (deleted)
2019-03-20 19:16 UTC, Abhinav Dahiya
no flags Details

Description Abhinav Dahiya 2019-03-20 19:16:27 UTC
Created attachment 1546197 [details]

Description of problem:

While testing for bare-metal UPI, the ingress-operator creates the ingress with Private publishing strategy.

So I patched the default ingresscontroller object to switch ingress to HostNetwork. but even after waiting for quite sometime the ingress was still in Private strategy.

How reproducible:

$ oc --config dev-metal/auth/kubeconfig patch default --type merge --patch '{"spec":{"endpointPublishingStrategy": {"type": "HostNetwork"}}}' -n openshift-ingress-operator patched

## wait for few minutes..

$ oc --config dev-metal/auth/kubeconfig get default -n openshift-ingress-operator -ojson | jq '.status'
  "availableReplicas": 1,
  "domain": "",
  "endpointPublishingStrategy": {
    "type": "Private"
  "selector": "app=router,router=router-default"

Actual results:

The ingress stays in Private

Expected results:

The ingress to have moved to HostNetwork

Additional info:

Comment 1 Dan Mace 2019-03-21 15:29:18 UTC
The endpointPublishingStrategy field is currently immutable post-creation by design[1]. We would like to support mutations, but it's not clear we can get it working correct in the 4.1 timeframe. If the workaround (deleting/recreating the default ingresscontroller or creating a new one entirely) is insufficient, please let us know so we can talk about reprioritizing.


Note You need to log in before you can comment on or make changes to this bug.