apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T19:14:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-110-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-110.ec2.internal
      uid: 7f9dd976-ea7d-45e6-b218-62fd666cec31
    resourceVersion: "25491"
    uid: f187a8d5-bfe7-4ada-904d-a9393430e1bf
  spec:
    sourcePod: network-check-source-8894fc9bd-jkvx4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T19:21:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.005612ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:21:44Z"
    - latency: 1.434402ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:20:44Z"
    - latency: 1.06305ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:19:44Z"
    - latency: 1.818634ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:18:44Z"
    - latency: 860.894µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:17:44Z"
    - latency: 932.176µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:16:44Z"
    - latency: 1.305691ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:15:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T19:14:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-110-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-110.ec2.internal
      uid: 7f9dd976-ea7d-45e6-b218-62fd666cec31
    resourceVersion: "24448"
    uid: f587dabe-5cfa-4258-bad1-5d7bdd43be16
  spec:
    sourcePod: network-check-source-8894fc9bd-jkvx4
    targetEndpoint: aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T19:20:44Z"
      message: 'load-balancer-api-external: tcp connection to aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.578791ms
      message: 'load-balancer-api-external: tcp connection to aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:20:44Z"
    - latency: 8.058175ms
      message: 'load-balancer-api-external: resolved host name aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:20:44Z"
    - latency: 4.159874ms
      message: 'load-balancer-api-external: tcp connection to aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:19:44Z"
    - latency: 7.952833ms
      message: 'load-balancer-api-external: resolved host name aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:19:44Z"
    - latency: 4.595307ms
      message: 'load-balancer-api-external: tcp connection to aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:18:44Z"
    - latency: 10.253985ms
      message: 'load-balancer-api-external: resolved host name aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:18:44Z"
    - latency: 4.869325ms
      message: 'load-balancer-api-external: tcp connection to aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:17:44Z"
    - latency: 8.017483ms
      message: 'load-balancer-api-external: resolved host name aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:17:44Z"
    - latency: 5.248889ms
      message: 'load-balancer-api-external: tcp connection to aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:16:44Z"
    - latency: 7.506492ms
      message: 'load-balancer-api-external: resolved host name aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:16:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T19:14:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-110-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-110.ec2.internal
      uid: 7f9dd976-ea7d-45e6-b218-62fd666cec31
    resourceVersion: "24449"
    uid: 2f3e73ba-027c-4870-ba3c-4113442e85a9
  spec:
    sourcePod: network-check-source-8894fc9bd-jkvx4
    targetEndpoint: aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T19:20:44Z"
      message: 'load-balancer-api-internal: tcp connection to aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.63278ms
      message: 'load-balancer-api-internal: tcp connection to aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:20:44Z"
    - latency: 8.02548ms
      message: 'load-balancer-api-internal: resolved host name aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:20:44Z"
    - latency: 3.609782ms
      message: 'load-balancer-api-internal: tcp connection to aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:19:44Z"
    - latency: 8.042067ms
      message: 'load-balancer-api-internal: resolved host name aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:19:44Z"
    - latency: 4.227132ms
      message: 'load-balancer-api-internal: tcp connection to aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:18:44Z"
    - latency: 10.179278ms
      message: 'load-balancer-api-internal: resolved host name aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:18:44Z"
    - latency: 4.861827ms
      message: 'load-balancer-api-internal: tcp connection to aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:17:44Z"
    - latency: 7.966361ms
      message: 'load-balancer-api-internal: resolved host name aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:17:44Z"
    - latency: 5.099788ms
      message: 'load-balancer-api-internal: tcp connection to aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:16:44Z"
    - latency: 7.412708ms
      message: 'load-balancer-api-internal: resolved host name aeb998fc37af245b284820fd0f07c71a-e1ed2f3214edb752.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:16:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T19:14:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-110-to-network-check-target-ip-10-0-129-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-110.ec2.internal
      uid: 7f9dd976-ea7d-45e6-b218-62fd666cec31
    resourceVersion: "25488"
    uid: b140c594-beb1-4512-90e1-b99a4bf57c8b
  spec:
    sourcePod: network-check-source-8894fc9bd-jkvx4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T19:21:44Z"
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.390257ms
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:21:44Z"
    - latency: 652.684µs
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:20:44Z"
    - latency: 740.292µs
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:19:44Z"
    - latency: 1.646513ms
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:18:44Z"
    - latency: 728.119µs
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:17:44Z"
    - latency: 822.129µs
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:16:44Z"
    - latency: 1.103255ms
      message: 'network-check-target-ip-10-0-129-110: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:15:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T19:14:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-110-to-network-check-target-ip-10-0-134-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-110.ec2.internal
      uid: 7f9dd976-ea7d-45e6-b218-62fd666cec31
    resourceVersion: "25489"
    uid: d5caaccc-dd5d-4bd8-9e88-2191e77fdb22
  spec:
    sourcePod: network-check-source-8894fc9bd-jkvx4
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T19:21:44Z"
      message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.953907ms
      message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:21:44Z"
    - latency: 2.045487ms
      message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:20:44Z"
    - latency: 2.105175ms
      message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:19:44Z"
    - latency: 2.917566ms
      message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:18:44Z"
    - latency: 1.8744ms
      message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:17:44Z"
    - latency: 1.946008ms
      message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:16:44Z"
    - latency: 2.347991ms
      message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:15:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T19:14:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-110-to-network-check-target-ip-10-0-141-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-110.ec2.internal
      uid: 7f9dd976-ea7d-45e6-b218-62fd666cec31
    resourceVersion: "25490"
    uid: d0a4cbce-76c7-4618-bdf6-c7518e8b0fae
  spec:
    sourcePod: network-check-source-8894fc9bd-jkvx4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T19:21:44Z"
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.706613ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:21:44Z"
    - latency: 2.141524ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:20:44Z"
    - latency: 2.066114ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:19:44Z"
    - latency: 2.533394ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:18:44Z"
    - latency: 1.915528ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:17:44Z"
    - latency: 1.847185ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:16:44Z"
    - latency: 2.366127ms
      message: 'network-check-target-ip-10-0-141-191: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:15:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T19:14:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-110-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-110.ec2.internal
      uid: 7f9dd976-ea7d-45e6-b218-62fd666cec31
    resourceVersion: "24447"
    uid: fc235e64-ef97-4cea-9ef0-712ca8b87e0b
  spec:
    sourcePod: network-check-source-8894fc9bd-jkvx4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T19:20:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 879.987µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:20:44Z"
    - latency: 1.67048ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:20:44Z"
    - latency: 1.155595ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:19:44Z"
    - latency: 1.706531ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:19:44Z"
    - latency: 1.358628ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:18:44Z"
    - latency: 2.517823ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:18:44Z"
    - latency: 813.623µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:17:44Z"
    - latency: 1.579852ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:17:44Z"
    - latency: 766.334µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T19:16:44Z"
    - latency: 1.677064ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T19:16:44Z"
kind: List
metadata:
  resourceVersion: ""