apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:14:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-107-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-107.ec2.internal
      uid: 4d2dc777-fa3f-4875-89c7-e43f357e94ac
    resourceVersion: "11965"
    uid: 55876f89-479d-4d5d-90d3-d50b75f97b3e
  spec:
    sourcePod: network-check-source-6f78d59f99-rwnw7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:21:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.96855ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:21:39Z"
    - latency: 1.075105ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:20:39Z"
    - latency: 869.866µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:19:39Z"
    - latency: 1.433085ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:18:39Z"
    - latency: 833.672µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:17:39Z"
    - latency: 1.397772ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:16:39Z"
    - latency: 1.049105ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:15:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:14:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-107-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-107.ec2.internal
      uid: 4d2dc777-fa3f-4875-89c7-e43f357e94ac
    resourceVersion: "11786"
    uid: 586e9adf-2d91-474e-b82b-8b9cbf366770
  spec:
    sourcePod: network-check-source-6f78d59f99-rwnw7
    targetEndpoint: a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:20:39Z"
      message: 'load-balancer-api-external: tcp connection to a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.313646ms
      message: 'load-balancer-api-external: tcp connection to a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:20:39Z"
    - latency: 15.297643ms
      message: 'load-balancer-api-external: resolved host name a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:20:39Z"
    - latency: 18.847201ms
      message: 'load-balancer-api-external: tcp connection to a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:19:39Z"
    - latency: 10.818669ms
      message: 'load-balancer-api-external: resolved host name a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:19:39Z"
    - latency: 18.964625ms
      message: 'load-balancer-api-external: tcp connection to a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:18:39Z"
    - latency: 8.5968ms
      message: 'load-balancer-api-external: resolved host name a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:18:39Z"
    - latency: 17.539142ms
      message: 'load-balancer-api-external: tcp connection to a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:17:39Z"
    - latency: 9.92004ms
      message: 'load-balancer-api-external: resolved host name a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:17:39Z"
    - latency: 18.378313ms
      message: 'load-balancer-api-external: tcp connection to a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:16:39Z"
    - latency: 10.428077ms
      message: 'load-balancer-api-external: resolved host name a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:16:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:14:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-107-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-107.ec2.internal
      uid: 4d2dc777-fa3f-4875-89c7-e43f357e94ac
    resourceVersion: "11785"
    uid: 1b623167-e3c2-42dd-9ca1-5f511daabbc6
  spec:
    sourcePod: network-check-source-6f78d59f99-rwnw7
    targetEndpoint: a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:20:39Z"
      message: 'load-balancer-api-internal: tcp connection to a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.324872ms
      message: 'load-balancer-api-internal: tcp connection to a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:20:39Z"
    - latency: 15.276016ms
      message: 'load-balancer-api-internal: resolved host name a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:20:39Z"
    - latency: 18.687592ms
      message: 'load-balancer-api-internal: tcp connection to a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:19:39Z"
    - latency: 10.733379ms
      message: 'load-balancer-api-internal: resolved host name a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:19:39Z"
    - latency: 16.743084ms
      message: 'load-balancer-api-internal: tcp connection to a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:18:39Z"
    - latency: 8.673523ms
      message: 'load-balancer-api-internal: resolved host name a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:18:39Z"
    - latency: 16.735771ms
      message: 'load-balancer-api-internal: tcp connection to a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:17:39Z"
    - latency: 9.832232ms
      message: 'load-balancer-api-internal: resolved host name a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:17:39Z"
    - latency: 19.127112ms
      message: 'load-balancer-api-internal: tcp connection to a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:16:39Z"
    - latency: 10.329157ms
      message: 'load-balancer-api-internal: resolved host name a389b778f644f4d799c7c9e57fb51ba7-ab43ebc1bf6aa889.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:16:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:14:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-107-to-network-check-target-ip-10-0-128-234
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-107.ec2.internal
      uid: 4d2dc777-fa3f-4875-89c7-e43f357e94ac
    resourceVersion: "11963"
    uid: b81d934c-0d1f-4019-b77f-ccafec4b153f
  spec:
    sourcePod: network-check-source-6f78d59f99-rwnw7
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:21:39Z"
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.109639ms
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:21:39Z"
    - latency: 1.966159ms
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:20:39Z"
    - latency: 1.946643ms
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:19:39Z"
    - latency: 2.2466ms
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:18:39Z"
    - latency: 1.72699ms
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:17:39Z"
    - latency: 1.922361ms
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:16:39Z"
    - latency: 2.230796ms
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:15:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:14:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-107-to-network-check-target-ip-10-0-132-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-107.ec2.internal
      uid: 4d2dc777-fa3f-4875-89c7-e43f357e94ac
    resourceVersion: "11964"
    uid: f3d84c24-0d4c-4ed5-a551-e9f717e460ac
  spec:
    sourcePod: network-check-source-6f78d59f99-rwnw7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:21:39Z"
      message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.167472ms
      message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:21:39Z"
    - latency: 2.329531ms
      message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:20:39Z"
    - latency: 2.169468ms
      message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:19:39Z"
    - latency: 2.304414ms
      message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:18:39Z"
    - latency: 1.971309ms
      message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:17:39Z"
    - latency: 2.244371ms
      message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:16:39Z"
    - latency: 2.534066ms
      message: 'network-check-target-ip-10-0-132-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:15:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:14:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-107-to-network-check-target-ip-10-0-134-107
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-107.ec2.internal
      uid: 4d2dc777-fa3f-4875-89c7-e43f357e94ac
    resourceVersion: "11962"
    uid: 0137d223-c53d-42f3-91c3-cc21bce8aee2
  spec:
    sourcePod: network-check-source-6f78d59f99-rwnw7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:21:39Z"
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.233653ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:21:39Z"
    - latency: 1.168517ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:20:39Z"
    - latency: 964.386µs
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:19:39Z"
    - latency: 834.346µs
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:18:39Z"
    - latency: 763.563µs
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:17:39Z"
    - latency: 1.6267ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:16:39Z"
    - latency: 1.371636ms
      message: 'network-check-target-ip-10-0-134-107: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:15:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:14:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-107-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-107.ec2.internal
      uid: 4d2dc777-fa3f-4875-89c7-e43f357e94ac
    resourceVersion: "11784"
    uid: 21602bf5-76c2-4e8f-9cc4-938153170422
  spec:
    sourcePod: network-check-source-6f78d59f99-rwnw7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T14:20:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.113242ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:20:39Z"
    - latency: 1.79184ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:20:39Z"
    - latency: 801.275µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:19:39Z"
    - latency: 2.341841ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:19:39Z"
    - latency: 912.618µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:18:39Z"
    - latency: 1.857533ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:18:39Z"
    - latency: 864.829µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:17:39Z"
    - latency: 1.574513ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:17:39Z"
    - latency: 1.106784ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:16:39Z"
    - latency: 1.558057ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:16:39Z"
kind: List
metadata:
  resourceVersion: ""