apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:44:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-90-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-90.us-west-2.compute.internal
      uid: 86adf730-6243-4681-a14e-11cd8ba55739
    resourceVersion: "12058"
    uid: c272ba35-346e-421e-a2a0-8ffd93a09fca
  spec:
    sourcePod: network-check-source-6f78d59f99-mqwjv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T09:51:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 858.798µ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:38Z"
    - latency: 1.149087ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:50:38Z"
    - latency: 909.933µ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:38Z"
    - latency: 957.763µ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:38Z"
    - latency: 1.005537ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:47:38Z"
    - latency: 884.883µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:46:38Z"
    - latency: 1.592047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:45:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:44:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-90-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-90.us-west-2.compute.internal
      uid: 86adf730-6243-4681-a14e-11cd8ba55739
    resourceVersion: "13079"
    uid: edfc71d1-7ad1-4dd6-b324-827a60afc79a
  spec:
    sourcePod: network-check-source-6f78d59f99-mqwjv
    targetEndpoint: ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T09:50:38Z"
      message: 'load-balancer-api-external: tcp connection to ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.810736ms
      message: 'load-balancer-api-external: tcp connection to ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:56:38Z"
    - latency: 6.583505ms
      message: 'load-balancer-api-external: resolved host name ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:56:38Z"
    - latency: 58.096428ms
      message: 'load-balancer-api-external: tcp connection to ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:55:38Z"
    - latency: 7.045971ms
      message: 'load-balancer-api-external: resolved host name ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:55:38Z"
    - latency: 50.235878ms
      message: 'load-balancer-api-external: tcp connection to ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:54:38Z"
    - latency: 6.357529ms
      message: 'load-balancer-api-external: resolved host name ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:54:38Z"
    - latency: 48.995393ms
      message: 'load-balancer-api-external: tcp connection to ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:53:38Z"
    - latency: 7.115712ms
      message: 'load-balancer-api-external: resolved host name ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:53:38Z"
    - latency: 54.724446ms
      message: 'load-balancer-api-external: tcp connection to ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:52:38Z"
    - latency: 6.695529ms
      message: 'load-balancer-api-external: resolved host name ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:52:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:44:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-90-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-90.us-west-2.compute.internal
      uid: 86adf730-6243-4681-a14e-11cd8ba55739
    resourceVersion: "13078"
    uid: be002100-a27e-4232-bab0-f0d4823f53e7
  spec:
    sourcePod: network-check-source-6f78d59f99-mqwjv
    targetEndpoint: ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T09:50:38Z"
      message: 'load-balancer-api-internal: tcp connection to ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.864032ms
      message: 'load-balancer-api-internal: tcp connection to ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:56:38Z"
    - latency: 6.526295ms
      message: 'load-balancer-api-internal: resolved host name ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:56:38Z"
    - latency: 49.620658ms
      message: 'load-balancer-api-internal: tcp connection to ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:55:38Z"
    - latency: 6.984022ms
      message: 'load-balancer-api-internal: resolved host name ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:55:38Z"
    - latency: 52.429107ms
      message: 'load-balancer-api-internal: tcp connection to ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:54:38Z"
    - latency: 6.228135ms
      message: 'load-balancer-api-internal: resolved host name ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:54:38Z"
    - latency: 58.084642ms
      message: 'load-balancer-api-internal: tcp connection to ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:53:38Z"
    - latency: 7.065594ms
      message: 'load-balancer-api-internal: resolved host name ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:53:38Z"
    - latency: 58.148985ms
      message: 'load-balancer-api-internal: tcp connection to ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:52:38Z"
    - latency: 6.609031ms
      message: 'load-balancer-api-internal: resolved host name ac48edef0ce974bfb8444d55dce6c2c7-5e796d2b90c1cdd0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:52:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:44:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-90-to-network-check-target-ip-10-0-130-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-90.us-west-2.compute.internal
      uid: 86adf730-6243-4681-a14e-11cd8ba55739
    resourceVersion: "12056"
    uid: fca77cbb-dc88-4f40-8ba0-a4c767ad4c5e
  spec:
    sourcePod: network-check-source-6f78d59f99-mqwjv
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T09:51:38Z"
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.24902ms
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:51:38Z"
    - latency: 2.123061ms
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:50:38Z"
    - latency: 2.029557ms
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:49:38Z"
    - latency: 2.189487ms
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:48:38Z"
    - latency: 2.16999ms
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:47:38Z"
    - latency: 2.249847ms
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:46:38Z"
    - latency: 2.430523ms
      message: 'network-check-target-ip-10-0-130-9: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:45:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:44:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-90-to-network-check-target-ip-10-0-138-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-90.us-west-2.compute.internal
      uid: 86adf730-6243-4681-a14e-11cd8ba55739
    resourceVersion: "12055"
    uid: b05cbf1f-bc2f-4c9f-b800-69f2d61b5f75
  spec:
    sourcePod: network-check-source-6f78d59f99-mqwjv
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T09:51:38Z"
      message: 'network-check-target-ip-10-0-138-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.659314ms
      message: 'network-check-target-ip-10-0-138-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:51:38Z"
    - latency: 1.951087ms
      message: 'network-check-target-ip-10-0-138-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:50:38Z"
    - latency: 1.728925ms
      message: 'network-check-target-ip-10-0-138-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:49:38Z"
    - latency: 1.776652ms
      message: 'network-check-target-ip-10-0-138-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:48:38Z"
    - latency: 1.893676ms
      message: 'network-check-target-ip-10-0-138-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:47:38Z"
    - latency: 1.841884ms
      message: 'network-check-target-ip-10-0-138-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:46:38Z"
    - latency: 2.118308ms
      message: 'network-check-target-ip-10-0-138-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:45:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:44:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-90-to-network-check-target-ip-10-0-140-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-90.us-west-2.compute.internal
      uid: 86adf730-6243-4681-a14e-11cd8ba55739
    resourceVersion: "12054"
    uid: 4f9afa9a-cf2d-4acb-a68d-aff3b4239ca7
  spec:
    sourcePod: network-check-source-6f78d59f99-mqwjv
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T09:51:38Z"
      message: 'network-check-target-ip-10-0-140-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 819.279µs
      message: 'network-check-target-ip-10-0-140-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:51:38Z"
    - latency: 900.156µs
      message: 'network-check-target-ip-10-0-140-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:50:38Z"
    - latency: 1.15425ms
      message: 'network-check-target-ip-10-0-140-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:49:38Z"
    - latency: 1.104663ms
      message: 'network-check-target-ip-10-0-140-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:48:38Z"
    - latency: 1.316711ms
      message: 'network-check-target-ip-10-0-140-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:47:38Z"
    - latency: 835.034µs
      message: 'network-check-target-ip-10-0-140-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:46:38Z"
    - latency: 1.261068ms
      message: 'network-check-target-ip-10-0-140-90: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:45:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T09:44:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-90-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-90.us-west-2.compute.internal
      uid: 86adf730-6243-4681-a14e-11cd8ba55739
    resourceVersion: "13077"
    uid: edbdc97e-2613-49fa-bbdd-7226dbcc80a3
  spec:
    sourcePod: network-check-source-6f78d59f99-mqwjv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T09:50:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.141424ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:56:38Z"
    - latency: 2.094594ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:56:38Z"
    - latency: 847.371µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:55:38Z"
    - latency: 2.331376ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:55:38Z"
    - latency: 925.815µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:54:38Z"
    - latency: 1.690708ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:54:38Z"
    - latency: 1.06929ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:53:38Z"
    - latency: 1.838527ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:53:38Z"
    - latency: 961.701µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T09:52:38Z"
    - latency: 1.988765ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T09:52:38Z"
kind: List
metadata:
  resourceVersion: ""