apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:31:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-39-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-39.ec2.internal
      uid: 4363c8ef-2940-45f6-a242-9cdd35b18636
    resourceVersion: "19732"
    uid: 1b97ad0d-24cd-43ef-8e3e-d38f73d1ea0e
  spec:
    sourcePod: network-check-source-989f8b8dc-hcnqq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:38:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.063446ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:38:19Z"
    - latency: 1.387305ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:19Z"
    - latency: 955.887µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:19Z"
    - latency: 1.443709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:19Z"
    - latency: 1.144655ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:34:19Z"
    - latency: 1.240871ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:33:19Z"
    - latency: 1.630938ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:32:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:31:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-39-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-39.ec2.internal
      uid: 4363c8ef-2940-45f6-a242-9cdd35b18636
    resourceVersion: "18815"
    uid: f2d6c19e-21f3-4b1f-aaa3-a7670dda2149
  spec:
    sourcePod: network-check-source-989f8b8dc-hcnqq
    targetEndpoint: a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:37:19Z"
      message: 'load-balancer-api-external: tcp connection to a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 9.828827ms
      message: 'load-balancer-api-external: tcp connection to a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:19Z"
    - latency: 8.578744ms
      message: 'load-balancer-api-external: resolved host name a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:37:19Z"
    - latency: 6.833649ms
      message: 'load-balancer-api-external: tcp connection to a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:19Z"
    - latency: 8.948822ms
      message: 'load-balancer-api-external: resolved host name a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:36:19Z"
    - latency: 7.611264ms
      message: 'load-balancer-api-external: tcp connection to a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:19Z"
    - latency: 12.393691ms
      message: 'load-balancer-api-external: resolved host name a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:35:19Z"
    - latency: 6.162342ms
      message: 'load-balancer-api-external: tcp connection to a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:34:19Z"
    - latency: 8.965224ms
      message: 'load-balancer-api-external: resolved host name a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:34:19Z"
    - latency: 5.654927ms
      message: 'load-balancer-api-external: tcp connection to a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:33:19Z"
    - latency: 9.82414ms
      message: 'load-balancer-api-external: resolved host name a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:33:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:31:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-39-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-39.ec2.internal
      uid: 4363c8ef-2940-45f6-a242-9cdd35b18636
    resourceVersion: "18814"
    uid: 9845be96-9720-459d-85c8-62141972e9ac
  spec:
    sourcePod: network-check-source-989f8b8dc-hcnqq
    targetEndpoint: a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:37:19Z"
      message: 'load-balancer-api-internal: tcp connection to a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.910543ms
      message: 'load-balancer-api-internal: tcp connection to a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:19Z"
    - latency: 8.495576ms
      message: 'load-balancer-api-internal: resolved host name a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:37:19Z"
    - latency: 6.77959ms
      message: 'load-balancer-api-internal: tcp connection to a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:19Z"
    - latency: 8.932465ms
      message: 'load-balancer-api-internal: resolved host name a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:36:19Z"
    - latency: 14.234599ms
      message: 'load-balancer-api-internal: tcp connection to a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:19Z"
    - latency: 12.347887ms
      message: 'load-balancer-api-internal: resolved host name a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:35:19Z"
    - latency: 4.691616ms
      message: 'load-balancer-api-internal: tcp connection to a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:34:19Z"
    - latency: 8.876144ms
      message: 'load-balancer-api-internal: resolved host name a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:34:19Z"
    - latency: 7.02321ms
      message: 'load-balancer-api-internal: tcp connection to a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:33:19Z"
    - latency: 9.767449ms
      message: 'load-balancer-api-internal: resolved host name a9ed9cd9e2e8b4bd5932caf2d7601009-7b2360452df153d0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:33:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:31:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-39-to-network-check-target-ip-10-0-134-39
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-39.ec2.internal
      uid: 4363c8ef-2940-45f6-a242-9cdd35b18636
    resourceVersion: "19729"
    uid: da6dfe7d-5125-49da-ae7e-3dadcdda9887
  spec:
    sourcePod: network-check-source-989f8b8dc-hcnqq
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:38:19Z"
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 804.015µs
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:38:19Z"
    - latency: 848.357µs
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:19Z"
    - latency: 1.947007ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:19Z"
    - latency: 1.205096ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:19Z"
    - latency: 1.376379ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:34:19Z"
    - latency: 865.25µs
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:33:19Z"
    - latency: 2.225795ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:32:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:31:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-39-to-network-check-target-ip-10-0-142-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-39.ec2.internal
      uid: 4363c8ef-2940-45f6-a242-9cdd35b18636
    resourceVersion: "19730"
    uid: 5a317e33-154e-40ff-9676-b6b96aba7f6f
  spec:
    sourcePod: network-check-source-989f8b8dc-hcnqq
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:38:19Z"
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.182177ms
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:38:19Z"
    - latency: 1.859081ms
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:19Z"
    - latency: 2.409608ms
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:19Z"
    - latency: 2.651052ms
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:19Z"
    - latency: 2.306526ms
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:34:19Z"
    - latency: 2.199062ms
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:33:19Z"
    - latency: 2.667689ms
      message: 'network-check-target-ip-10-0-142-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:32:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:31:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-39-to-network-check-target-ip-10-0-143-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-39.ec2.internal
      uid: 4363c8ef-2940-45f6-a242-9cdd35b18636
    resourceVersion: "19731"
    uid: e3183e8b-ecc0-4600-980c-be62b9da02e1
  spec:
    sourcePod: network-check-source-989f8b8dc-hcnqq
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:38:19Z"
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.219597ms
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:38:19Z"
    - latency: 2.369876ms
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:19Z"
    - latency: 2.404849ms
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:19Z"
    - latency: 2.468033ms
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:19Z"
    - latency: 2.217742ms
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:34:19Z"
    - latency: 2.675165ms
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:33:19Z"
    - latency: 3.040969ms
      message: 'network-check-target-ip-10-0-143-129: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:32:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:31:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-39-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-39.ec2.internal
      uid: 4363c8ef-2940-45f6-a242-9cdd35b18636
    resourceVersion: "18813"
    uid: fcab279f-ea21-4585-b3f9-9f2dc442d549
  spec:
    sourcePod: network-check-source-989f8b8dc-hcnqq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:37:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 819.162µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:19Z"
    - latency: 1.701351ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:37:19Z"
    - latency: 895.476µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:19Z"
    - latency: 1.94109ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:36:19Z"
    - latency: 949.6µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:19Z"
    - latency: 2.325468ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:35:19Z"
    - latency: 947.989µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:34:19Z"
    - latency: 1.810715ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:34:19Z"
    - latency: 821.275µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:33:19Z"
    - latency: 1.86049ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:33:19Z"
kind: List
metadata:
  resourceVersion: ""