apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:14:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-254-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-254.ec2.internal
      uid: e0fb8198-69f8-4fef-b89d-9a364d8cddde
    resourceVersion: "24638"
    uid: 1db14d55-a336-498b-abcb-2553b7f8e27e
  spec:
    sourcePod: network-check-source-685456655f-gvhzf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:21:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.143775ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:21:29Z"
    - latency: 1.062851ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:20:29Z"
    - latency: 1.039065ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:19:29Z"
    - latency: 1.272609ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:29Z"
    - latency: 1.052504ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:29Z"
    - latency: 937.733µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:29Z"
    - latency: 917.158µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:15:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:14:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-254-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-254.ec2.internal
      uid: e0fb8198-69f8-4fef-b89d-9a364d8cddde
    resourceVersion: "23393"
    uid: 0362184c-9bf1-4ae1-a5c3-7833c1b6bb7b
  spec:
    sourcePod: network-check-source-685456655f-gvhzf
    targetEndpoint: a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:20:29Z"
      message: 'load-balancer-api-external: tcp connection to a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.575307ms
      message: 'load-balancer-api-external: tcp connection to a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:20:29Z"
    - latency: 8.281112ms
      message: 'load-balancer-api-external: resolved host name a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:20:29Z"
    - latency: 5.141817ms
      message: 'load-balancer-api-external: tcp connection to a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:19:29Z"
    - latency: 10.339844ms
      message: 'load-balancer-api-external: resolved host name a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:19:29Z"
    - latency: 5.607524ms
      message: 'load-balancer-api-external: tcp connection to a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:29Z"
    - latency: 9.252146ms
      message: 'load-balancer-api-external: resolved host name a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:18:29Z"
    - latency: 5.291042ms
      message: 'load-balancer-api-external: tcp connection to a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:29Z"
    - latency: 8.674154ms
      message: 'load-balancer-api-external: resolved host name a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:17:29Z"
    - latency: 4.528333ms
      message: 'load-balancer-api-external: tcp connection to a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:29Z"
    - latency: 8.291426ms
      message: 'load-balancer-api-external: resolved host name a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:16:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:14:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-254-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-254.ec2.internal
      uid: e0fb8198-69f8-4fef-b89d-9a364d8cddde
    resourceVersion: "23392"
    uid: b3e80711-8ccc-4183-875e-dd3dfc37228c
  spec:
    sourcePod: network-check-source-685456655f-gvhzf
    targetEndpoint: a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:20:29Z"
      message: 'load-balancer-api-internal: tcp connection to a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.536812ms
      message: 'load-balancer-api-internal: tcp connection to a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:20:29Z"
    - latency: 8.371772ms
      message: 'load-balancer-api-internal: resolved host name a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:20:29Z"
    - latency: 5.138328ms
      message: 'load-balancer-api-internal: tcp connection to a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:19:29Z"
    - latency: 10.376874ms
      message: 'load-balancer-api-internal: resolved host name a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:19:29Z"
    - latency: 3.829517ms
      message: 'load-balancer-api-internal: tcp connection to a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:29Z"
    - latency: 9.222898ms
      message: 'load-balancer-api-internal: resolved host name a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:18:29Z"
    - latency: 4.847496ms
      message: 'load-balancer-api-internal: tcp connection to a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:29Z"
    - latency: 8.520486ms
      message: 'load-balancer-api-internal: resolved host name a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:17:29Z"
    - latency: 4.532567ms
      message: 'load-balancer-api-internal: tcp connection to a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:29Z"
    - latency: 8.091896ms
      message: 'load-balancer-api-internal: resolved host name a7ec2771d16f34f5b99f2e4b88e0bc60-693fbc8fe775c7cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:16:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:14:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-254-to-network-check-target-ip-10-0-130-254
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-254.ec2.internal
      uid: e0fb8198-69f8-4fef-b89d-9a364d8cddde
    resourceVersion: "24635"
    uid: c937a450-70bf-4551-9ea9-13be1e16c369
  spec:
    sourcePod: network-check-source-685456655f-gvhzf
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:21:29Z"
      message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.276271ms
      message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:21:29Z"
    - latency: 1.211186ms
      message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:20:29Z"
    - latency: 1.538373ms
      message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:19:29Z"
    - latency: 1.234881ms
      message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:29Z"
    - latency: 996.211µs
      message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:29Z"
    - latency: 1.336487ms
      message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:29Z"
    - latency: 1.183301ms
      message: 'network-check-target-ip-10-0-130-254: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:15:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:14:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-254-to-network-check-target-ip-10-0-138-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-254.ec2.internal
      uid: e0fb8198-69f8-4fef-b89d-9a364d8cddde
    resourceVersion: "24636"
    uid: ae87e4e8-9951-4f68-b012-827750ed7ffb
  spec:
    sourcePod: network-check-source-685456655f-gvhzf
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:21:29Z"
      message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.260117ms
      message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:21:29Z"
    - latency: 2.108108ms
      message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:20:29Z"
    - latency: 2.383667ms
      message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:19:29Z"
    - latency: 2.211493ms
      message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:29Z"
    - latency: 2.18107ms
      message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:29Z"
    - latency: 1.94226ms
      message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:29Z"
    - latency: 6.360447ms
      message: 'network-check-target-ip-10-0-138-84: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:15:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:14:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-254-to-network-check-target-ip-10-0-143-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-254.ec2.internal
      uid: e0fb8198-69f8-4fef-b89d-9a364d8cddde
    resourceVersion: "24637"
    uid: 29314a23-6d4b-4afb-b1a2-92af789eccae
  spec:
    sourcePod: network-check-source-685456655f-gvhzf
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:21:29Z"
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.749345ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:21:29Z"
    - latency: 2.538167ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:20:29Z"
    - latency: 2.559553ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:19:29Z"
    - latency: 2.610078ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:29Z"
    - latency: 2.590106ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:29Z"
    - latency: 2.510577ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:29Z"
    - latency: 5.182995ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:15:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:14:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-254-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-254.ec2.internal
      uid: e0fb8198-69f8-4fef-b89d-9a364d8cddde
    resourceVersion: "23391"
    uid: a3d21d2d-e851-459e-885f-2e08e47b126a
  spec:
    sourcePod: network-check-source-685456655f-gvhzf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:20:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 974.76µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:20:29Z"
    - latency: 1.880333ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:20:29Z"
    - latency: 841.109µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:19:29Z"
    - latency: 1.822958ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:19:29Z"
    - latency: 879.157µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:29Z"
    - latency: 2.118135ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:18:29Z"
    - latency: 993.49µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:29Z"
    - latency: 1.784023ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:17:29Z"
    - latency: 834.169µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:29Z"
    - latency: 1.681238ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:16:29Z"
kind: List
metadata:
  resourceVersion: ""