apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:06:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-69-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-69.ec2.internal
      uid: 87880c1e-a2f8-431c-b264-a52d127ec866
    resourceVersion: "14264"
    uid: 7dc2b946-732c-4802-8b78-ec76b7f68409
  spec:
    sourcePod: network-check-source-7d88cb55d8-nkdh2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:13:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.153354ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:13:09Z"
    - latency: 799.507µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:12:09Z"
    - latency: 986.15µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:11:09Z"
    - latency: 1.028344ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:10:09Z"
    - latency: 910.56µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:09:09Z"
    - latency: 936.893µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:08:09Z"
    - latency: 858.792µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:07:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:06:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-69-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-69.ec2.internal
      uid: 87880c1e-a2f8-431c-b264-a52d127ec866
    resourceVersion: "16002"
    uid: 87cd5955-fdde-4f61-b39f-07be616d2508
  spec:
    sourcePod: network-check-source-7d88cb55d8-nkdh2
    targetEndpoint: a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:12:09Z"
      message: 'load-balancer-api-external: tcp connection to a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.344437ms
      message: 'load-balancer-api-external: tcp connection to a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:18:09Z"
    - latency: 7.347739ms
      message: 'load-balancer-api-external: resolved host name a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:18:09Z"
    - latency: 3.954046ms
      message: 'load-balancer-api-external: tcp connection to a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:17:09Z"
    - latency: 7.78009ms
      message: 'load-balancer-api-external: resolved host name a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:17:09Z"
    - latency: 5.231407ms
      message: 'load-balancer-api-external: tcp connection to a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:16:09Z"
    - latency: 8.184743ms
      message: 'load-balancer-api-external: resolved host name a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:16:09Z"
    - latency: 4.43528ms
      message: 'load-balancer-api-external: tcp connection to a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:15:09Z"
    - latency: 8.013836ms
      message: 'load-balancer-api-external: resolved host name a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:15:09Z"
    - latency: 3.907897ms
      message: 'load-balancer-api-external: tcp connection to a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:14:09Z"
    - latency: 7.85067ms
      message: 'load-balancer-api-external: resolved host name a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:14:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:06:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-69-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-69.ec2.internal
      uid: 87880c1e-a2f8-431c-b264-a52d127ec866
    resourceVersion: "16003"
    uid: 4dd9a201-a47e-4651-8823-a2f5e9a2956f
  spec:
    sourcePod: network-check-source-7d88cb55d8-nkdh2
    targetEndpoint: a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:12:09Z"
      message: 'load-balancer-api-internal: tcp connection to a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.191912ms
      message: 'load-balancer-api-internal: tcp connection to a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:18:09Z"
    - latency: 7.482207ms
      message: 'load-balancer-api-internal: resolved host name a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:18:09Z"
    - latency: 3.723689ms
      message: 'load-balancer-api-internal: tcp connection to a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:17:09Z"
    - latency: 7.873625ms
      message: 'load-balancer-api-internal: resolved host name a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:17:09Z"
    - latency: 5.188548ms
      message: 'load-balancer-api-internal: tcp connection to a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:16:09Z"
    - latency: 8.221226ms
      message: 'load-balancer-api-internal: resolved host name a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:16:09Z"
    - latency: 4.431381ms
      message: 'load-balancer-api-internal: tcp connection to a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:15:09Z"
    - latency: 8.09105ms
      message: 'load-balancer-api-internal: resolved host name a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:15:09Z"
    - latency: 4.38994ms
      message: 'load-balancer-api-internal: tcp connection to a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:14:09Z"
    - latency: 7.875906ms
      message: 'load-balancer-api-internal: resolved host name a9ed97e72c02243d9a2c399ad8036cf9-244f30bf520f91c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:14:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:06:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-69-to-network-check-target-ip-10-0-133-126
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-69.ec2.internal
      uid: 87880c1e-a2f8-431c-b264-a52d127ec866
    resourceVersion: "14263"
    uid: 872e3264-407e-445f-98d4-db0c10585ffe
  spec:
    sourcePod: network-check-source-7d88cb55d8-nkdh2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:13:09Z"
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.109599ms
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:13:09Z"
    - latency: 2.191991ms
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:12:09Z"
    - latency: 2.1184ms
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:11:09Z"
    - latency: 1.803648ms
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:10:09Z"
    - latency: 2.158253ms
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:09:09Z"
    - latency: 2.405065ms
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:08:09Z"
    - latency: 2.298017ms
      message: 'network-check-target-ip-10-0-133-126: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:07:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:06:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-69-to-network-check-target-ip-10-0-140-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-69.ec2.internal
      uid: 87880c1e-a2f8-431c-b264-a52d127ec866
    resourceVersion: "14262"
    uid: d8e45a43-9bf8-4ac1-ac07-d89a98360524
  spec:
    sourcePod: network-check-source-7d88cb55d8-nkdh2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:13:09Z"
      message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.281081ms
      message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:13:09Z"
    - latency: 2.197385ms
      message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:12:09Z"
    - latency: 2.197965ms
      message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:11:09Z"
    - latency: 1.986481ms
      message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:10:09Z"
    - latency: 2.891925ms
      message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:09:09Z"
    - latency: 2.345671ms
      message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:08:09Z"
    - latency: 2.359649ms
      message: 'network-check-target-ip-10-0-140-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:07:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:06:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-69-to-network-check-target-ip-10-0-140-69
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-69.ec2.internal
      uid: 87880c1e-a2f8-431c-b264-a52d127ec866
    resourceVersion: "14261"
    uid: ddc5ae7f-7bf7-41ac-a787-76f4c2d1958d
  spec:
    sourcePod: network-check-source-7d88cb55d8-nkdh2
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:13:09Z"
      message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.234µs
      message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:13:09Z"
    - latency: 803.474µs
      message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:12:09Z"
    - latency: 927.218µs
      message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:11:09Z"
    - latency: 885.625µs
      message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:10:09Z"
    - latency: 913.963µs
      message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:09:09Z"
    - latency: 934.313µs
      message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:08:09Z"
    - latency: 1.202164ms
      message: 'network-check-target-ip-10-0-140-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:07:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T15:06:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-69-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-69.ec2.internal
      uid: 87880c1e-a2f8-431c-b264-a52d127ec866
    resourceVersion: "16001"
    uid: bdee5661-2cdf-40c1-b017-f512c805e367
  spec:
    sourcePod: network-check-source-7d88cb55d8-nkdh2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T15:12:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.099517ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:18:09Z"
    - latency: 1.731706ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:18:09Z"
    - latency: 880.466µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:17:09Z"
    - latency: 1.655629ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:17:09Z"
    - latency: 1.003205ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:16:09Z"
    - latency: 1.792306ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:16:09Z"
    - latency: 750.952µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:15:09Z"
    - latency: 1.67123ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:15:09Z"
    - latency: 865.839µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T15:14:09Z"
    - latency: 1.718275ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T15:14:09Z"
kind: List
metadata:
  resourceVersion: ""