apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:46:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-215-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-215.ec2.internal
      uid: 933dc8b8-7405-429a-a271-d3b9c6bc3eca
    resourceVersion: "21177"
    uid: dd662bf8-eafe-403d-85d0-7e080ff2c254
  spec:
    sourcePod: network-check-source-6f78d59f99-vlvk2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:53:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.230047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:53:31Z"
    - latency: 1.257513ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:52:31Z"
    - latency: 1.114633ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:51:31Z"
    - latency: 1.183625ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:50:31Z"
    - latency: 1.355404ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:49:31Z"
    - latency: 1.358653ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:48:31Z"
    - latency: 1.056697ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:47:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:46:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-215-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-215.ec2.internal
      uid: 933dc8b8-7405-429a-a271-d3b9c6bc3eca
    resourceVersion: "23997"
    uid: 93d08770-cc6d-4ffd-8824-441060e140dc
  spec:
    sourcePod: network-check-source-6f78d59f99-vlvk2
    targetEndpoint: a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:52:31Z"
      message: 'load-balancer-api-external: tcp connection to a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.798803ms
      message: 'load-balancer-api-external: tcp connection to a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:58:31Z"
    - latency: 6.552118ms
      message: 'load-balancer-api-external: resolved host name a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T00:58:31Z"
    - latency: 16.891314ms
      message: 'load-balancer-api-external: tcp connection to a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:57:31Z"
    - latency: 7.479856ms
      message: 'load-balancer-api-external: resolved host name a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T00:57:31Z"
    - latency: 17.543582ms
      message: 'load-balancer-api-external: tcp connection to a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:56:31Z"
    - latency: 7.305864ms
      message: 'load-balancer-api-external: resolved host name a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T00:56:31Z"
    - latency: 20.827337ms
      message: 'load-balancer-api-external: tcp connection to a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:55:31Z"
    - latency: 6.462663ms
      message: 'load-balancer-api-external: resolved host name a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T00:55:31Z"
    - latency: 15.257393ms
      message: 'load-balancer-api-external: tcp connection to a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:54:31Z"
    - latency: 6.822854ms
      message: 'load-balancer-api-external: resolved host name a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T00:54:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:46:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-215-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-215.ec2.internal
      uid: 933dc8b8-7405-429a-a271-d3b9c6bc3eca
    resourceVersion: "23996"
    uid: edebf85c-1582-43d1-a5a9-4828c728871d
  spec:
    sourcePod: network-check-source-6f78d59f99-vlvk2
    targetEndpoint: a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:52:31Z"
      message: 'load-balancer-api-internal: tcp connection to a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.723734ms
      message: 'load-balancer-api-internal: tcp connection to a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:58:31Z"
    - latency: 6.674936ms
      message: 'load-balancer-api-internal: resolved host name a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T00:58:31Z"
    - latency: 16.858102ms
      message: 'load-balancer-api-internal: tcp connection to a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:57:31Z"
    - latency: 7.54619ms
      message: 'load-balancer-api-internal: resolved host name a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T00:57:31Z"
    - latency: 18.022608ms
      message: 'load-balancer-api-internal: tcp connection to a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:56:31Z"
    - latency: 7.340252ms
      message: 'load-balancer-api-internal: resolved host name a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T00:56:31Z"
    - latency: 20.796767ms
      message: 'load-balancer-api-internal: tcp connection to a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:55:31Z"
    - latency: 6.405066ms
      message: 'load-balancer-api-internal: resolved host name a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T00:55:31Z"
    - latency: 17.322413ms
      message: 'load-balancer-api-internal: tcp connection to a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:54:31Z"
    - latency: 6.738396ms
      message: 'load-balancer-api-internal: resolved host name a87987aa2181842dfbd3c96b9e3b9be6-49910b82ce7bae3a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T00:54:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:46:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-215-to-network-check-target-ip-10-0-138-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-215.ec2.internal
      uid: 933dc8b8-7405-429a-a271-d3b9c6bc3eca
    resourceVersion: "21174"
    uid: 6a19021a-8ec5-46ae-9a40-1133160cd84e
  spec:
    sourcePod: network-check-source-6f78d59f99-vlvk2
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:53:31Z"
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.029445ms
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:53:31Z"
    - latency: 852.729µs
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:52:31Z"
    - latency: 1.649389ms
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:51:31Z"
    - latency: 1.265238ms
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:50:31Z"
    - latency: 943.124µs
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:49:31Z"
    - latency: 1.10544ms
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:48:31Z"
    - latency: 1.422885ms
      message: 'network-check-target-ip-10-0-138-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:47:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:46:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-215-to-network-check-target-ip-10-0-139-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-215.ec2.internal
      uid: 933dc8b8-7405-429a-a271-d3b9c6bc3eca
    resourceVersion: "21176"
    uid: ecb235bd-c651-42ad-9732-4c1521e43f07
  spec:
    sourcePod: network-check-source-6f78d59f99-vlvk2
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:53:31Z"
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.13403ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:53:31Z"
    - latency: 2.228577ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:52:31Z"
    - latency: 2.591564ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:51:31Z"
    - latency: 2.057486ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:50:31Z"
    - latency: 2.241686ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:49:31Z"
    - latency: 2.783149ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:48:31Z"
    - latency: 2.594986ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:47:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:46:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-215-to-network-check-target-ip-10-0-140-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-215.ec2.internal
      uid: 933dc8b8-7405-429a-a271-d3b9c6bc3eca
    resourceVersion: "21175"
    uid: db322da9-7a0b-4a70-81e6-6c9e4e030208
  spec:
    sourcePod: network-check-source-6f78d59f99-vlvk2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:53:31Z"
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.716929ms
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:53:31Z"
    - latency: 2.122242ms
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:52:31Z"
    - latency: 1.907438ms
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:51:31Z"
    - latency: 1.960607ms
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:50:31Z"
    - latency: 1.927079ms
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:49:31Z"
    - latency: 2.731829ms
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:48:31Z"
    - latency: 1.927267ms
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:47:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:46:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-215-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-215.ec2.internal
      uid: 933dc8b8-7405-429a-a271-d3b9c6bc3eca
    resourceVersion: "23995"
    uid: c85db449-a75d-4f25-82cd-8d0900542898
  spec:
    sourcePod: network-check-source-6f78d59f99-vlvk2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:52:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 978.532µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:58:31Z"
    - latency: 1.809538ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T00:58:31Z"
    - latency: 1.255227ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:57:31Z"
    - latency: 2.245513ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T00:57:31Z"
    - latency: 1.050803ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:56:31Z"
    - latency: 2.306918ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T00:56:31Z"
    - latency: 944.256µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:55:31Z"
    - latency: 2.153652ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T00:55:31Z"
    - latency: 1.014101ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T00:54:31Z"
    - latency: 1.938759ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T00:54:31Z"
kind: List
metadata:
  resourceVersion: ""