-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.14, 4.15, 4.16
-
Quality / Stability / Reliability
-
False
-
-
None
-
Critical
-
None
-
None
-
None
-
Rejected
-
NI&D Sprint 276, NI&D Sprint 277
-
2
-
None
-
None
-
None
-
-
None
-
-
None
Description of problem:
If the tuningOptions were added without proper indentation in the IngressController, all the existing configurations under the spec section were overwritten/removed.
Version-Release number of selected component (if applicable):
OCP cluster v4.14.25, 4.15, 4.16+
How reproducible:
When we mistakenly added the tuningOptions without keeping the proper indentation in the ingresscontroller, then it causes the rest of the configuration under spec to disappear without throwing an error earlier.
Steps to Reproduce:
1. Edit the ingressController and add the tuningOptions parameter with only 1 space, then save it.
~~~
spec:
tuningOptions: >>>>>> the wrong indentation causes the configuration under spec to disappear. reloadInterval: 0s
clientTLS:
clientCA:
name: ""
clientCertificatePolicy: ""
httpCompression: {}
httpEmptyRequestsPolicy: Respond
httpErrorCodePages:
name: ""
httpHeaders:
headerNameCaseAdjustments:
~~~
2. After that, we noticed that without throwing any error, ingress pods started restarting but all the existing configurations got disappear from the spec section of the ingress controller.
~~~
spec:
httpEmptyRequestsPolicy: Respond
tuningOptions:
reloadInterval: 0s
~~~
Actual results:
Existing configurations got removed from the spec section.
Expected results:
It should throw an error or doesn't edit the changes.
Additional info:
