apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:19:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-99-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-99.ec2.internal
      uid: 8a6b2f24-a5ec-4409-9064-0e7d85b97f8d
    resourceVersion: "14331"
    uid: 2e8d24fc-91cf-4d5d-8d66-69434c8c095f
  spec:
    sourcePod: network-check-source-685456655f-fhnwj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:26:34Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.006116ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:34Z"
    - latency: 1.404355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:34Z"
    - latency: 922.537µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:34Z"
    - latency: 874.425µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:34Z"
    - latency: 752.633µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:22:34Z"
    - latency: 1.110136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:21:34Z"
    - latency: 941.867µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:20:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:19:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-99-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-99.ec2.internal
      uid: 8a6b2f24-a5ec-4409-9064-0e7d85b97f8d
    resourceVersion: "13938"
    uid: 655e62d6-b8f9-419c-860f-e631ba9be8d3
  spec:
    sourcePod: network-check-source-685456655f-fhnwj
    targetEndpoint: a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:25:34Z"
      message: 'load-balancer-api-external: tcp connection to a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.060194ms
      message: 'load-balancer-api-external: tcp connection to a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:34Z"
    - latency: 7.759946ms
      message: 'load-balancer-api-external: resolved host name a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:25:34Z"
    - latency: 5.624897ms
      message: 'load-balancer-api-external: tcp connection to a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:34Z"
    - latency: 7.783222ms
      message: 'load-balancer-api-external: resolved host name a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:24:34Z"
    - latency: 5.961388ms
      message: 'load-balancer-api-external: tcp connection to a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:34Z"
    - latency: 7.768197ms
      message: 'load-balancer-api-external: resolved host name a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:23:34Z"
    - latency: 4.446071ms
      message: 'load-balancer-api-external: tcp connection to a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:22:34Z"
    - latency: 8.488294ms
      message: 'load-balancer-api-external: resolved host name a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:22:34Z"
    - latency: 4.685942ms
      message: 'load-balancer-api-external: tcp connection to a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:21:34Z"
    - latency: 7.479446ms
      message: 'load-balancer-api-external: resolved host name a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:21:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:19:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-99-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-99.ec2.internal
      uid: 8a6b2f24-a5ec-4409-9064-0e7d85b97f8d
    resourceVersion: "13939"
    uid: d77b6bf9-a14f-4879-9fe2-8e3e2bf41c24
  spec:
    sourcePod: network-check-source-685456655f-fhnwj
    targetEndpoint: a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:25:34Z"
      message: 'load-balancer-api-internal: tcp connection to a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.001208ms
      message: 'load-balancer-api-internal: tcp connection to a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:34Z"
    - latency: 7.864537ms
      message: 'load-balancer-api-internal: resolved host name a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:25:34Z"
    - latency: 5.619774ms
      message: 'load-balancer-api-internal: tcp connection to a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:34Z"
    - latency: 7.841006ms
      message: 'load-balancer-api-internal: resolved host name a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:24:34Z"
    - latency: 5.584925ms
      message: 'load-balancer-api-internal: tcp connection to a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:34Z"
    - latency: 7.843843ms
      message: 'load-balancer-api-internal: resolved host name a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:23:34Z"
    - latency: 4.476426ms
      message: 'load-balancer-api-internal: tcp connection to a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:22:34Z"
    - latency: 8.489555ms
      message: 'load-balancer-api-internal: resolved host name a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:22:34Z"
    - latency: 6.757386ms
      message: 'load-balancer-api-internal: tcp connection to a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:21:34Z"
    - latency: 7.574101ms
      message: 'load-balancer-api-internal: resolved host name a4ee2d7b313404337bf4946829ae1054-7979c980131013d5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:21:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:19:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-99-to-network-check-target-ip-10-0-129-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-99.ec2.internal
      uid: 8a6b2f24-a5ec-4409-9064-0e7d85b97f8d
    resourceVersion: "14329"
    uid: c68bbc91-67e5-430f-aab4-9b7305549e2b
  spec:
    sourcePod: network-check-source-685456655f-fhnwj
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:26:34Z"
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.140512ms
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:34Z"
    - latency: 2.061867ms
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:34Z"
    - latency: 2.013028ms
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:34Z"
    - latency: 2.101268ms
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:34Z"
    - latency: 1.949434ms
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:22:34Z"
    - latency: 1.938636ms
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:21:34Z"
    - latency: 2.213752ms
      message: 'network-check-target-ip-10-0-129-35: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:20:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:19:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-99-to-network-check-target-ip-10-0-137-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-99.ec2.internal
      uid: 8a6b2f24-a5ec-4409-9064-0e7d85b97f8d
    resourceVersion: "14330"
    uid: 19ca2592-b9cb-4034-99be-12129b4423f5
  spec:
    sourcePod: network-check-source-685456655f-fhnwj
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:26:34Z"
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.148516ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:34Z"
    - latency: 2.253745ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:34Z"
    - latency: 2.41912ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:34Z"
    - latency: 2.054419ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:34Z"
    - latency: 2.049863ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:22:34Z"
    - latency: 2.21343ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:21:34Z"
    - latency: 2.665839ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:20:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:19:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-99-to-network-check-target-ip-10-0-143-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-99.ec2.internal
      uid: 8a6b2f24-a5ec-4409-9064-0e7d85b97f8d
    resourceVersion: "14328"
    uid: e9e87c4d-a3c5-4013-8dc4-538c393353e2
  spec:
    sourcePod: network-check-source-685456655f-fhnwj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:26:34Z"
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 937.08µs
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:34Z"
    - latency: 1.626322ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:34Z"
    - latency: 953.314µs
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:34Z"
    - latency: 877.943µs
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:34Z"
    - latency: 950.671µs
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:22:34Z"
    - latency: 1.118856ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:21:34Z"
    - latency: 1.219718ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:20:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T13:19:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-99-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-99.ec2.internal
      uid: 8a6b2f24-a5ec-4409-9064-0e7d85b97f8d
    resourceVersion: "13937"
    uid: 2813b358-b1f5-4e3c-81fa-3492ed561d4b
  spec:
    sourcePod: network-check-source-685456655f-fhnwj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:25:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 950.439µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:34Z"
    - latency: 1.674336ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:25:34Z"
    - latency: 963.952µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:34Z"
    - latency: 1.657498ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:24:34Z"
    - latency: 1.244633ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:34Z"
    - latency: 1.671831ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:23:34Z"
    - latency: 901.231µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:22:34Z"
    - latency: 1.677676ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:22:34Z"
    - latency: 823.621µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:21:34Z"
    - latency: 1.744333ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:21:34Z"
kind: List
metadata:
  resourceVersion: ""