apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:33:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-36-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-36.ec2.internal
      uid: 34724d7e-2de1-4afa-b6bc-9b7ab9b68818
    resourceVersion: "15895"
    uid: 0daf1596-014b-42ed-8cc9-a79cfaad21fc
  spec:
    sourcePod: network-check-source-dbd9cf844-4g9pl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:40:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.348201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:40:02Z"
    - latency: 937.324µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:39:02Z"
    - latency: 921.468µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:38:02Z"
    - latency: 1.342387ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:37:02Z"
    - latency: 1.312388ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:36:02Z"
    - latency: 890.863µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:35:02Z"
    - latency: 905.857µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:34:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:33:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-36-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-36.ec2.internal
      uid: 34724d7e-2de1-4afa-b6bc-9b7ab9b68818
    resourceVersion: "15562"
    uid: 7e9da63c-52db-48cb-9bd8-d8d2bb828182
  spec:
    sourcePod: network-check-source-dbd9cf844-4g9pl
    targetEndpoint: a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:39:02Z"
      message: 'load-balancer-api-external: tcp connection to a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.045528ms
      message: 'load-balancer-api-external: tcp connection to a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:39:02Z"
    - latency: 5.988438ms
      message: 'load-balancer-api-external: resolved host name a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:39:02Z"
    - latency: 8.283464ms
      message: 'load-balancer-api-external: tcp connection to a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:38:02Z"
    - latency: 6.92281ms
      message: 'load-balancer-api-external: resolved host name a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:38:02Z"
    - latency: 5.443702ms
      message: 'load-balancer-api-external: tcp connection to a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:37:02Z"
    - latency: 6.710824ms
      message: 'load-balancer-api-external: resolved host name a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:37:02Z"
    - latency: 6.420483ms
      message: 'load-balancer-api-external: tcp connection to a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:36:02Z"
    - latency: 7.002001ms
      message: 'load-balancer-api-external: resolved host name a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:36:02Z"
    - latency: 4.949702ms
      message: 'load-balancer-api-external: tcp connection to a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:35:02Z"
    - latency: 9.754156ms
      message: 'load-balancer-api-external: resolved host name a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:35:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:33:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-36-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-36.ec2.internal
      uid: 34724d7e-2de1-4afa-b6bc-9b7ab9b68818
    resourceVersion: "15563"
    uid: 894a7397-f374-4819-93c0-74dad024dbcc
  spec:
    sourcePod: network-check-source-dbd9cf844-4g9pl
    targetEndpoint: a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:39:02Z"
      message: 'load-balancer-api-internal: tcp connection to a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.999039ms
      message: 'load-balancer-api-internal: tcp connection to a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:39:02Z"
    - latency: 6.120728ms
      message: 'load-balancer-api-internal: resolved host name a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:39:02Z"
    - latency: 5.616283ms
      message: 'load-balancer-api-internal: tcp connection to a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:38:02Z"
    - latency: 6.96932ms
      message: 'load-balancer-api-internal: resolved host name a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:38:02Z"
    - latency: 5.389877ms
      message: 'load-balancer-api-internal: tcp connection to a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:37:02Z"
    - latency: 6.74251ms
      message: 'load-balancer-api-internal: resolved host name a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:37:02Z"
    - latency: 5.49192ms
      message: 'load-balancer-api-internal: tcp connection to a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:36:02Z"
    - latency: 7.020959ms
      message: 'load-balancer-api-internal: resolved host name a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:36:02Z"
    - latency: 4.916238ms
      message: 'load-balancer-api-internal: tcp connection to a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:35:02Z"
    - latency: 9.864321ms
      message: 'load-balancer-api-internal: resolved host name a53a113583893490e80bbb2b0855fd65-00823513ca005063.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:35:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:33:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-36-to-network-check-target-ip-10-0-128-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-36.ec2.internal
      uid: 34724d7e-2de1-4afa-b6bc-9b7ab9b68818
    resourceVersion: "15894"
    uid: c697d3df-0dc2-41f5-bb1e-730781be9ac8
  spec:
    sourcePod: network-check-source-dbd9cf844-4g9pl
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:40:02Z"
      message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.367305ms
      message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:40:02Z"
    - latency: 2.150867ms
      message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:39:02Z"
    - latency: 2.358926ms
      message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:38:02Z"
    - latency: 2.257782ms
      message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:37:02Z"
    - latency: 2.147434ms
      message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:36:02Z"
    - latency: 5.665128ms
      message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:35:02Z"
    - latency: 2.410898ms
      message: 'network-check-target-ip-10-0-128-139: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:34:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:33:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-36-to-network-check-target-ip-10-0-130-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-36.ec2.internal
      uid: 34724d7e-2de1-4afa-b6bc-9b7ab9b68818
    resourceVersion: "15892"
    uid: 235215a2-ae9e-4c8e-8c53-51353cb641a6
  spec:
    sourcePod: network-check-source-dbd9cf844-4g9pl
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:40:02Z"
      message: 'network-check-target-ip-10-0-130-36: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 835.3µs
      message: 'network-check-target-ip-10-0-130-36: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:40:02Z"
    - latency: 1.029053ms
      message: 'network-check-target-ip-10-0-130-36: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:39:02Z"
    - latency: 1.208594ms
      message: 'network-check-target-ip-10-0-130-36: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:38:02Z"
    - latency: 945.977µs
      message: 'network-check-target-ip-10-0-130-36: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:37:02Z"
    - latency: 1.316742ms
      message: 'network-check-target-ip-10-0-130-36: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:36:02Z"
    - latency: 977.971µs
      message: 'network-check-target-ip-10-0-130-36: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:35:02Z"
    - latency: 1.237856ms
      message: 'network-check-target-ip-10-0-130-36: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:34:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:33:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-36-to-network-check-target-ip-10-0-135-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-36.ec2.internal
      uid: 34724d7e-2de1-4afa-b6bc-9b7ab9b68818
    resourceVersion: "15893"
    uid: c02f28ff-3468-4cc3-9429-8f37ce7dce49
  spec:
    sourcePod: network-check-source-dbd9cf844-4g9pl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:40:02Z"
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.407858ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:40:02Z"
    - latency: 2.366101ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:39:02Z"
    - latency: 2.33392ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:38:02Z"
    - latency: 2.179933ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:37:02Z"
    - latency: 2.160011ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:36:02Z"
    - latency: 5.643027ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:35:02Z"
    - latency: 2.561024ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:34:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T16:33:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-36-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-36.ec2.internal
      uid: 34724d7e-2de1-4afa-b6bc-9b7ab9b68818
    resourceVersion: "15560"
    uid: 15cbcbb1-08a6-4ce7-838c-1da5b28e2db1
  spec:
    sourcePod: network-check-source-dbd9cf844-4g9pl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T16:39:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.217µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:39:02Z"
    - latency: 1.601857ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:39:02Z"
    - latency: 1.084663ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:38:02Z"
    - latency: 1.951852ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:38:02Z"
    - latency: 929.624µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:37:02Z"
    - latency: 1.717397ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:37:02Z"
    - latency: 908.68µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:36:02Z"
    - latency: 1.608984ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:36:02Z"
    - latency: 3.883406ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T16:35:02Z"
    - latency: 1.741069ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T16:35:02Z"
kind: List
metadata:
  resourceVersion: ""