apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:34:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-64-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-64.ec2.internal
      uid: 1bbda32f-c9f1-42a7-8143-935a028b9ac4
    resourceVersion: "15299"
    uid: 95a672b0-4c7c-48a3-aa19-25fbc79a7ea5
  spec:
    sourcePod: network-check-source-989f8b8dc-5cpbm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:41:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.758062ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:41:15Z"
    - latency: 1.119456ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:40:15Z"
    - latency: 896.362µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:39:15Z"
    - latency: 897.127µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:38:15Z"
    - latency: 975.173µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:15Z"
    - latency: 1.358533ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:15Z"
    - latency: 992.167µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:34:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-64-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-64.ec2.internal
      uid: 1bbda32f-c9f1-42a7-8143-935a028b9ac4
    resourceVersion: "14800"
    uid: 98f22482-98b4-4c7d-9c6c-78ff1d763b94
  spec:
    sourcePod: network-check-source-989f8b8dc-5cpbm
    targetEndpoint: a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:40:15Z"
      message: 'load-balancer-api-external: tcp connection to a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.908671ms
      message: 'load-balancer-api-external: tcp connection to a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:40:15Z"
    - latency: 6.633078ms
      message: 'load-balancer-api-external: resolved host name a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:40:15Z"
    - latency: 5.103988ms
      message: 'load-balancer-api-external: tcp connection to a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:39:15Z"
    - latency: 6.587881ms
      message: 'load-balancer-api-external: resolved host name a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:39:15Z"
    - latency: 4.040872ms
      message: 'load-balancer-api-external: tcp connection to a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:38:15Z"
    - latency: 6.375847ms
      message: 'load-balancer-api-external: resolved host name a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:38:15Z"
    - latency: 4.328689ms
      message: 'load-balancer-api-external: tcp connection to a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:15Z"
    - latency: 8.072667ms
      message: 'load-balancer-api-external: resolved host name a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:37:15Z"
    - latency: 4.210286ms
      message: 'load-balancer-api-external: tcp connection to a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:15Z"
    - latency: 7.719808ms
      message: 'load-balancer-api-external: resolved host name a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:36:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:34:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-64-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-64.ec2.internal
      uid: 1bbda32f-c9f1-42a7-8143-935a028b9ac4
    resourceVersion: "14801"
    uid: ee0248e0-4042-4846-91aa-d313cd86df24
  spec:
    sourcePod: network-check-source-989f8b8dc-5cpbm
    targetEndpoint: a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:40:15Z"
      message: 'load-balancer-api-internal: tcp connection to a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.965513ms
      message: 'load-balancer-api-internal: tcp connection to a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:40:15Z"
    - latency: 6.564166ms
      message: 'load-balancer-api-internal: resolved host name a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:40:15Z"
    - latency: 5.311195ms
      message: 'load-balancer-api-internal: tcp connection to a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:39:15Z"
    - latency: 6.650809ms
      message: 'load-balancer-api-internal: resolved host name a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:39:15Z"
    - latency: 4.546671ms
      message: 'load-balancer-api-internal: tcp connection to a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:38:15Z"
    - latency: 6.309052ms
      message: 'load-balancer-api-internal: resolved host name a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:38:15Z"
    - latency: 4.821025ms
      message: 'load-balancer-api-internal: tcp connection to a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:15Z"
    - latency: 7.964269ms
      message: 'load-balancer-api-internal: resolved host name a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:37:15Z"
    - latency: 3.900367ms
      message: 'load-balancer-api-internal: tcp connection to a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:15Z"
    - latency: 7.771831ms
      message: 'load-balancer-api-internal: resolved host name a4b6667faa490438daa5f57b24642c50-3a1d20e7f95004a2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:36:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:34:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-64-to-network-check-target-ip-10-0-136-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-64.ec2.internal
      uid: 1bbda32f-c9f1-42a7-8143-935a028b9ac4
    resourceVersion: "15297"
    uid: cf5dbd64-6033-426c-a590-8d6ac94656bc
  spec:
    sourcePod: network-check-source-989f8b8dc-5cpbm
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:41:15Z"
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.201166ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:41:15Z"
    - latency: 2.232946ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:40:15Z"
    - latency: 2.30529ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:39:15Z"
    - latency: 2.29852ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:38:15Z"
    - latency: 2.167518ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:15Z"
    - latency: 2.202076ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:15Z"
    - latency: 2.185163ms
      message: 'network-check-target-ip-10-0-136-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:34:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-64-to-network-check-target-ip-10-0-137-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-64.ec2.internal
      uid: 1bbda32f-c9f1-42a7-8143-935a028b9ac4
    resourceVersion: "15296"
    uid: e43eeaa3-a382-46de-99a4-3c1a3a977d9e
  spec:
    sourcePod: network-check-source-989f8b8dc-5cpbm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:41:15Z"
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 848.336µs
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:41:15Z"
    - latency: 917.635µs
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:40:15Z"
    - latency: 873.858µs
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:39:15Z"
    - latency: 1.367272ms
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:38:15Z"
    - latency: 1.011817ms
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:15Z"
    - latency: 1.151781ms
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:15Z"
    - latency: 1.182338ms
      message: 'network-check-target-ip-10-0-137-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:34:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-64-to-network-check-target-ip-10-0-138-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-64.ec2.internal
      uid: 1bbda32f-c9f1-42a7-8143-935a028b9ac4
    resourceVersion: "15298"
    uid: 016e452f-4b5c-4f0b-898e-b6eff7f11188
  spec:
    sourcePod: network-check-source-989f8b8dc-5cpbm
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:41:15Z"
      message: 'network-check-target-ip-10-0-138-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.008052ms
      message: 'network-check-target-ip-10-0-138-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:41:15Z"
    - latency: 1.956135ms
      message: 'network-check-target-ip-10-0-138-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:40:15Z"
    - latency: 1.829692ms
      message: 'network-check-target-ip-10-0-138-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:39:15Z"
    - latency: 2.032697ms
      message: 'network-check-target-ip-10-0-138-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:38:15Z"
    - latency: 1.904175ms
      message: 'network-check-target-ip-10-0-138-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:15Z"
    - latency: 2.066227ms
      message: 'network-check-target-ip-10-0-138-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:15Z"
    - latency: 2.175064ms
      message: 'network-check-target-ip-10-0-138-56: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:35:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T15:34:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-64-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-64.ec2.internal
      uid: 1bbda32f-c9f1-42a7-8143-935a028b9ac4
    resourceVersion: "14799"
    uid: aa792be9-05ed-46bf-9f2b-3e2bf44ba011
  spec:
    sourcePod: network-check-source-989f8b8dc-5cpbm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T15:40:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 900.84µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:40:15Z"
    - latency: 1.621195ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:40:15Z"
    - latency: 1.074353ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:39:15Z"
    - latency: 1.704939ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:39:15Z"
    - latency: 877.962µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:38:15Z"
    - latency: 1.66743ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:38:15Z"
    - latency: 1.110849ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:37:15Z"
    - latency: 1.92676ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:37:15Z"
    - latency: 965.669µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T15:36:15Z"
    - latency: 1.750085ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T15:36:15Z"
kind: List
metadata:
  resourceVersion: ""