apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T03:49:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-175-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-175.ec2.internal
      uid: 8b9ff4e3-a6d3-4bf0-80e3-f31f9e5fc2b6
    resourceVersion: "15174"
    uid: 451f4378-b73e-4e5c-a471-e5260d5c4df1
  spec:
    sourcePod: network-check-source-65bdbbff45-lbbp7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T03:56:21Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.021381ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:56:21Z"
    - latency: 1.371158ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:55:21Z"
    - latency: 960.506µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:54:21Z"
    - latency: 1.01878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:53:21Z"
    - latency: 1.040469ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:52:21Z"
    - latency: 1.492651ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:51:21Z"
    - latency: 874.498µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:50:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T03:49:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-175-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-175.ec2.internal
      uid: 8b9ff4e3-a6d3-4bf0-80e3-f31f9e5fc2b6
    resourceVersion: "14836"
    uid: 0a9ae4e0-a5b2-4672-b7c1-1a474e60a14f
  spec:
    sourcePod: network-check-source-65bdbbff45-lbbp7
    targetEndpoint: aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T03:55:21Z"
      message: 'load-balancer-api-external: tcp connection to aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.037633ms
      message: 'load-balancer-api-external: tcp connection to aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:55:21Z"
    - latency: 6.163831ms
      message: 'load-balancer-api-external: resolved host name aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:55:21Z"
    - latency: 5.141754ms
      message: 'load-balancer-api-external: tcp connection to aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:54:21Z"
    - latency: 8.442556ms
      message: 'load-balancer-api-external: resolved host name aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:54:21Z"
    - latency: 5.753671ms
      message: 'load-balancer-api-external: tcp connection to aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:53:21Z"
    - latency: 8.490081ms
      message: 'load-balancer-api-external: resolved host name aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:53:21Z"
    - latency: 5.761344ms
      message: 'load-balancer-api-external: tcp connection to aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:52:21Z"
    - latency: 20.097791ms
      message: 'load-balancer-api-external: resolved host name aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:52:21Z"
    - latency: 5.131847ms
      message: 'load-balancer-api-external: tcp connection to aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:51:21Z"
    - latency: 6.357626ms
      message: 'load-balancer-api-external: resolved host name aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:51:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T03:49:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-175-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-175.ec2.internal
      uid: 8b9ff4e3-a6d3-4bf0-80e3-f31f9e5fc2b6
    resourceVersion: "14835"
    uid: f0cbcc04-0c87-40ee-9fc7-8fd4dd0843a0
  spec:
    sourcePod: network-check-source-65bdbbff45-lbbp7
    targetEndpoint: aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T03:55:21Z"
      message: 'load-balancer-api-internal: tcp connection to aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.045288ms
      message: 'load-balancer-api-internal: tcp connection to aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:55:21Z"
    - latency: 6.093064ms
      message: 'load-balancer-api-internal: resolved host name aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:55:21Z"
    - latency: 5.248055ms
      message: 'load-balancer-api-internal: tcp connection to aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:54:21Z"
    - latency: 8.22325ms
      message: 'load-balancer-api-internal: resolved host name aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:54:21Z"
    - latency: 6.564527ms
      message: 'load-balancer-api-internal: tcp connection to aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:53:21Z"
    - latency: 8.623615ms
      message: 'load-balancer-api-internal: resolved host name aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:53:21Z"
    - latency: 5.678802ms
      message: 'load-balancer-api-internal: tcp connection to aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:52:21Z"
    - latency: 20.188947ms
      message: 'load-balancer-api-internal: resolved host name aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:52:21Z"
    - latency: 4.114124ms
      message: 'load-balancer-api-internal: tcp connection to aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:51:21Z"
    - latency: 6.536911ms
      message: 'load-balancer-api-internal: resolved host name aa631270d48f54f5c8397a987103cc60-2c343b33764988ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:51:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T03:49:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-175-to-network-check-target-ip-10-0-132-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-175.ec2.internal
      uid: 8b9ff4e3-a6d3-4bf0-80e3-f31f9e5fc2b6
    resourceVersion: "15172"
    uid: 6b99064c-1d4a-4b8a-85e3-8ea8b69c8d84
  spec:
    sourcePod: network-check-source-65bdbbff45-lbbp7
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T03:56:21Z"
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.140259ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:56:21Z"
    - latency: 2.228279ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:55:21Z"
    - latency: 2.438404ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:54:21Z"
    - latency: 2.905535ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:53:21Z"
    - latency: 2.137409ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:52:21Z"
    - latency: 2.852712ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:51:21Z"
    - latency: 2.47385ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:50:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T03:49:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-175-to-network-check-target-ip-10-0-137-81
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-175.ec2.internal
      uid: 8b9ff4e3-a6d3-4bf0-80e3-f31f9e5fc2b6
    resourceVersion: "15171"
    uid: e566bf52-1687-416f-a329-a68136f14873
  spec:
    sourcePod: network-check-source-65bdbbff45-lbbp7
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T03:56:21Z"
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.887049ms
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:56:21Z"
    - latency: 1.883469ms
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:55:21Z"
    - latency: 6.683606ms
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:54:21Z"
    - latency: 2.660205ms
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:53:21Z"
    - latency: 14.704906ms
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:52:21Z"
    - latency: 1.919581ms
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:51:21Z"
    - latency: 2.022454ms
      message: 'network-check-target-ip-10-0-137-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:50:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T03:49:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-175-to-network-check-target-ip-10-0-143-175
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-175.ec2.internal
      uid: 8b9ff4e3-a6d3-4bf0-80e3-f31f9e5fc2b6
    resourceVersion: "15170"
    uid: 163c1261-b6a7-46af-8371-cc6e14d6a0ea
  spec:
    sourcePod: network-check-source-65bdbbff45-lbbp7
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T03:56:21Z"
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.13681ms
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:56:21Z"
    - latency: 990.239µs
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:55:21Z"
    - latency: 1.263381ms
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:54:21Z"
    - latency: 2.307295ms
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:53:21Z"
    - latency: 936.944µs
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:52:21Z"
    - latency: 1.048613ms
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:51:21Z"
    - latency: 1.210021ms
      message: 'network-check-target-ip-10-0-143-175: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:50:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-01T03:49:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-175-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-175.ec2.internal
      uid: 8b9ff4e3-a6d3-4bf0-80e3-f31f9e5fc2b6
    resourceVersion: "14834"
    uid: c262a902-ab6f-4bf8-96c4-0d91285513b8
  spec:
    sourcePod: network-check-source-65bdbbff45-lbbp7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-01T03:55:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.005793ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:55:21Z"
    - latency: 1.710821ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:55:21Z"
    - latency: 764.105µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:54:21Z"
    - latency: 1.799481ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:54:21Z"
    - latency: 1.108693ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:53:21Z"
    - latency: 2.611257ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:53:21Z"
    - latency: 909.855µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:52:21Z"
    - latency: 14.78866ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:52:21Z"
    - latency: 830.291µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T03:51:21Z"
    - latency: 1.788215ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T03:51:21Z"
kind: List
metadata:
  resourceVersion: ""