apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:19:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-2-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-2.ec2.internal
      uid: 00e3b873-60d6-4006-8df7-629d3d2feb7c
    resourceVersion: "23244"
    uid: 9cb61bd5-02b3-4d0e-8c96-7296b6e36633
  spec:
    sourcePod: network-check-source-8894fc9bd-tdbc5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T20:26:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 799.167µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:26:18Z"
    - latency: 1.077325ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:25:18Z"
    - latency: 912.342µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:24:18Z"
    - latency: 1.686851ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:23:18Z"
    - latency: 992.831µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:22:18Z"
    - latency: 1.533093ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:21:18Z"
    - latency: 1.15996ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:20:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:19:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-2-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-2.ec2.internal
      uid: 00e3b873-60d6-4006-8df7-629d3d2feb7c
    resourceVersion: "21933"
    uid: 00206698-ce91-40ed-94e2-991c953b0e77
  spec:
    sourcePod: network-check-source-8894fc9bd-tdbc5
    targetEndpoint: a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T20:25:18Z"
      message: 'load-balancer-api-external: tcp connection to a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.071675ms
      message: 'load-balancer-api-external: tcp connection to a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:25:18Z"
    - latency: 6.41761ms
      message: 'load-balancer-api-external: resolved host name a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:25:18Z"
    - latency: 3.651488ms
      message: 'load-balancer-api-external: tcp connection to a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:24:18Z"
    - latency: 6.416878ms
      message: 'load-balancer-api-external: resolved host name a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:24:18Z"
    - latency: 5.340829ms
      message: 'load-balancer-api-external: tcp connection to a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:23:18Z"
    - latency: 6.631607ms
      message: 'load-balancer-api-external: resolved host name a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:23:18Z"
    - latency: 4.22396ms
      message: 'load-balancer-api-external: tcp connection to a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:22:18Z"
    - latency: 6.593008ms
      message: 'load-balancer-api-external: resolved host name a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:22:18Z"
    - latency: 3.292395ms
      message: 'load-balancer-api-external: tcp connection to a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:21:18Z"
    - latency: 7.354683ms
      message: 'load-balancer-api-external: resolved host name a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:21:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:19:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-2-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-2.ec2.internal
      uid: 00e3b873-60d6-4006-8df7-629d3d2feb7c
    resourceVersion: "21934"
    uid: 0ef65ed0-672f-49a3-ad6d-c500ac927992
  spec:
    sourcePod: network-check-source-8894fc9bd-tdbc5
    targetEndpoint: a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T20:25:18Z"
      message: 'load-balancer-api-internal: tcp connection to a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.045514ms
      message: 'load-balancer-api-internal: tcp connection to a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:25:18Z"
    - latency: 6.373896ms
      message: 'load-balancer-api-internal: resolved host name a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:25:18Z"
    - latency: 5.823694ms
      message: 'load-balancer-api-internal: tcp connection to a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:24:18Z"
    - latency: 6.354354ms
      message: 'load-balancer-api-internal: resolved host name a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:24:18Z"
    - latency: 5.35417ms
      message: 'load-balancer-api-internal: tcp connection to a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:23:18Z"
    - latency: 6.561565ms
      message: 'load-balancer-api-internal: resolved host name a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:23:18Z"
    - latency: 4.31658ms
      message: 'load-balancer-api-internal: tcp connection to a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:22:18Z"
    - latency: 6.555766ms
      message: 'load-balancer-api-internal: resolved host name a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:22:18Z"
    - latency: 3.253576ms
      message: 'load-balancer-api-internal: tcp connection to a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:21:18Z"
    - latency: 7.310173ms
      message: 'load-balancer-api-internal: resolved host name a5beac1f15bbe4b4096174acc245bef4-a3858845a3722158.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:21:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:19:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-2-to-network-check-target-ip-10-0-129-50
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-2.ec2.internal
      uid: 00e3b873-60d6-4006-8df7-629d3d2feb7c
    resourceVersion: "23243"
    uid: 8faaaa03-057c-41a2-b7af-65a4593117d2
  spec:
    sourcePod: network-check-source-8894fc9bd-tdbc5
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T20:26:18Z"
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.221138ms
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:26:18Z"
    - latency: 2.353328ms
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:25:18Z"
    - latency: 2.079815ms
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:24:18Z"
    - latency: 2.202913ms
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:23:18Z"
    - latency: 2.406036ms
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:22:18Z"
    - latency: 2.679346ms
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:21:18Z"
    - latency: 2.352991ms
      message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:20:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:19:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-2-to-network-check-target-ip-10-0-132-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-2.ec2.internal
      uid: 00e3b873-60d6-4006-8df7-629d3d2feb7c
    resourceVersion: "23242"
    uid: 1ad6c440-d973-469d-bd56-244eddf81c66
  spec:
    sourcePod: network-check-source-8894fc9bd-tdbc5
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T20:26:18Z"
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.820259ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:26:18Z"
    - latency: 1.953904ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:25:18Z"
    - latency: 1.796707ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:24:18Z"
    - latency: 1.816047ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:23:18Z"
    - latency: 2.005909ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:22:18Z"
    - latency: 1.837112ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:21:18Z"
    - latency: 2.276503ms
      message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:20:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:19:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-2-to-network-check-target-ip-10-0-139-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-2.ec2.internal
      uid: 00e3b873-60d6-4006-8df7-629d3d2feb7c
    resourceVersion: "23241"
    uid: 7c084132-d096-45cb-83df-54f5041c897a
  spec:
    sourcePod: network-check-source-8894fc9bd-tdbc5
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T20:26:18Z"
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 856.338µs
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:26:18Z"
    - latency: 1.284502ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:25:18Z"
    - latency: 856.841µs
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:24:18Z"
    - latency: 2.089089ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:23:18Z"
    - latency: 823.751µs
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:22:18Z"
    - latency: 1.123115ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:21:18Z"
    - latency: 1.729958ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:20:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T20:19:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-2-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-2.ec2.internal
      uid: 00e3b873-60d6-4006-8df7-629d3d2feb7c
    resourceVersion: "21931"
    uid: abf2fa57-cca6-4288-8b02-8e4c3c43b298
  spec:
    sourcePod: network-check-source-8894fc9bd-tdbc5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T20:25:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.136183ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:25:18Z"
    - latency: 1.787304ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:25:18Z"
    - latency: 1.145021ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:24:18Z"
    - latency: 1.741159ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:24:18Z"
    - latency: 973.433µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:23:18Z"
    - latency: 1.655799ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:23:18Z"
    - latency: 806.736µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:22:18Z"
    - latency: 2.002764ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:22:18Z"
    - latency: 1.131871ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T20:21:18Z"
    - latency: 1.943573ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T20:21:18Z"
kind: List
metadata:
  resourceVersion: ""