apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:50:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-14-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-14.ec2.internal
      uid: 1b47301d-e3bd-442e-bda4-4054ad438e9e
    resourceVersion: "17454"
    uid: 808b93fa-b6a3-4d47-a534-87745af983a3
  spec:
    sourcePod: network-check-source-56499946bc-ww8fl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:57:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.004011ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:57:42Z"
    - latency: 1.028845ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:56:42Z"
    - latency: 1.273938ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:55:42Z"
    - latency: 1.14645ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:54:42Z"
    - latency: 1.022356ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:53:42Z"
    - latency: 1.128479ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:52:42Z"
    - latency: 1.024318ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:51:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:50:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-14-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-14.ec2.internal
      uid: 1b47301d-e3bd-442e-bda4-4054ad438e9e
    resourceVersion: "16998"
    uid: 8a48e613-21f1-4f42-990f-010d2b22c73b
  spec:
    sourcePod: network-check-source-56499946bc-ww8fl
    targetEndpoint: af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:56:42Z"
      message: 'load-balancer-api-external: tcp connection to af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.350974ms
      message: 'load-balancer-api-external: tcp connection to af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:56:42Z"
    - latency: 6.401321ms
      message: 'load-balancer-api-external: resolved host name af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:56:42Z"
    - latency: 5.082257ms
      message: 'load-balancer-api-external: tcp connection to af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:55:42Z"
    - latency: 6.6334ms
      message: 'load-balancer-api-external: resolved host name af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:55:42Z"
    - latency: 4.024272ms
      message: 'load-balancer-api-external: tcp connection to af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:54:42Z"
    - latency: 6.444373ms
      message: 'load-balancer-api-external: resolved host name af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:54:42Z"
    - latency: 4.525375ms
      message: 'load-balancer-api-external: tcp connection to af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:53:42Z"
    - latency: 7.054102ms
      message: 'load-balancer-api-external: resolved host name af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:53:42Z"
    - latency: 4.136033ms
      message: 'load-balancer-api-external: tcp connection to af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:52:42Z"
    - latency: 6.689728ms
      message: 'load-balancer-api-external: resolved host name af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:52:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:50:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-14-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-14.ec2.internal
      uid: 1b47301d-e3bd-442e-bda4-4054ad438e9e
    resourceVersion: "16999"
    uid: e96221b5-bb23-4313-b109-b0b0726d2484
  spec:
    sourcePod: network-check-source-56499946bc-ww8fl
    targetEndpoint: af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:56:42Z"
      message: 'load-balancer-api-internal: tcp connection to af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.809634ms
      message: 'load-balancer-api-internal: tcp connection to af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:56:42Z"
    - latency: 6.364664ms
      message: 'load-balancer-api-internal: resolved host name af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:56:42Z"
    - latency: 5.096557ms
      message: 'load-balancer-api-internal: tcp connection to af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:55:42Z"
    - latency: 6.548486ms
      message: 'load-balancer-api-internal: resolved host name af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:55:42Z"
    - latency: 4.801625ms
      message: 'load-balancer-api-internal: tcp connection to af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:54:42Z"
    - latency: 6.419177ms
      message: 'load-balancer-api-internal: resolved host name af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:54:42Z"
    - latency: 4.510786ms
      message: 'load-balancer-api-internal: tcp connection to af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:53:42Z"
    - latency: 6.977567ms
      message: 'load-balancer-api-internal: resolved host name af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:53:42Z"
    - latency: 5.212234ms
      message: 'load-balancer-api-internal: tcp connection to af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:52:42Z"
    - latency: 6.635326ms
      message: 'load-balancer-api-internal: resolved host name af57d6754b174426a8ff975d3b7735ed-8818685039104905.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:52:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:50:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-14-to-network-check-target-ip-10-0-131-109
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-14.ec2.internal
      uid: 1b47301d-e3bd-442e-bda4-4054ad438e9e
    resourceVersion: "17453"
    uid: 8dba49b3-641f-4603-a4c8-7da0bd254d01
  spec:
    sourcePod: network-check-source-56499946bc-ww8fl
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:57:42Z"
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.496701ms
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:57:42Z"
    - latency: 2.261895ms
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:56:42Z"
    - latency: 2.207642ms
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:55:42Z"
    - latency: 2.532991ms
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:54:42Z"
    - latency: 2.070735ms
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:53:42Z"
    - latency: 2.161374ms
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:52:42Z"
    - latency: 2.333246ms
      message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:51:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:50:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-14-to-network-check-target-ip-10-0-137-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-14.ec2.internal
      uid: 1b47301d-e3bd-442e-bda4-4054ad438e9e
    resourceVersion: "17451"
    uid: f572d807-ad2b-4133-a3cb-31337ccd8238
  spec:
    sourcePod: network-check-source-56499946bc-ww8fl
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:57:42Z"
      message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.218272ms
      message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:57:42Z"
    - latency: 1.294648ms
      message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:56:42Z"
    - latency: 1.47791ms
      message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:55:42Z"
    - latency: 1.39572ms
      message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:54:42Z"
    - latency: 1.245027ms
      message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:53:42Z"
    - latency: 804.989µs
      message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:52:42Z"
    - latency: 1.09793ms
      message: 'network-check-target-ip-10-0-137-14: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:51:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:50:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-14-to-network-check-target-ip-10-0-141-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-14.ec2.internal
      uid: 1b47301d-e3bd-442e-bda4-4054ad438e9e
    resourceVersion: "17452"
    uid: 5056fc1e-942d-4c3a-95b9-b68b0b5dc178
  spec:
    sourcePod: network-check-source-56499946bc-ww8fl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:57:42Z"
      message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.042616ms
      message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:57:42Z"
    - latency: 2.078896ms
      message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:56:42Z"
    - latency: 1.966177ms
      message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:55:42Z"
    - latency: 1.801826ms
      message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:54:42Z"
    - latency: 2.122793ms
      message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:53:42Z"
    - latency: 1.892104ms
      message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:52:42Z"
    - latency: 2.177581ms
      message: 'network-check-target-ip-10-0-141-121: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:51:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T15:50:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-14-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-14.ec2.internal
      uid: 1b47301d-e3bd-442e-bda4-4054ad438e9e
    resourceVersion: "16997"
    uid: a6de1d5c-d973-4a1d-95af-439ac664f9e1
  spec:
    sourcePod: network-check-source-56499946bc-ww8fl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T15:56:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 879.519µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:56:42Z"
    - latency: 1.852124ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:56:42Z"
    - latency: 1.168325ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:55:42Z"
    - latency: 1.525583ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:55:42Z"
    - latency: 1.078781ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:54:42Z"
    - latency: 1.642405ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:54:42Z"
    - latency: 1.109929ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:53:42Z"
    - latency: 1.700393ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:53:42Z"
    - latency: 880.533µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T15:52:42Z"
    - latency: 1.648279ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T15:52:42Z"
kind: List
metadata:
  resourceVersion: ""