apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T11:42:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-33-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-33.ec2.internal
      uid: 58bee41e-212f-42bf-820f-b9f7c93df08a
    resourceVersion: "14588"
    uid: ce404192-d241-462d-9348-d4649f19e5bb
  spec:
    sourcePod: network-check-source-dbd9cf844-mbvxz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:49:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 904.106µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:49:50Z"
    - latency: 1.037994ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:48:50Z"
    - latency: 1.391926ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:47:50Z"
    - latency: 1.611777ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:46:50Z"
    - latency: 1.04285ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:45:50Z"
    - latency: 913.056µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:44:50Z"
    - latency: 1.254253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:43:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T11:42:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-33-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-33.ec2.internal
      uid: 58bee41e-212f-42bf-820f-b9f7c93df08a
    resourceVersion: "14259"
    uid: 7fb5113f-03b4-48f4-b599-328c1dcab41e
  spec:
    sourcePod: network-check-source-dbd9cf844-mbvxz
    targetEndpoint: ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:48:50Z"
      message: 'load-balancer-api-external: tcp connection to ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.817763ms
      message: 'load-balancer-api-external: tcp connection to ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:48:50Z"
    - latency: 8.14318ms
      message: 'load-balancer-api-external: resolved host name ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:48:50Z"
    - latency: 5.528614ms
      message: 'load-balancer-api-external: tcp connection to ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:47:50Z"
    - latency: 7.12426ms
      message: 'load-balancer-api-external: resolved host name ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:47:50Z"
    - latency: 5.772899ms
      message: 'load-balancer-api-external: tcp connection to ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:46:50Z"
    - latency: 11.154571ms
      message: 'load-balancer-api-external: resolved host name ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:46:50Z"
    - latency: 4.06076ms
      message: 'load-balancer-api-external: tcp connection to ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:45:50Z"
    - latency: 7.132495ms
      message: 'load-balancer-api-external: resolved host name ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:45:50Z"
    - latency: 4.343544ms
      message: 'load-balancer-api-external: tcp connection to ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:44:50Z"
    - latency: 6.974948ms
      message: 'load-balancer-api-external: resolved host name ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:44:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T11:42:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-33-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-33.ec2.internal
      uid: 58bee41e-212f-42bf-820f-b9f7c93df08a
    resourceVersion: "14258"
    uid: ce6568dd-f2d5-4ca9-b530-c8422439af77
  spec:
    sourcePod: network-check-source-dbd9cf844-mbvxz
    targetEndpoint: ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:48:50Z"
      message: 'load-balancer-api-internal: tcp connection to ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.811794ms
      message: 'load-balancer-api-internal: tcp connection to ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:48:50Z"
    - latency: 8.087069ms
      message: 'load-balancer-api-internal: resolved host name ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:48:50Z"
    - latency: 5.553002ms
      message: 'load-balancer-api-internal: tcp connection to ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:47:50Z"
    - latency: 7.063722ms
      message: 'load-balancer-api-internal: resolved host name ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:47:50Z"
    - latency: 4.274018ms
      message: 'load-balancer-api-internal: tcp connection to ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:46:50Z"
    - latency: 11.134701ms
      message: 'load-balancer-api-internal: resolved host name ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:46:50Z"
    - latency: 4.144869ms
      message: 'load-balancer-api-internal: tcp connection to ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:45:50Z"
    - latency: 7.058187ms
      message: 'load-balancer-api-internal: resolved host name ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:45:50Z"
    - latency: 4.36047ms
      message: 'load-balancer-api-internal: tcp connection to ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:44:50Z"
    - latency: 6.952483ms
      message: 'load-balancer-api-internal: resolved host name ac914efb3957a4a3da0f641655a9f02a-e476b9407648a5ed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:44:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T11:42:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-33-to-network-check-target-ip-10-0-130-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-33.ec2.internal
      uid: 58bee41e-212f-42bf-820f-b9f7c93df08a
    resourceVersion: "14586"
    uid: eaf2810a-c01a-4037-9c09-b7d6c51d1478
  spec:
    sourcePod: network-check-source-dbd9cf844-mbvxz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:49:50Z"
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.958736ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:49:50Z"
    - latency: 2.1763ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:48:50Z"
    - latency: 2.302856ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:47:50Z"
    - latency: 2.239621ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:46:50Z"
    - latency: 2.212307ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:45:50Z"
    - latency: 2.379095ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:44:50Z"
    - latency: 2.302359ms
      message: 'network-check-target-ip-10-0-130-222: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:43:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T11:42:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-33-to-network-check-target-ip-10-0-130-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-33.ec2.internal
      uid: 58bee41e-212f-42bf-820f-b9f7c93df08a
    resourceVersion: "14585"
    uid: d1bfb11b-c2b9-4153-a6e0-4a551819dadd
  spec:
    sourcePod: network-check-source-dbd9cf844-mbvxz
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:49:50Z"
      message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 811.706µs
      message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:49:50Z"
    - latency: 769.992µs
      message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:48:50Z"
    - latency: 1.654752ms
      message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:47:50Z"
    - latency: 1.881893ms
      message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:46:50Z"
    - latency: 1.485816ms
      message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:45:50Z"
    - latency: 1.378237ms
      message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:44:50Z"
    - latency: 1.871044ms
      message: 'network-check-target-ip-10-0-130-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:43:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T11:42:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-33-to-network-check-target-ip-10-0-138-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-33.ec2.internal
      uid: 58bee41e-212f-42bf-820f-b9f7c93df08a
    resourceVersion: "14587"
    uid: 61f59d3a-3380-44b6-b116-91227cba7bdf
  spec:
    sourcePod: network-check-source-dbd9cf844-mbvxz
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:49:50Z"
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.854583ms
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:49:50Z"
    - latency: 1.865526ms
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:48:50Z"
    - latency: 1.884556ms
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:47:50Z"
    - latency: 1.923342ms
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:46:50Z"
    - latency: 2.281549ms
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:45:50Z"
    - latency: 1.956159ms
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:44:50Z"
    - latency: 1.982745ms
      message: 'network-check-target-ip-10-0-138-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:43:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T11:42:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-33-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-33.ec2.internal
      uid: 58bee41e-212f-42bf-820f-b9f7c93df08a
    resourceVersion: "14256"
    uid: ada5fead-002b-4ee5-92a8-c0d4923eb2ac
  spec:
    sourcePod: network-check-source-dbd9cf844-mbvxz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T11:48:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 837.092µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:48:50Z"
    - latency: 1.660982ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:48:50Z"
    - latency: 1.020988ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:47:50Z"
    - latency: 1.932814ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:47:50Z"
    - latency: 776.621µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:46:50Z"
    - latency: 2.176709ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:46:50Z"
    - latency: 1.050967ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:45:50Z"
    - latency: 1.529845ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:45:50Z"
    - latency: 840.852µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T11:44:50Z"
    - latency: 1.554051ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T11:44:50Z"
kind: List
metadata:
  resourceVersion: ""