apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T09:54:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-218-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-218.ec2.internal
      uid: 260a2051-8b11-4124-8571-2cde4391c860
    resourceVersion: "23446"
    uid: 20220d86-1c20-4805-a949-916adcb5b4ea
  spec:
    sourcePod: network-check-source-7cbc45fddc-tqxsg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:01:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.305674ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:01:37Z"
    - latency: 1.050089ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:00:37Z"
    - latency: 1.174351ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:59:37Z"
    - latency: 989.74µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:58:37Z"
    - latency: 881.601µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:57:37Z"
    - latency: 982.48µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:56:37Z"
    - latency: 909.92µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:55:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T09:54:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-218-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-218.ec2.internal
      uid: 260a2051-8b11-4124-8571-2cde4391c860
    resourceVersion: "22072"
    uid: 99dd625c-5ff2-4fa6-81e8-1e9de9c1164a
  spec:
    sourcePod: network-check-source-7cbc45fddc-tqxsg
    targetEndpoint: a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:00:37Z"
      message: 'load-balancer-api-external: tcp connection to a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.759726ms
      message: 'load-balancer-api-external: tcp connection to a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:00:37Z"
    - latency: 6.454435ms
      message: 'load-balancer-api-external: resolved host name a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T10:00:37Z"
    - latency: 4.816555ms
      message: 'load-balancer-api-external: tcp connection to a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:59:37Z"
    - latency: 6.953445ms
      message: 'load-balancer-api-external: resolved host name a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:59:37Z"
    - latency: 4.808961ms
      message: 'load-balancer-api-external: tcp connection to a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:58:37Z"
    - latency: 5.888435ms
      message: 'load-balancer-api-external: resolved host name a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:58:37Z"
    - latency: 4.650489ms
      message: 'load-balancer-api-external: tcp connection to a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:57:37Z"
    - latency: 8.550292ms
      message: 'load-balancer-api-external: resolved host name a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:57:37Z"
    - latency: 5.27118ms
      message: 'load-balancer-api-external: tcp connection to a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:56:37Z"
    - latency: 7.03438ms
      message: 'load-balancer-api-external: resolved host name a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:56:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T09:54:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-218-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-218.ec2.internal
      uid: 260a2051-8b11-4124-8571-2cde4391c860
    resourceVersion: "22071"
    uid: 8ba59644-4dcd-4187-8736-d6842042b56b
  spec:
    sourcePod: network-check-source-7cbc45fddc-tqxsg
    targetEndpoint: a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:00:37Z"
      message: 'load-balancer-api-internal: tcp connection to a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.760668ms
      message: 'load-balancer-api-internal: tcp connection to a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:00:37Z"
    - latency: 6.468761ms
      message: 'load-balancer-api-internal: resolved host name a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T10:00:37Z"
    - latency: 4.834779ms
      message: 'load-balancer-api-internal: tcp connection to a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:59:37Z"
    - latency: 7.018767ms
      message: 'load-balancer-api-internal: resolved host name a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:59:37Z"
    - latency: 4.835527ms
      message: 'load-balancer-api-internal: tcp connection to a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:58:37Z"
    - latency: 5.980222ms
      message: 'load-balancer-api-internal: resolved host name a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:58:37Z"
    - latency: 4.778928ms
      message: 'load-balancer-api-internal: tcp connection to a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:57:37Z"
    - latency: 8.614389ms
      message: 'load-balancer-api-internal: resolved host name a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:57:37Z"
    - latency: 5.211479ms
      message: 'load-balancer-api-internal: tcp connection to a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:56:37Z"
    - latency: 7.182445ms
      message: 'load-balancer-api-internal: resolved host name a410b57f520d54d5fa058e4d07c67c28-19b96f7c7222ba19.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:56:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T09:54:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-218-to-network-check-target-ip-10-0-139-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-218.ec2.internal
      uid: 260a2051-8b11-4124-8571-2cde4391c860
    resourceVersion: "23444"
    uid: 1b537af3-51be-43e6-b21b-894a6076834e
  spec:
    sourcePod: network-check-source-7cbc45fddc-tqxsg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:01:37Z"
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.909699ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:01:37Z"
    - latency: 2.084975ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:00:37Z"
    - latency: 1.933531ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:59:37Z"
    - latency: 2.110811ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:58:37Z"
    - latency: 1.858149ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:57:37Z"
    - latency: 2.016546ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:56:37Z"
    - latency: 2.082864ms
      message: 'network-check-target-ip-10-0-139-28: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:55:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T09:54:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-218-to-network-check-target-ip-10-0-142-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-218.ec2.internal
      uid: 260a2051-8b11-4124-8571-2cde4391c860
    resourceVersion: "23445"
    uid: 6c31eb2a-2cbe-4aa4-984f-2639ee05a5b4
  spec:
    sourcePod: network-check-source-7cbc45fddc-tqxsg
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:01:37Z"
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.212687ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:01:37Z"
    - latency: 2.323957ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:00:37Z"
    - latency: 2.186992ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:59:37Z"
    - latency: 2.537091ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:58:37Z"
    - latency: 1.91872ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:57:37Z"
    - latency: 1.902714ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:56:37Z"
    - latency: 2.248747ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:55:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T09:54:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-218-to-network-check-target-ip-10-0-143-218
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-218.ec2.internal
      uid: 260a2051-8b11-4124-8571-2cde4391c860
    resourceVersion: "23443"
    uid: 580debf6-2008-4492-9fdb-3981992c6524
  spec:
    sourcePod: network-check-source-7cbc45fddc-tqxsg
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:01:37Z"
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 978.432µs
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:01:37Z"
    - latency: 961.987µs
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:00:37Z"
    - latency: 909.028µs
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:59:37Z"
    - latency: 1.172979ms
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:58:37Z"
    - latency: 833.761µs
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:57:37Z"
    - latency: 844.368µs
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:56:37Z"
    - latency: 1.404374ms
      message: 'network-check-target-ip-10-0-143-218: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:55:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T09:54:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-218-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-218.ec2.internal
      uid: 260a2051-8b11-4124-8571-2cde4391c860
    resourceVersion: "22070"
    uid: e1565896-f6ab-4e6c-b930-c4e2c95c462e
  spec:
    sourcePod: network-check-source-7cbc45fddc-tqxsg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T10:00:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.197784ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T10:00:37Z"
    - latency: 1.785825ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T10:00:37Z"
    - latency: 1.040258ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:59:37Z"
    - latency: 1.808481ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:59:37Z"
    - latency: 1.006982ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:58:37Z"
    - latency: 1.819591ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:58:37Z"
    - latency: 774.395µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:57:37Z"
    - latency: 2.118685ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:57:37Z"
    - latency: 983.663µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:56:37Z"
    - latency: 1.813984ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:56:37Z"
kind: List
metadata:
  resourceVersion: ""