apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:36:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-102-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-102.us-west-2.compute.internal
      uid: 9d5fd7cd-fed0-4ac1-9377-7e7e9e9c01cd
    resourceVersion: "11727"
    uid: 34bed852-67ce-4ac7-9361-f3dca5bd4e23
  spec:
    sourcePod: network-check-source-6f78d59f99-z5j5h
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T15:43:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 938.603µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:43:31Z"
    - latency: 991.157µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:42:31Z"
    - latency: 989.924µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:41:31Z"
    - latency: 1.102512ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:40:31Z"
    - latency: 1.272588ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:39:31Z"
    - latency: 836.152µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:38:31Z"
    - latency: 970.623µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:37:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:36:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-102-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-102.us-west-2.compute.internal
      uid: 9d5fd7cd-fed0-4ac1-9377-7e7e9e9c01cd
    resourceVersion: "11418"
    uid: 8bc10b52-28c3-4a96-983d-ea23443e06d3
  spec:
    sourcePod: network-check-source-6f78d59f99-z5j5h
    targetEndpoint: ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T15:42:31Z"
      message: 'load-balancer-api-external: tcp connection to ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 51.464447ms
      message: 'load-balancer-api-external: tcp connection to ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:42:31Z"
    - latency: 8.343154ms
      message: 'load-balancer-api-external: resolved host name ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:42:31Z"
    - latency: 50.460362ms
      message: 'load-balancer-api-external: tcp connection to ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:41:31Z"
    - latency: 9.644404ms
      message: 'load-balancer-api-external: resolved host name ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:41:31Z"
    - latency: 56.769974ms
      message: 'load-balancer-api-external: tcp connection to ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:40:31Z"
    - latency: 8.809312ms
      message: 'load-balancer-api-external: resolved host name ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:40:31Z"
    - latency: 51.155087ms
      message: 'load-balancer-api-external: tcp connection to ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:39:31Z"
    - latency: 14.048187ms
      message: 'load-balancer-api-external: resolved host name ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:39:31Z"
    - latency: 49.548595ms
      message: 'load-balancer-api-external: tcp connection to ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:38:31Z"
    - latency: 8.415542ms
      message: 'load-balancer-api-external: resolved host name ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:38:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:36:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-102-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-102.us-west-2.compute.internal
      uid: 9d5fd7cd-fed0-4ac1-9377-7e7e9e9c01cd
    resourceVersion: "11419"
    uid: cbf70af0-fd02-4d7a-87fe-18ec350f0a15
  spec:
    sourcePod: network-check-source-6f78d59f99-z5j5h
    targetEndpoint: ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T15:42:31Z"
      message: 'load-balancer-api-internal: tcp connection to ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 50.727771ms
      message: 'load-balancer-api-internal: tcp connection to ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:42:31Z"
    - latency: 8.285917ms
      message: 'load-balancer-api-internal: resolved host name ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:42:31Z"
    - latency: 55.330998ms
      message: 'load-balancer-api-internal: tcp connection to ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:41:31Z"
    - latency: 9.711598ms
      message: 'load-balancer-api-internal: resolved host name ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:41:31Z"
    - latency: 54.140266ms
      message: 'load-balancer-api-internal: tcp connection to ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:40:31Z"
    - latency: 8.862485ms
      message: 'load-balancer-api-internal: resolved host name ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:40:31Z"
    - latency: 61.95346ms
      message: 'load-balancer-api-internal: tcp connection to ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:39:31Z"
    - latency: 14.110777ms
      message: 'load-balancer-api-internal: resolved host name ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:39:31Z"
    - latency: 49.612085ms
      message: 'load-balancer-api-internal: tcp connection to ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:38:31Z"
    - latency: 8.393324ms
      message: 'load-balancer-api-internal: resolved host name ac79ad3d692764734abd2f0e62156b9f-3e14d33ea062bfc8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:38:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:36:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-102-to-network-check-target-ip-10-0-133-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-102.us-west-2.compute.internal
      uid: 9d5fd7cd-fed0-4ac1-9377-7e7e9e9c01cd
    resourceVersion: "11724"
    uid: 2046f65e-635d-4a13-80b2-d951e88dada4
  spec:
    sourcePod: network-check-source-6f78d59f99-z5j5h
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T15:43:31Z"
      message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.391086ms
      message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:43:31Z"
    - latency: 1.20189ms
      message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:42:31Z"
    - latency: 859.809µs
      message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:41:31Z"
    - latency: 874.249µs
      message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:40:31Z"
    - latency: 1.6721ms
      message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:39:31Z"
    - latency: 1.348819ms
      message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:38:31Z"
    - latency: 1.304089ms
      message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:37:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:36:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-102-to-network-check-target-ip-10-0-133-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-102.us-west-2.compute.internal
      uid: 9d5fd7cd-fed0-4ac1-9377-7e7e9e9c01cd
    resourceVersion: "11725"
    uid: 291396cd-1e47-4a39-b767-9094e8e70e5f
  spec:
    sourcePod: network-check-source-6f78d59f99-z5j5h
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T15:43:31Z"
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.993152ms
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:43:31Z"
    - latency: 1.855162ms
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:42:31Z"
    - latency: 1.866387ms
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:41:31Z"
    - latency: 1.936529ms
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:40:31Z"
    - latency: 2.087964ms
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:39:31Z"
    - latency: 1.930031ms
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:38:31Z"
    - latency: 1.900273ms
      message: 'network-check-target-ip-10-0-133-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:37:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:36:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-102-to-network-check-target-ip-10-0-136-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-102.us-west-2.compute.internal
      uid: 9d5fd7cd-fed0-4ac1-9377-7e7e9e9c01cd
    resourceVersion: "11726"
    uid: 872be7a4-664f-481d-b4dd-27099bcb89a6
  spec:
    sourcePod: network-check-source-6f78d59f99-z5j5h
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T15:43:31Z"
      message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.33745ms
      message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:43:31Z"
    - latency: 2.33025ms
      message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:42:31Z"
    - latency: 2.216338ms
      message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:41:31Z"
    - latency: 2.086366ms
      message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:40:31Z"
    - latency: 2.284075ms
      message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:39:31Z"
    - latency: 2.174935ms
      message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:38:31Z"
    - latency: 2.176847ms
      message: 'network-check-target-ip-10-0-136-152: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:37:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:36:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-102-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-102.us-west-2.compute.internal
      uid: 9d5fd7cd-fed0-4ac1-9377-7e7e9e9c01cd
    resourceVersion: "11415"
    uid: 93fd958f-b26c-4a39-bdc7-98415ec5c8fd
  spec:
    sourcePod: network-check-source-6f78d59f99-z5j5h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T15:42:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 955.123µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:42:31Z"
    - latency: 1.720072ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:42:31Z"
    - latency: 909.722µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:41:31Z"
    - latency: 1.83118ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:41:31Z"
    - latency: 840.268µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:40:31Z"
    - latency: 2.653411ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:40:31Z"
    - latency: 943.828µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:39:31Z"
    - latency: 3.089557ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:39:31Z"
    - latency: 889.404µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:38:31Z"
    - latency: 1.65255ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T15:38:31Z"
kind: List
metadata:
  resourceVersion: ""