apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:30:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-187-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-187.us-west-1.compute.internal
      uid: ae63597f-d3d6-4987-a236-1f7f9126cfca
    resourceVersion: "19233"
    uid: f4b0efa4-1185-4c30-9db5-3e79bd34e8bf
  spec:
    sourcePod: network-check-source-6f78d59f99-kq75r
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:37:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.192806ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:37:27Z"
    - latency: 1.306611ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:36:27Z"
    - latency: 994.802µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:35:27Z"
    - latency: 1.050218ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:34:27Z"
    - latency: 943.454µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:33:27Z"
    - latency: 954.778µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:32:27Z"
    - latency: 1.068251ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:31:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:30:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-187-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-187.us-west-1.compute.internal
      uid: ae63597f-d3d6-4987-a236-1f7f9126cfca
    resourceVersion: "18602"
    uid: 9dc0f0a6-e43d-4a23-86d9-8b2d1a93ceb3
  spec:
    sourcePod: network-check-source-6f78d59f99-kq75r
    targetEndpoint: adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:36:27Z"
      message: 'load-balancer-api-external: tcp connection to adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 56.559036ms
      message: 'load-balancer-api-external: tcp connection to adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:36:27Z"
    - latency: 6.605123ms
      message: 'load-balancer-api-external: resolved host name adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:36:27Z"
    - latency: 54.919479ms
      message: 'load-balancer-api-external: tcp connection to adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:35:27Z"
    - latency: 8.147383ms
      message: 'load-balancer-api-external: resolved host name adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:35:27Z"
    - latency: 52.348844ms
      message: 'load-balancer-api-external: tcp connection to adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:34:27Z"
    - latency: 6.798134ms
      message: 'load-balancer-api-external: resolved host name adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:34:27Z"
    - latency: 53.618378ms
      message: 'load-balancer-api-external: tcp connection to adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:33:27Z"
    - latency: 8.959074ms
      message: 'load-balancer-api-external: resolved host name adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:33:27Z"
    - latency: 55.980998ms
      message: 'load-balancer-api-external: tcp connection to adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:32:27Z"
    - latency: 6.870816ms
      message: 'load-balancer-api-external: resolved host name adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:32:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:30:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-187-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-187.us-west-1.compute.internal
      uid: ae63597f-d3d6-4987-a236-1f7f9126cfca
    resourceVersion: "18601"
    uid: f2261ffe-3c8a-402f-801d-19ee7a11610f
  spec:
    sourcePod: network-check-source-6f78d59f99-kq75r
    targetEndpoint: adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:36:27Z"
      message: 'load-balancer-api-internal: tcp connection to adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 56.537813ms
      message: 'load-balancer-api-internal: tcp connection to adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:36:27Z"
    - latency: 6.665478ms
      message: 'load-balancer-api-internal: resolved host name adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:36:27Z"
    - latency: 54.957008ms
      message: 'load-balancer-api-internal: tcp connection to adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:35:27Z"
    - latency: 8.135402ms
      message: 'load-balancer-api-internal: resolved host name adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:35:27Z"
    - latency: 52.565391ms
      message: 'load-balancer-api-internal: tcp connection to adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:34:27Z"
    - latency: 6.818764ms
      message: 'load-balancer-api-internal: resolved host name adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:34:27Z"
    - latency: 53.629124ms
      message: 'load-balancer-api-internal: tcp connection to adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:33:27Z"
    - latency: 8.982828ms
      message: 'load-balancer-api-internal: resolved host name adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:33:27Z"
    - latency: 55.957056ms
      message: 'load-balancer-api-internal: tcp connection to adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:32:27Z"
    - latency: 6.911476ms
      message: 'load-balancer-api-internal: resolved host name adb7e0907d0814a26adefe13e52276af-493a23b380b01ace.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:32:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:30:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-187-to-network-check-target-ip-10-0-135-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-187.us-west-1.compute.internal
      uid: ae63597f-d3d6-4987-a236-1f7f9126cfca
    resourceVersion: "19231"
    uid: 378e9931-cbb7-46b8-916c-9e42345b894d
  spec:
    sourcePod: network-check-source-6f78d59f99-kq75r
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:37:27Z"
      message: 'network-check-target-ip-10-0-135-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.894159ms
      message: 'network-check-target-ip-10-0-135-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:37:27Z"
    - latency: 1.856666ms
      message: 'network-check-target-ip-10-0-135-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:36:27Z"
    - latency: 2.168821ms
      message: 'network-check-target-ip-10-0-135-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:35:27Z"
    - latency: 2.115263ms
      message: 'network-check-target-ip-10-0-135-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:34:27Z"
    - latency: 2.331293ms
      message: 'network-check-target-ip-10-0-135-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:33:27Z"
    - latency: 1.877873ms
      message: 'network-check-target-ip-10-0-135-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:32:27Z"
    - latency: 2.25674ms
      message: 'network-check-target-ip-10-0-135-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:31:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:30:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-187-to-network-check-target-ip-10-0-137-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-187.us-west-1.compute.internal
      uid: ae63597f-d3d6-4987-a236-1f7f9126cfca
    resourceVersion: "19230"
    uid: 79cf6e2a-f333-411f-899b-871cc94a711e
  spec:
    sourcePod: network-check-source-6f78d59f99-kq75r
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:37:27Z"
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.630359ms
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:37:27Z"
    - latency: 1.57996ms
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:36:27Z"
    - latency: 1.377768ms
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:35:27Z"
    - latency: 1.308479ms
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:34:27Z"
    - latency: 1.967165ms
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:33:27Z"
    - latency: 1.686888ms
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:32:27Z"
    - latency: 1.764239ms
      message: 'network-check-target-ip-10-0-137-192: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:31:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:30:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-187-to-network-check-target-ip-10-0-143-187
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-187.us-west-1.compute.internal
      uid: ae63597f-d3d6-4987-a236-1f7f9126cfca
    resourceVersion: "19229"
    uid: 2301bb5f-be72-4e38-99ad-2ad7900d810f
  spec:
    sourcePod: network-check-source-6f78d59f99-kq75r
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:37:27Z"
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.363741ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:37:27Z"
    - latency: 1.44791ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:36:27Z"
    - latency: 1.045758ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:35:27Z"
    - latency: 1.274033ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:34:27Z"
    - latency: 1.256137ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:33:27Z"
    - latency: 1.328264ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:32:27Z"
    - latency: 1.621926ms
      message: 'network-check-target-ip-10-0-143-187: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:31:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:30:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-187-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-187.us-west-1.compute.internal
      uid: ae63597f-d3d6-4987-a236-1f7f9126cfca
    resourceVersion: "18597"
    uid: d26a2272-8119-49e3-b0c8-167ca298ad67
  spec:
    sourcePod: network-check-source-6f78d59f99-kq75r
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:36:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.041313ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:36:27Z"
    - latency: 1.961903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:36:27Z"
    - latency: 1.847044ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:35:27Z"
    - latency: 1.839845ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:35:27Z"
    - latency: 1.341694ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:34:27Z"
    - latency: 1.853246ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:34:27Z"
    - latency: 780.139µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:33:27Z"
    - latency: 2.254812ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:33:27Z"
    - latency: 1.717375ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:32:27Z"
    - latency: 1.698867ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:32:27Z"
kind: List
metadata:
  resourceVersion: ""