Bug 1891952 - [Release 4.7] Apps Domain Enhancement
Summary: [Release 4.7] Apps Domain Enhancement
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.7
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.7.0
Assignee: Miciah Dashiel Butler Masters
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks: 1891957 1898347
TreeView+ depends on / blocked
 
Reported: 2020-10-27 18:23 UTC by Dustin Row
Modified: 2022-10-13 16:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:28:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-config-operator pull 167 0 None closed Bug 1891952: Bump API For Ingress AppsDomain Field 2021-02-08 03:02:12 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:29:09 UTC

Comment 3 Hongan Li 2020-11-17 08:54:18 UTC
Tested with 4.7.0-0.nightly-2020-11-12-200927 but both "oc edit" and "oc patch" cannot add the new appsDomain to ingresses.config/cluster. Am I missing something?

# oc edit ingresses.config/cluster -oyaml    # adding appsDomain and saved
# oc get ingresses.config/cluster -oyaml
<--snip--->
spec:
  domain: apps.hongli-az47.qe.azure.devcluster.openshift.com
status: {}


# oc patch ingresses.config/cluster -p '{"spec":{"appsDomain":"apps.fidata.io"}}' --type=merge
ingress.config.openshift.io/cluster patched (no change)
# oc get ingresses.config/cluster -oyaml
apiVersion: config.openshift.io/v1
kind: Ingress
metadata:
  creationTimestamp: "2020-11-17T01:14:42Z"
  generation: 1
  managedFields:
  - apiVersion: config.openshift.io/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:spec:
        .: {}
        f:domain: {}
      f:status: {}
    manager: cluster-bootstrap
    operation: Update
    time: "2020-11-17T01:14:42Z"
  name: cluster
  resourceVersion: "525"
  selfLink: /apis/config.openshift.io/v1/ingresses/cluster
  uid: a4367ff2-75b9-44b6-92f7-d74bc85eb196
spec:
  domain: apps.hongli-az47.qe.azure.devcluster.openshift.com
status: {}

Comment 5 Hongan Li 2020-11-25 11:44:54 UTC
Tested with 4.7.0-0.nightly-2020-11-24-151855 and passed.

NOTE:
changing spec.appsDomain causes openshift-apiserver operator to perform a rolling update of the openshift-apiserver pods which takes some minutes. After the rollout, the new created route will use the spec.appsDomain.


# oc patch ingresses.config/cluster -p '{"spec":{"appsDomain":"second.exmaple.com"}}' --type=merge

# oc -n openshift-apiserver get pods
NAME                         READY   STATUS        RESTARTS   AGE
apiserver-5954447598-2hvpl   2/2     Running       0          114s
apiserver-5954447598-xk92t   0/2     Pending       0          39s
apiserver-869774b97f-926cr   2/2     Terminating   0          11m
apiserver-869774b97f-n4274   2/2     Running       0          12m

### after the rollout, create a route
# oc expose svc service-unsecure

# oc get route
NAME               HOST/PORT                                     PATH   SERVICES           PORT   TERMINATION   WILDCARD
service-unsecure   service-unsecure-hongli1.second.example.com          service-unsecure   http                 None

Comment 8 errata-xmlrpc 2021-02-24 15:28:35 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633


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