apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T09:01:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-114-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-114.ec2.internal
      uid: 746654f1-bf4a-41e4-97be-14da862a7776
    resourceVersion: "15090"
    uid: b6a424b0-ebc9-45bc-a3e8-11b5b9bbafe7
  spec:
    sourcePod: network-check-source-6f8b768455-td2bq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T09:08:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.081883ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:08:32Z"
    - latency: 1.357993ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:07:32Z"
    - latency: 1.043913ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:06:32Z"
    - latency: 1.038083ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:05:32Z"
    - latency: 1.03439ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:04:32Z"
    - latency: 965.532µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:03:32Z"
    - latency: 1.055399ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:02:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T09:01:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-114-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-114.ec2.internal
      uid: 746654f1-bf4a-41e4-97be-14da862a7776
    resourceVersion: "14673"
    uid: 8e305518-4203-4400-9643-04dc8fa91ef0
  spec:
    sourcePod: network-check-source-6f8b768455-td2bq
    targetEndpoint: a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T09:07:32Z"
      message: 'load-balancer-api-external: tcp connection to a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.220368ms
      message: 'load-balancer-api-external: tcp connection to a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:07:32Z"
    - latency: 8.640272ms
      message: 'load-balancer-api-external: resolved host name a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T09:07:32Z"
    - latency: 5.636801ms
      message: 'load-balancer-api-external: tcp connection to a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:06:32Z"
    - latency: 8.391401ms
      message: 'load-balancer-api-external: resolved host name a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T09:06:32Z"
    - latency: 3.412927ms
      message: 'load-balancer-api-external: tcp connection to a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:05:32Z"
    - latency: 8.815876ms
      message: 'load-balancer-api-external: resolved host name a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T09:05:32Z"
    - latency: 4.102627ms
      message: 'load-balancer-api-external: tcp connection to a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:04:32Z"
    - latency: 7.68955ms
      message: 'load-balancer-api-external: resolved host name a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T09:04:32Z"
    - latency: 5.137034ms
      message: 'load-balancer-api-external: tcp connection to a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:03:32Z"
    - latency: 13.199533ms
      message: 'load-balancer-api-external: resolved host name a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T09:03:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T09:01:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-114-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-114.ec2.internal
      uid: 746654f1-bf4a-41e4-97be-14da862a7776
    resourceVersion: "14672"
    uid: e632141d-97f1-4936-a82b-f3129931c42f
  spec:
    sourcePod: network-check-source-6f8b768455-td2bq
    targetEndpoint: a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T09:07:32Z"
      message: 'load-balancer-api-internal: tcp connection to a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.128084ms
      message: 'load-balancer-api-internal: tcp connection to a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:07:32Z"
    - latency: 8.719901ms
      message: 'load-balancer-api-internal: resolved host name a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T09:07:32Z"
    - latency: 3.595098ms
      message: 'load-balancer-api-internal: tcp connection to a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:06:32Z"
    - latency: 8.525922ms
      message: 'load-balancer-api-internal: resolved host name a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T09:06:32Z"
    - latency: 5.270708ms
      message: 'load-balancer-api-internal: tcp connection to a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:05:32Z"
    - latency: 8.910593ms
      message: 'load-balancer-api-internal: resolved host name a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T09:05:32Z"
    - latency: 4.071322ms
      message: 'load-balancer-api-internal: tcp connection to a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:04:32Z"
    - latency: 7.588792ms
      message: 'load-balancer-api-internal: resolved host name a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T09:04:32Z"
    - latency: 5.138944ms
      message: 'load-balancer-api-internal: tcp connection to a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:03:32Z"
    - latency: 13.301117ms
      message: 'load-balancer-api-internal: resolved host name a4af1b78ebb9747fa93cf347e4ddb0e3-1e204aa56256510e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T09:03:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T09:01:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-114-to-network-check-target-ip-10-0-136-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-114.ec2.internal
      uid: 746654f1-bf4a-41e4-97be-14da862a7776
    resourceVersion: "15089"
    uid: c3003404-f4af-44b6-9a73-7130985db10d
  spec:
    sourcePod: network-check-source-6f8b768455-td2bq
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T09:08:32Z"
      message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.221381ms
      message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:08:32Z"
    - latency: 2.030467ms
      message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:07:32Z"
    - latency: 2.138449ms
      message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:06:32Z"
    - latency: 2.346968ms
      message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:05:32Z"
    - latency: 2.516784ms
      message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:04:32Z"
    - latency: 5.753933ms
      message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:03:32Z"
    - latency: 2.124145ms
      message: 'network-check-target-ip-10-0-136-94: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:02:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T09:01:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-114-to-network-check-target-ip-10-0-137-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-114.ec2.internal
      uid: 746654f1-bf4a-41e4-97be-14da862a7776
    resourceVersion: "15087"
    uid: e7df3738-777e-4e92-81c8-84144719edf0
  spec:
    sourcePod: network-check-source-6f8b768455-td2bq
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T09:08:32Z"
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.234191ms
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:08:32Z"
    - latency: 1.159859ms
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:07:32Z"
    - latency: 887.977µs
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:06:32Z"
    - latency: 924.133µs
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:05:32Z"
    - latency: 850.317µs
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:04:32Z"
    - latency: 868.606µs
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:03:32Z"
    - latency: 1.211504ms
      message: 'network-check-target-ip-10-0-137-114: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:02:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T09:01:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-114-to-network-check-target-ip-10-0-141-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-114.ec2.internal
      uid: 746654f1-bf4a-41e4-97be-14da862a7776
    resourceVersion: "15088"
    uid: c22b5de2-bd8b-4250-9b92-0da133b26d85
  spec:
    sourcePod: network-check-source-6f8b768455-td2bq
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T09:08:32Z"
      message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.267255ms
      message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:08:32Z"
    - latency: 2.082351ms
      message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:07:32Z"
    - latency: 2.052202ms
      message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:06:32Z"
    - latency: 2.052016ms
      message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:05:32Z"
    - latency: 2.045444ms
      message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:04:32Z"
    - latency: 1.924922ms
      message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:03:32Z"
    - latency: 1.821758ms
      message: 'network-check-target-ip-10-0-141-124: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:02:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T09:01:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-114-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-114.ec2.internal
      uid: 746654f1-bf4a-41e4-97be-14da862a7776
    resourceVersion: "14671"
    uid: c1aeb56e-21bf-483e-bf29-3ac4418d2ad8
  spec:
    sourcePod: network-check-source-6f8b768455-td2bq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T09:07:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 706.903µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:07:32Z"
    - latency: 2.008387ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T09:07:32Z"
    - latency: 1.124933ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:06:32Z"
    - latency: 1.795014ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T09:06:32Z"
    - latency: 936.665µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:05:32Z"
    - latency: 1.766122ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T09:05:32Z"
    - latency: 979.311µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:04:32Z"
    - latency: 1.708669ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T09:04:32Z"
    - latency: 797.634µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T09:03:32Z"
    - latency: 5.787657ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T09:03:32Z"
kind: List
metadata:
  resourceVersion: ""