apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:44:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-14-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-14.us-west-1.compute.internal
      uid: 834d190e-5d38-481b-8ed3-cb59415d9f7f
    resourceVersion: "11616"
    uid: fea54ea6-4b73-489f-97f8-d715f7507ffc
  spec:
    sourcePod: network-check-source-6f78d59f99-xrqpk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T09:51:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 972.875µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:51:52Z"
    - latency: 747.118µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:50:52Z"
    - latency: 955.066µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:49:52Z"
    - latency: 882.016µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:48:52Z"
    - latency: 1.092417ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:47:52Z"
    - latency: 1.050376ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:46:52Z"
    - latency: 1.110457ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:45:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:44:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-14-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-14.us-west-1.compute.internal
      uid: 834d190e-5d38-481b-8ed3-cb59415d9f7f
    resourceVersion: "11460"
    uid: acc6d9b4-7bba-42cc-be5d-06629ddabdfb
  spec:
    sourcePod: network-check-source-6f78d59f99-xrqpk
    targetEndpoint: a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T09:50:52Z"
      message: 'load-balancer-api-external: tcp connection to a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.257298ms
      message: 'load-balancer-api-external: tcp connection to a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:50:52Z"
    - latency: 7.989583ms
      message: 'load-balancer-api-external: resolved host name a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:50:52Z"
    - latency: 53.395178ms
      message: 'load-balancer-api-external: tcp connection to a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:49:52Z"
    - latency: 6.236453ms
      message: 'load-balancer-api-external: resolved host name a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:49:52Z"
    - latency: 54.94303ms
      message: 'load-balancer-api-external: tcp connection to a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:48:52Z"
    - latency: 7.943424ms
      message: 'load-balancer-api-external: resolved host name a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:48:52Z"
    - latency: 53.81299ms
      message: 'load-balancer-api-external: tcp connection to a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:47:52Z"
    - latency: 8.252325ms
      message: 'load-balancer-api-external: resolved host name a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:47:52Z"
    - latency: 52.190772ms
      message: 'load-balancer-api-external: tcp connection to a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:46:52Z"
    - latency: 6.392116ms
      message: 'load-balancer-api-external: resolved host name a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:46:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:44:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-14-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-14.us-west-1.compute.internal
      uid: 834d190e-5d38-481b-8ed3-cb59415d9f7f
    resourceVersion: "11461"
    uid: bf93ef65-6955-441a-a1a2-0df713be7089
  spec:
    sourcePod: network-check-source-6f78d59f99-xrqpk
    targetEndpoint: a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T09:50:52Z"
      message: 'load-balancer-api-internal: tcp connection to a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.874362ms
      message: 'load-balancer-api-internal: tcp connection to a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:50:52Z"
    - latency: 8.045188ms
      message: 'load-balancer-api-internal: resolved host name a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:50:52Z"
    - latency: 53.383468ms
      message: 'load-balancer-api-internal: tcp connection to a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:49:52Z"
    - latency: 6.310633ms
      message: 'load-balancer-api-internal: resolved host name a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:49:52Z"
    - latency: 57.425986ms
      message: 'load-balancer-api-internal: tcp connection to a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:48:52Z"
    - latency: 8.002535ms
      message: 'load-balancer-api-internal: resolved host name a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:48:52Z"
    - latency: 53.770551ms
      message: 'load-balancer-api-internal: tcp connection to a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:47:52Z"
    - latency: 8.297948ms
      message: 'load-balancer-api-internal: resolved host name a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:47:52Z"
    - latency: 52.863919ms
      message: 'load-balancer-api-internal: tcp connection to a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:46:52Z"
    - latency: 6.424019ms
      message: 'load-balancer-api-internal: resolved host name a3d7df8747ad44ef09027db7d42ccbe0-ee142b4a131f672d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:46:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:44:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-14-to-network-check-target-ip-10-0-128-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-14.us-west-1.compute.internal
      uid: 834d190e-5d38-481b-8ed3-cb59415d9f7f
    resourceVersion: "11615"
    uid: 74635156-4eaf-47df-ba95-991147dbea5f
  spec:
    sourcePod: network-check-source-6f78d59f99-xrqpk
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T09:51:52Z"
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.030636ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:51:52Z"
    - latency: 2.141029ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:50:52Z"
    - latency: 2.181166ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:49:52Z"
    - latency: 2.017447ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:48:52Z"
    - latency: 2.212368ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:47:52Z"
    - latency: 2.016242ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:46:52Z"
    - latency: 2.299931ms
      message: 'network-check-target-ip-10-0-128-178: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:45:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:44:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-14-to-network-check-target-ip-10-0-139-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-14.us-west-1.compute.internal
      uid: 834d190e-5d38-481b-8ed3-cb59415d9f7f
    resourceVersion: "11614"
    uid: ef8740cc-6933-42ad-8090-eb00db74bb41
  spec:
    sourcePod: network-check-source-6f78d59f99-xrqpk
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T09:51:52Z"
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.070795ms
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:51:52Z"
    - latency: 1.869966ms
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:50:52Z"
    - latency: 1.851675ms
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:49:52Z"
    - latency: 2.035902ms
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:48:52Z"
    - latency: 2.006398ms
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:47:52Z"
    - latency: 2.070856ms
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:46:52Z"
    - latency: 2.291464ms
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:45:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:44:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-14-to-network-check-target-ip-10-0-141-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-14.us-west-1.compute.internal
      uid: 834d190e-5d38-481b-8ed3-cb59415d9f7f
    resourceVersion: "11613"
    uid: 537dda61-14b4-4132-9b14-378d7dd87061
  spec:
    sourcePod: network-check-source-6f78d59f99-xrqpk
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T09:51:52Z"
      message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.586945ms
      message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:51:52Z"
    - latency: 974.059µs
      message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:50:52Z"
    - latency: 938.722µs
      message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:49:52Z"
    - latency: 1.070605ms
      message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:48:52Z"
    - latency: 850.422µs
      message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:47:52Z"
    - latency: 1.316334ms
      message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:46:52Z"
    - latency: 1.806741ms
      message: 'network-check-target-ip-10-0-141-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:45:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:44:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-14-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-14.us-west-1.compute.internal
      uid: 834d190e-5d38-481b-8ed3-cb59415d9f7f
    resourceVersion: "11458"
    uid: 1d3b2e96-6d31-48ce-be7c-e4c300e16496
  spec:
    sourcePod: network-check-source-6f78d59f99-xrqpk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T09:50:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 812.374µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:50:52Z"
    - latency: 2.117909ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:50:52Z"
    - latency: 814.155µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:49:52Z"
    - latency: 1.589111ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:49:52Z"
    - latency: 879.092µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:48:52Z"
    - latency: 1.585764ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:48:52Z"
    - latency: 737.443µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:47:52Z"
    - latency: 1.698232ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:47:52Z"
    - latency: 876.857µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:46:52Z"
    - latency: 2.075761ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:46:52Z"
kind: List
metadata:
  resourceVersion: ""