Bug 1899435 - GCP: the dns for *.apps in Google Cloud DNS is not updated when updating spec.endpointPublishingStrategy.loadBalancer.scope
Summary: GCP: the dns for *.apps in Google Cloud DNS is not updated when updating spec...
Keywords:
Status: CLOSED DUPLICATE of bug 1898417
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.7
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.7.0
Assignee: Miheer Salunke
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-19 08:37 UTC by Hongan Li
Modified: 2022-08-04 22:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-08 10:34:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Hongan Li 2020-11-19 08:37:04 UTC
Description of problem:
the dns for *.apps in Google Cloud DNS is not updated when updating ingresscontroller spec.endpointPublishingStrategy.loadBalancer.scope from Internal to External and/or vice versa. 

Version-Release number of selected component (if applicable):
4.7.0-0.nightly-2020-11-18-203317

How reproducible:
100%

Steps to Reproduce:
1. launch a cluster on GCP.
2. change the spec.endpointPublishingStrategy.loadBalancer.scope to Internal
   #oc -n openshift-ingress-operator edit ingresscontroller/default

3. change back the scope from Internal to External
   # oc -n openshift-ingress-operator patch ingresscontroller/default -p '{"spec":{"endpointPublishingStrategy":{"loadBalancer":{"scope":"External"}}}}' --type=merge

Actual results:
Checked Google Cloud DNS and it always shows the first IP 35.202.177.208 for *.apps.<cluster-name>.<domain>.

step1:
# oc -n openshift-ingress get svc
NAME                      TYPE           CLUSTER-IP     EXTERNAL-IP      PORT(S)                      AGE
router-default            LoadBalancer   172.30.33.31   35.202.177.208   80:32225/TCP,443:32658/TCP   5m50s

step2:
# oc -n openshift-ingress get svc
NAME                      TYPE           CLUSTER-IP     EXTERNAL-IP   PORT(S)                      AGE
router-default            LoadBalancer   172.30.33.31   10.0.32.5     80:32225/TCP,443:32658/TCP   6m46s

step3:
# oc -n openshift-ingress get svc
NAME                      TYPE           CLUSTER-IP     EXTERNAL-IP    PORT(S)                      AGE
router-default            LoadBalancer   172.30.33.31   34.72.136.74   80:32225/TCP,443:32658/TCP   28m

Expected results:
step2: the DNS for *.apps should be updated to 10.0.32.5 
step3: the DNS for *.apps should be updated to 34.72.136.74

Additional info:
no this issue on AWS/Azure.

Comment 1 Hongan Li 2020-11-19 08:56:08 UTC
the root cause might be same to https://bugzilla.redhat.com/show_bug.cgi?id=1898417#c2, but for this one I don't think the workaround (recreating dnsrecords) is acceptable, maybe we should add logic for GCP platform to refresh Google Cloud DNS.

Comment 2 Andrew McDermott 2020-11-19 17:17:28 UTC
Any fix here should update the docs to say that in 4.7 we can now change scope. This should be backported to 4.6 but not beyond that.

Comment 4 Miheer Salunke 2020-12-08 10:34:12 UTC

*** This bug has been marked as a duplicate of bug 1898417 ***


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