apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-63-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-63.ec2.internal
      uid: 0afa9b6b-578a-4086-bac1-c8308d00da4e
    resourceVersion: "15119"
    uid: 6fa3e42f-84bd-4254-8379-1e3a64890e92
  spec:
    sourcePod: network-check-source-685456655f-4c89m
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:52:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.574078ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:52:33Z"
    - latency: 1.245591ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:51:33Z"
    - latency: 897.34µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:50:33Z"
    - latency: 1.368643ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:49:33Z"
    - latency: 969.827µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:33Z"
    - latency: 852.969µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:33Z"
    - latency: 909.355µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-63-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-63.ec2.internal
      uid: 0afa9b6b-578a-4086-bac1-c8308d00da4e
    resourceVersion: "14776"
    uid: 772700c2-5801-4d77-932b-35efe7415fb5
  spec:
    sourcePod: network-check-source-685456655f-4c89m
    targetEndpoint: a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:51:33Z"
      message: 'load-balancer-api-external: tcp connection to a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.267538ms
      message: 'load-balancer-api-external: tcp connection to a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:51:33Z"
    - latency: 7.181569ms
      message: 'load-balancer-api-external: resolved host name a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:51:33Z"
    - latency: 4.90093ms
      message: 'load-balancer-api-external: tcp connection to a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:50:33Z"
    - latency: 6.891948ms
      message: 'load-balancer-api-external: resolved host name a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:50:33Z"
    - latency: 4.683167ms
      message: 'load-balancer-api-external: tcp connection to a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:49:33Z"
    - latency: 6.576603ms
      message: 'load-balancer-api-external: resolved host name a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:49:33Z"
    - latency: 3.550093ms
      message: 'load-balancer-api-external: tcp connection to a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:33Z"
    - latency: 6.265613ms
      message: 'load-balancer-api-external: resolved host name a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:48:33Z"
    - latency: 4.565461ms
      message: 'load-balancer-api-external: tcp connection to a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:33Z"
    - latency: 6.552083ms
      message: 'load-balancer-api-external: resolved host name a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:47:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-63-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-63.ec2.internal
      uid: 0afa9b6b-578a-4086-bac1-c8308d00da4e
    resourceVersion: "14777"
    uid: 01e1a0ca-4c9a-49a7-a48d-1ad6ed641728
  spec:
    sourcePod: network-check-source-685456655f-4c89m
    targetEndpoint: a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:51:33Z"
      message: 'load-balancer-api-internal: tcp connection to a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.641668ms
      message: 'load-balancer-api-internal: tcp connection to a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:51:33Z"
    - latency: 7.14105ms
      message: 'load-balancer-api-internal: resolved host name a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:51:33Z"
    - latency: 4.904802ms
      message: 'load-balancer-api-internal: tcp connection to a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:50:33Z"
    - latency: 6.940336ms
      message: 'load-balancer-api-internal: resolved host name a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:50:33Z"
    - latency: 4.666418ms
      message: 'load-balancer-api-internal: tcp connection to a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:49:33Z"
    - latency: 6.517561ms
      message: 'load-balancer-api-internal: resolved host name a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:49:33Z"
    - latency: 3.578209ms
      message: 'load-balancer-api-internal: tcp connection to a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:33Z"
    - latency: 6.234154ms
      message: 'load-balancer-api-internal: resolved host name a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:48:33Z"
    - latency: 4.550221ms
      message: 'load-balancer-api-internal: tcp connection to a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:33Z"
    - latency: 6.472866ms
      message: 'load-balancer-api-internal: resolved host name a8a3480d5df844d8c912e3d6136c78b9-4e5dc92e291acd94.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:47:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-63-to-network-check-target-ip-10-0-139-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-63.ec2.internal
      uid: 0afa9b6b-578a-4086-bac1-c8308d00da4e
    resourceVersion: "15118"
    uid: 0ccff31a-a604-42f1-93a2-3e103a199da2
  spec:
    sourcePod: network-check-source-685456655f-4c89m
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:52:33Z"
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.096218ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:52:33Z"
    - latency: 2.237679ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:51:33Z"
    - latency: 2.239682ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:50:33Z"
    - latency: 2.105581ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:49:33Z"
    - latency: 2.276222ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:33Z"
    - latency: 1.886713ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:33Z"
    - latency: 2.373165ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-63-to-network-check-target-ip-10-0-139-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-63.ec2.internal
      uid: 0afa9b6b-578a-4086-bac1-c8308d00da4e
    resourceVersion: "15117"
    uid: 63d659be-ee2c-4c1c-bb8c-f5ea5ae2b2d2
  spec:
    sourcePod: network-check-source-685456655f-4c89m
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:52:33Z"
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.548008ms
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:52:33Z"
    - latency: 1.861334ms
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:51:33Z"
    - latency: 1.82745ms
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:50:33Z"
    - latency: 1.999183ms
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:49:33Z"
    - latency: 2.033802ms
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:33Z"
    - latency: 1.912063ms
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:33Z"
    - latency: 2.000001ms
      message: 'network-check-target-ip-10-0-139-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-63-to-network-check-target-ip-10-0-142-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-63.ec2.internal
      uid: 0afa9b6b-578a-4086-bac1-c8308d00da4e
    resourceVersion: "15116"
    uid: 64b33856-2657-47af-8168-b14d17f5da96
  spec:
    sourcePod: network-check-source-685456655f-4c89m
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:52:33Z"
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.774293ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:52:33Z"
    - latency: 1.033536ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:51:33Z"
    - latency: 1.103887ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:50:33Z"
    - latency: 1.047109ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:49:33Z"
    - latency: 1.147093ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:33Z"
    - latency: 843.49µs
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:33Z"
    - latency: 1.575867ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:46:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-63-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-63.ec2.internal
      uid: 0afa9b6b-578a-4086-bac1-c8308d00da4e
    resourceVersion: "14775"
    uid: 859c26cc-f7d7-4ddd-99f1-50e7cfdd99c9
  spec:
    sourcePod: network-check-source-685456655f-4c89m
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T12:51:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.113483ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:51:33Z"
    - latency: 1.895228ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:51:33Z"
    - latency: 768.61µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:50:33Z"
    - latency: 1.852334ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:50:33Z"
    - latency: 990.477µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:49:33Z"
    - latency: 1.99186ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:49:33Z"
    - latency: 1.174945ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:48:33Z"
    - latency: 2.071617ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:48:33Z"
    - latency: 1.007331ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T12:47:33Z"
    - latency: 1.94098ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T12:47:33Z"
kind: List
metadata:
  resourceVersion: ""