apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:44:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-42-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-42.us-west-1.compute.internal
      uid: 6252cbfc-a202-4ea2-9be2-5d7c693db43b
    resourceVersion: "19815"
    uid: 9df5e35f-8a4f-4ee8-96bd-ee27ea3968a5
  spec:
    sourcePod: network-check-source-6f78d59f99-mg5jj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:51:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 918.642µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:51:23Z"
    - latency: 1.445942ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:50:23Z"
    - latency: 940.022µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:49:23Z"
    - latency: 994.144µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:48:23Z"
    - latency: 849.386µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:47:23Z"
    - latency: 1.093329ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:46:23Z"
    - latency: 1.108249ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:45:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:44:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-42-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-42.us-west-1.compute.internal
      uid: 6252cbfc-a202-4ea2-9be2-5d7c693db43b
    resourceVersion: "23530"
    uid: 1e0926b4-4170-4338-af70-f8ae04b12e71
  spec:
    sourcePod: network-check-source-6f78d59f99-mg5jj
    targetEndpoint: ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:50:23Z"
      message: 'load-balancer-api-external: tcp connection to ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.345347ms
      message: 'load-balancer-api-external: tcp connection to ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:56:23Z"
    - latency: 7.420168ms
      message: 'load-balancer-api-external: resolved host name ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:56:23Z"
    - latency: 54.77742ms
      message: 'load-balancer-api-external: tcp connection to ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:55:23Z"
    - latency: 9.081306ms
      message: 'load-balancer-api-external: resolved host name ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:55:23Z"
    - latency: 54.834362ms
      message: 'load-balancer-api-external: tcp connection to ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:54:23Z"
    - latency: 7.984803ms
      message: 'load-balancer-api-external: resolved host name ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:54:23Z"
    - latency: 54.865891ms
      message: 'load-balancer-api-external: tcp connection to ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:53:23Z"
    - latency: 6.223235ms
      message: 'load-balancer-api-external: resolved host name ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:53:23Z"
    - latency: 54.110224ms
      message: 'load-balancer-api-external: tcp connection to ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:52:23Z"
    - latency: 6.260427ms
      message: 'load-balancer-api-external: resolved host name ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:52:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:44:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-42-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-42.us-west-1.compute.internal
      uid: 6252cbfc-a202-4ea2-9be2-5d7c693db43b
    resourceVersion: "23529"
    uid: a0e66a42-fcb4-41af-b175-e1746590768d
  spec:
    sourcePod: network-check-source-6f78d59f99-mg5jj
    targetEndpoint: ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:50:23Z"
      message: 'load-balancer-api-internal: tcp connection to ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 52.808498ms
      message: 'load-balancer-api-internal: tcp connection to ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:56:23Z"
    - latency: 7.375508ms
      message: 'load-balancer-api-internal: resolved host name ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:56:23Z"
    - latency: 61.872842ms
      message: 'load-balancer-api-internal: tcp connection to ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:55:23Z"
    - latency: 8.999538ms
      message: 'load-balancer-api-internal: resolved host name ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:55:23Z"
    - latency: 54.711128ms
      message: 'load-balancer-api-internal: tcp connection to ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:54:23Z"
    - latency: 7.92115ms
      message: 'load-balancer-api-internal: resolved host name ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:54:23Z"
    - latency: 54.910362ms
      message: 'load-balancer-api-internal: tcp connection to ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:53:23Z"
    - latency: 6.191415ms
      message: 'load-balancer-api-internal: resolved host name ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:53:23Z"
    - latency: 54.116032ms
      message: 'load-balancer-api-internal: tcp connection to ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:52:23Z"
    - latency: 6.235245ms
      message: 'load-balancer-api-internal: resolved host name ac233063f238c41d9a627ce19ba9e9a8-28f231a21e81d07d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:52:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:44:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-42-to-network-check-target-ip-10-0-129-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-42.us-west-1.compute.internal
      uid: 6252cbfc-a202-4ea2-9be2-5d7c693db43b
    resourceVersion: "19806"
    uid: 9ef237f1-9040-4e28-8351-671c71d2710e
  spec:
    sourcePod: network-check-source-6f78d59f99-mg5jj
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:51:23Z"
      message: 'network-check-target-ip-10-0-129-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.814802ms
      message: 'network-check-target-ip-10-0-129-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:51:23Z"
    - latency: 1.657492ms
      message: 'network-check-target-ip-10-0-129-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:50:23Z"
    - latency: 1.73187ms
      message: 'network-check-target-ip-10-0-129-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:49:23Z"
    - latency: 1.618575ms
      message: 'network-check-target-ip-10-0-129-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:48:23Z"
    - latency: 2.221376ms
      message: 'network-check-target-ip-10-0-129-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:47:23Z"
    - latency: 1.982158ms
      message: 'network-check-target-ip-10-0-129-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:46:23Z"
    - latency: 1.748466ms
      message: 'network-check-target-ip-10-0-129-193: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:45:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:44:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-42-to-network-check-target-ip-10-0-134-13
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-42.us-west-1.compute.internal
      uid: 6252cbfc-a202-4ea2-9be2-5d7c693db43b
    resourceVersion: "19807"
    uid: 123f65eb-d93d-4ffb-82d3-8ba0308b89b7
  spec:
    sourcePod: network-check-source-6f78d59f99-mg5jj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:51:23Z"
      message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.11507ms
      message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:51:23Z"
    - latency: 2.124923ms
      message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:50:23Z"
    - latency: 2.076995ms
      message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:49:23Z"
    - latency: 3.00869ms
      message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:48:23Z"
    - latency: 2.348913ms
      message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:47:23Z"
    - latency: 2.309129ms
      message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:46:23Z"
    - latency: 2.373078ms
      message: 'network-check-target-ip-10-0-134-13: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:45:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:44:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-42-to-network-check-target-ip-10-0-143-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-42.us-west-1.compute.internal
      uid: 6252cbfc-a202-4ea2-9be2-5d7c693db43b
    resourceVersion: "19805"
    uid: 54fb5f91-3b45-447b-b059-ba51510a09bf
  spec:
    sourcePod: network-check-source-6f78d59f99-mg5jj
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:51:23Z"
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 920.71µs
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:51:23Z"
    - latency: 1.054685ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:50:23Z"
    - latency: 870.985µs
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:49:23Z"
    - latency: 996.479µs
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:48:23Z"
    - latency: 2.033832ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:47:23Z"
    - latency: 1.50738ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:46:23Z"
    - latency: 1.687554ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:45:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:44:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-42-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-42.us-west-1.compute.internal
      uid: 6252cbfc-a202-4ea2-9be2-5d7c693db43b
    resourceVersion: "23525"
    uid: ee728f04-db8b-4a18-af96-317fe713e0b3
  spec:
    sourcePod: network-check-source-6f78d59f99-mg5jj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:50:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.060502ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:56:23Z"
    - latency: 1.603376ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:56:23Z"
    - latency: 939.956µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:55:23Z"
    - latency: 1.776689ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:55:23Z"
    - latency: 1.251623ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:54:23Z"
    - latency: 1.896232ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:54:23Z"
    - latency: 1.250044ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:53:23Z"
    - latency: 1.694605ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:53:23Z"
    - latency: 1.030248ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T00:52:23Z"
    - latency: 1.936492ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T00:52:23Z"
kind: List
metadata:
  resourceVersion: ""