apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:31:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-48-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-48.us-east-2.compute.internal
      uid: deda9ead-1e88-4622-9273-af87d99ecc04
    resourceVersion: "24827"
    uid: d8043fa9-ef91-4a0f-80cf-af4e3bfc724a
  spec:
    sourcePod: network-check-source-6f78d59f99-4xtdb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:39:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.153862ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:14:00Z"
    - latency: 854.963µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:13:00Z"
    - latency: 1.60599ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:12:00Z"
    - latency: 1.373811ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:11:00Z"
    - latency: 832.575µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:10:00Z"
    - latency: 1.139169ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:00Z"
    - latency: 1.229127ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:00Z"
    - latency: 917.273µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:00Z"
    - latency: 1.060901ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:00Z"
    - latency: 1.276303ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:31:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-48-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-48.us-east-2.compute.internal
      uid: deda9ead-1e88-4622-9273-af87d99ecc04
    resourceVersion: "26653"
    uid: b7dba0f2-e668-43d4-90f8-232c555c0098
  spec:
    sourcePod: network-check-source-6f78d59f99-4xtdb
    targetEndpoint: a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:38:00Z"
      message: 'load-balancer-api-external: tcp connection to a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.876601ms
      message: 'load-balancer-api-external: tcp connection to a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:20:00Z"
    - latency: 7.976506ms
      message: 'load-balancer-api-external: resolved host name a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:20:00Z"
    - latency: 5.136817ms
      message: 'load-balancer-api-external: tcp connection to a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:19:00Z"
    - latency: 7.62916ms
      message: 'load-balancer-api-external: resolved host name a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:19:00Z"
    - latency: 5.880666ms
      message: 'load-balancer-api-external: tcp connection to a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:18:00Z"
    - latency: 7.936398ms
      message: 'load-balancer-api-external: resolved host name a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:18:00Z"
    - latency: 6.67735ms
      message: 'load-balancer-api-external: tcp connection to a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:17:00Z"
    - latency: 8.685157ms
      message: 'load-balancer-api-external: resolved host name a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:17:00Z"
    - latency: 6.136686ms
      message: 'load-balancer-api-external: tcp connection to a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:16:00Z"
    - latency: 7.497933ms
      message: 'load-balancer-api-external: resolved host name a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:16:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:31:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-48-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-48.us-east-2.compute.internal
      uid: deda9ead-1e88-4622-9273-af87d99ecc04
    resourceVersion: "26652"
    uid: 61647e5b-9334-4ed4-b540-c107c9939ee4
  spec:
    sourcePod: network-check-source-6f78d59f99-4xtdb
    targetEndpoint: a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:38:00Z"
      message: 'load-balancer-api-internal: tcp connection to a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.847477ms
      message: 'load-balancer-api-internal: tcp connection to a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:20:00Z"
    - latency: 7.891917ms
      message: 'load-balancer-api-internal: resolved host name a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:20:00Z"
    - latency: 5.152034ms
      message: 'load-balancer-api-internal: tcp connection to a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:19:00Z"
    - latency: 7.689698ms
      message: 'load-balancer-api-internal: resolved host name a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:19:00Z"
    - latency: 5.92057ms
      message: 'load-balancer-api-internal: tcp connection to a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:18:00Z"
    - latency: 7.854434ms
      message: 'load-balancer-api-internal: resolved host name a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:18:00Z"
    - latency: 6.666833ms
      message: 'load-balancer-api-internal: tcp connection to a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:17:00Z"
    - latency: 8.715322ms
      message: 'load-balancer-api-internal: resolved host name a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:17:00Z"
    - latency: 6.116921ms
      message: 'load-balancer-api-internal: tcp connection to a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:16:00Z"
    - latency: 6.844189ms
      message: 'load-balancer-api-internal: resolved host name a51a8a8dfd08c47608cb84249ed1c067-21202dd1f9d41abd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:16:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:31:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-48-to-network-check-target-ip-10-0-130-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-48.us-east-2.compute.internal
      uid: deda9ead-1e88-4622-9273-af87d99ecc04
    resourceVersion: "24823"
    uid: fa1b6f16-1b10-46e5-b3e3-ea4d57e60927
  spec:
    sourcePod: network-check-source-6f78d59f99-4xtdb
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:39:00Z"
      message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 830.596µs
      message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:14:00Z"
    - latency: 1.32873ms
      message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:13:00Z"
    - latency: 1.424022ms
      message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:12:00Z"
    - latency: 799.995µs
      message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:11:00Z"
    - latency: 952.492µs
      message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:10:00Z"
    - latency: 1.277042ms
      message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:00Z"
    - latency: 1.409288ms
      message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:00Z"
    - latency: 951.291µs
      message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:00Z"
    - latency: 866.973µs
      message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:00Z"
    - latency: 1.170658ms
      message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:31:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-48-to-network-check-target-ip-10-0-134-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-48.us-east-2.compute.internal
      uid: deda9ead-1e88-4622-9273-af87d99ecc04
    resourceVersion: "24824"
    uid: 6c40e568-abe3-4b57-b57c-f02039d7b523
  spec:
    sourcePod: network-check-source-6f78d59f99-4xtdb
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:39:00Z"
      message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.02871ms
      message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:14:00Z"
    - latency: 2.012794ms
      message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:13:00Z"
    - latency: 2.307115ms
      message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:12:00Z"
    - latency: 2.220756ms
      message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:11:00Z"
    - latency: 1.975098ms
      message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:10:00Z"
    - latency: 2.427101ms
      message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:09:00Z"
    - latency: 2.244033ms
      message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:08:00Z"
    - latency: 2.11857ms
      message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:07:00Z"
    - latency: 2.058328ms
      message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:06:00Z"
    - latency: 2.358738ms
      message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:05:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T08:15:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-48-to-network-check-target-ip-10-0-136-240
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-48.us-east-2.compute.internal
      uid: deda9ead-1e88-4622-9273-af87d99ecc04
    resourceVersion: "25388"
    uid: 4c011c48-7934-47a3-b62c-8c922ef739be
  spec:
    sourcePod: network-check-source-6f78d59f99-4xtdb
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:31:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-48-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-48.us-east-2.compute.internal
      uid: deda9ead-1e88-4622-9273-af87d99ecc04
    resourceVersion: "26651"
    uid: f6b27c8a-0152-4636-be7f-1a4efa2af8ed
  spec:
    sourcePod: network-check-source-6f78d59f99-4xtdb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:38:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 919.342µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:20:00Z"
    - latency: 1.810272ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:20:00Z"
    - latency: 712.793µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:19:00Z"
    - latency: 1.60099ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:19:00Z"
    - latency: 1.030368ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:18:00Z"
    - latency: 1.713666ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:18:00Z"
    - latency: 1.805382ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:17:00Z"
    - latency: 1.982125ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:17:00Z"
    - latency: 768.194µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:16:00Z"
    - latency: 1.824132ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:16:00Z"
kind: List
metadata:
  resourceVersion: ""