-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
OSSM 3.0.3
-
None
-
False
-
-
False
-
-
With OSSM 2.x we deployed the ControlPlane with following setting for all proxies
proxyMetadata:
ISTIO_META_DNS_AUTO_ALLOCATE: 'true'
ISTIO_META_DNS_CAPTURE: 'true'
That has changed with OSSM 3.x which does not populate those METADATA setting leading to following behavior when resolving ServiceEntries
print(requests.get('http://something.internal:8080')) requests.exceptions.ConnectionError: HTTPConnectionPool(host='something.internal', port=8080): Max retries exceeded with url: / (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0x7f93d6da8e20>: Failed to resolve 'something.internal' ([Errno -2] Name or service not known)"))
event though having a ServiceEntry configured accordingly.
Pushing those values into an OSSM 3.x Istio CR get's the expected behavior back
print(requests.get('http://something.internal:8080'))
<Response [200]>
Reproducer steps:
- deploy a default Istio CR with OSSM 3.x
- deploy a workload with curl or python-requests
- deploy a ServiceEntry as specified below
- try accessing the service
apiVersion: networking.istio.io/v1 kind: ServiceEntry metadata: name: dns-capture namespace: whatever spec: addresses: - 127.0.0.1 exportTo: - . hosts: - something.internal location: MESH_INTERNAL ports: - name: http number: 8080 protocol: http targetPort: 8080 resolution: NONE
- is related to
-
-
- New
-