apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T14:20:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-105-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-105.ec2.internal
      uid: 52f043e3-0fe0-4977-8ea1-370f26015c09
    resourceVersion: "15001"
    uid: ebfa87e9-6cbf-486c-9eb5-c441c27b0651
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h56gk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T14:27:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.991596ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:27:34Z"
    - latency: 1.380144ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:26:34Z"
    - latency: 842.979µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:25:34Z"
    - latency: 953.235µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:24:34Z"
    - latency: 1.183176ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:23:34Z"
    - latency: 951.02µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:22:34Z"
    - latency: 1.062195ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:21:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T14:20:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-105-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-105.ec2.internal
      uid: 52f043e3-0fe0-4977-8ea1-370f26015c09
    resourceVersion: "17246"
    uid: 87c8f04b-08ef-47a3-b9dd-e141d77aed7e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h56gk
    targetEndpoint: a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T14:26:35Z"
      message: 'load-balancer-api-external: tcp connection to a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.223744ms
      message: 'load-balancer-api-external: tcp connection to a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:32:35Z"
    - latency: 7.793097ms
      message: 'load-balancer-api-external: resolved host name a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T14:32:34Z"
    - latency: 3.843299ms
      message: 'load-balancer-api-external: tcp connection to a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:31:35Z"
    - latency: 7.726343ms
      message: 'load-balancer-api-external: resolved host name a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T14:31:34Z"
    - latency: 5.965728ms
      message: 'load-balancer-api-external: tcp connection to a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:30:35Z"
    - latency: 8.926183ms
      message: 'load-balancer-api-external: resolved host name a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T14:30:34Z"
    - latency: 5.387653ms
      message: 'load-balancer-api-external: tcp connection to a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:29:35Z"
    - latency: 9.158223ms
      message: 'load-balancer-api-external: resolved host name a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T14:29:34Z"
    - latency: 4.455585ms
      message: 'load-balancer-api-external: tcp connection to a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:28:35Z"
    - latency: 7.017226ms
      message: 'load-balancer-api-external: resolved host name a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T14:28:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T14:20:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-105-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-105.ec2.internal
      uid: 52f043e3-0fe0-4977-8ea1-370f26015c09
    resourceVersion: "17245"
    uid: 6dc59ebd-1416-44cd-9d67-44e796d22e59
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h56gk
    targetEndpoint: a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T14:26:35Z"
      message: 'load-balancer-api-internal: tcp connection to a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.273297ms
      message: 'load-balancer-api-internal: tcp connection to a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:32:35Z"
    - latency: 7.760978ms
      message: 'load-balancer-api-internal: resolved host name a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T14:32:34Z"
    - latency: 3.775174ms
      message: 'load-balancer-api-internal: tcp connection to a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:31:35Z"
    - latency: 7.695595ms
      message: 'load-balancer-api-internal: resolved host name a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T14:31:34Z"
    - latency: 6.039382ms
      message: 'load-balancer-api-internal: tcp connection to a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:30:35Z"
    - latency: 8.898469ms
      message: 'load-balancer-api-internal: resolved host name a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T14:30:34Z"
    - latency: 5.43908ms
      message: 'load-balancer-api-internal: tcp connection to a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:29:35Z"
    - latency: 9.14862ms
      message: 'load-balancer-api-internal: resolved host name a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T14:29:34Z"
    - latency: 21.401729ms
      message: 'load-balancer-api-internal: tcp connection to a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:28:35Z"
    - latency: 6.98951ms
      message: 'load-balancer-api-internal: resolved host name a6a2c3df5890f48d1941d02e8f06359c-444d4b78e991c08b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T14:28:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T14:20:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-105-to-network-check-target-ip-10-0-128-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-105.ec2.internal
      uid: 52f043e3-0fe0-4977-8ea1-370f26015c09
    resourceVersion: "14998"
    uid: 8612c60a-06e5-4365-9409-487a93d3de7f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h56gk
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T14:27:35Z"
      message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.530417ms
      message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:27:34Z"
    - latency: 2.339918ms
      message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:26:34Z"
    - latency: 2.191694ms
      message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:25:34Z"
    - latency: 2.075972ms
      message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:24:34Z"
    - latency: 2.429891ms
      message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:23:34Z"
    - latency: 2.885072ms
      message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:22:34Z"
    - latency: 2.452281ms
      message: 'network-check-target-ip-10-0-128-86: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:21:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T14:20:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-105-to-network-check-target-ip-10-0-129-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-105.ec2.internal
      uid: 52f043e3-0fe0-4977-8ea1-370f26015c09
    resourceVersion: "15000"
    uid: f9ba135a-9338-4f26-a916-f3b5e8fe7486
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h56gk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T14:27:35Z"
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.403213ms
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:27:34Z"
    - latency: 2.3639ms
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:26:34Z"
    - latency: 1.791718ms
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:25:34Z"
    - latency: 1.923579ms
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:24:34Z"
    - latency: 1.963797ms
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:23:34Z"
    - latency: 2.109433ms
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:22:34Z"
    - latency: 2.306234ms
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:21:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T14:20:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-105-to-network-check-target-ip-10-0-131-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-105.ec2.internal
      uid: 52f043e3-0fe0-4977-8ea1-370f26015c09
    resourceVersion: "14999"
    uid: 2e91555e-5b9e-4e58-949d-c9d579d10bb4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h56gk
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T14:27:35Z"
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.051283ms
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:27:34Z"
    - latency: 1.647984ms
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:26:34Z"
    - latency: 747.924µs
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:25:34Z"
    - latency: 790.965µs
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:24:34Z"
    - latency: 931.007µs
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:23:34Z"
    - latency: 849.181µs
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:22:34Z"
    - latency: 1.027274ms
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:21:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T14:20:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-105-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-105.ec2.internal
      uid: 52f043e3-0fe0-4977-8ea1-370f26015c09
    resourceVersion: "17244"
    uid: 54f316a4-f868-47e8-adb2-18b81fcda701
  spec:
    sourcePod: network-check-source-7bc5b6bf85-h56gk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T14:26:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 775.305µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:32:34Z"
    - latency: 1.604481ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T14:32:34Z"
    - latency: 1.000487ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:31:35Z"
    - latency: 1.936832ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T14:31:34Z"
    - latency: 782.609µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:30:35Z"
    - latency: 1.986888ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T14:30:34Z"
    - latency: 793.29µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:29:35Z"
    - latency: 2.499858ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T14:29:34Z"
    - latency: 969.69µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T14:28:35Z"
    - latency: 1.641867ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T14:28:34Z"
kind: List
metadata:
  resourceVersion: ""