apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T08:06:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-2-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-2.ec2.internal
      uid: d2a65ca5-0bc5-43e4-8f6e-0a78c8bee59f
    resourceVersion: "14875"
    uid: 26008450-662c-4620-b143-a047888ca2bf
  spec:
    sourcePod: network-check-source-56d84b9f44-rp68z
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T08:13:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 985.931µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:13:33Z"
    - latency: 1.187633ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:12:33Z"
    - latency: 1.114892ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:11:33Z"
    - latency: 941.195µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:10:33Z"
    - latency: 966.675µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:09:33Z"
    - latency: 921.476µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:08:33Z"
    - latency: 899.441µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:07:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T08:06:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-2-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-2.ec2.internal
      uid: d2a65ca5-0bc5-43e4-8f6e-0a78c8bee59f
    resourceVersion: "14541"
    uid: faff7f19-059d-4bc0-9a06-6e3628d55b94
  spec:
    sourcePod: network-check-source-56d84b9f44-rp68z
    targetEndpoint: adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T08:12:33Z"
      message: 'load-balancer-api-external: tcp connection to adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.662255ms
      message: 'load-balancer-api-external: tcp connection to adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:12:33Z"
    - latency: 12.585864ms
      message: 'load-balancer-api-external: resolved host name adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T08:12:33Z"
    - latency: 4.705092ms
      message: 'load-balancer-api-external: tcp connection to adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:11:33Z"
    - latency: 10.654713ms
      message: 'load-balancer-api-external: resolved host name adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T08:11:33Z"
    - latency: 4.199416ms
      message: 'load-balancer-api-external: tcp connection to adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:10:33Z"
    - latency: 7.856023ms
      message: 'load-balancer-api-external: resolved host name adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T08:10:33Z"
    - latency: 4.481039ms
      message: 'load-balancer-api-external: tcp connection to adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:09:33Z"
    - latency: 8.332346ms
      message: 'load-balancer-api-external: resolved host name adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T08:09:33Z"
    - latency: 5.044051ms
      message: 'load-balancer-api-external: tcp connection to adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:08:33Z"
    - latency: 8.27386ms
      message: 'load-balancer-api-external: resolved host name adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T08:08:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T08:06:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-2-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-2.ec2.internal
      uid: d2a65ca5-0bc5-43e4-8f6e-0a78c8bee59f
    resourceVersion: "14542"
    uid: 3b03902f-5ee5-4337-a32a-02e994c9a124
  spec:
    sourcePod: network-check-source-56d84b9f44-rp68z
    targetEndpoint: adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T08:12:33Z"
      message: 'load-balancer-api-internal: tcp connection to adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.678948ms
      message: 'load-balancer-api-internal: tcp connection to adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:12:33Z"
    - latency: 12.604858ms
      message: 'load-balancer-api-internal: resolved host name adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T08:12:33Z"
    - latency: 4.698122ms
      message: 'load-balancer-api-internal: tcp connection to adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:11:33Z"
    - latency: 10.57236ms
      message: 'load-balancer-api-internal: resolved host name adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T08:11:33Z"
    - latency: 4.309231ms
      message: 'load-balancer-api-internal: tcp connection to adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:10:33Z"
    - latency: 7.800719ms
      message: 'load-balancer-api-internal: resolved host name adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T08:10:33Z"
    - latency: 4.509709ms
      message: 'load-balancer-api-internal: tcp connection to adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:09:33Z"
    - latency: 8.286889ms
      message: 'load-balancer-api-internal: resolved host name adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T08:09:33Z"
    - latency: 5.066337ms
      message: 'load-balancer-api-internal: tcp connection to adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:08:33Z"
    - latency: 8.195524ms
      message: 'load-balancer-api-internal: resolved host name adce81dadf9194e18870dbddc881fd4a-dc7e1029946c157f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T08:08:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T08:06:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-2-to-network-check-target-ip-10-0-134-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-2.ec2.internal
      uid: d2a65ca5-0bc5-43e4-8f6e-0a78c8bee59f
    resourceVersion: "14873"
    uid: 63341a57-2dd6-4e2b-b9e8-82f969b28b62
  spec:
    sourcePod: network-check-source-56d84b9f44-rp68z
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T08:13:33Z"
      message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.989228ms
      message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:13:33Z"
    - latency: 2.386466ms
      message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:12:33Z"
    - latency: 2.623625ms
      message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:11:33Z"
    - latency: 2.307273ms
      message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:10:33Z"
    - latency: 2.100328ms
      message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:09:33Z"
    - latency: 2.111012ms
      message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:08:33Z"
    - latency: 15.766474ms
      message: 'network-check-target-ip-10-0-134-166: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:07:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T08:06:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-2-to-network-check-target-ip-10-0-141-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-2.ec2.internal
      uid: d2a65ca5-0bc5-43e4-8f6e-0a78c8bee59f
    resourceVersion: "14874"
    uid: d4f851f8-77f0-4ca4-8820-9a7ff1e41f94
  spec:
    sourcePod: network-check-source-56d84b9f44-rp68z
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T08:13:33Z"
      message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.137747ms
      message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:13:33Z"
    - latency: 2.134088ms
      message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:12:33Z"
    - latency: 1.981637ms
      message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:11:33Z"
    - latency: 2.264186ms
      message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:10:33Z"
    - latency: 2.191078ms
      message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:09:33Z"
    - latency: 2.173557ms
      message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:08:33Z"
    - latency: 2.453002ms
      message: 'network-check-target-ip-10-0-141-156: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:07:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T08:06:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-2-to-network-check-target-ip-10-0-143-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-2.ec2.internal
      uid: d2a65ca5-0bc5-43e4-8f6e-0a78c8bee59f
    resourceVersion: "14872"
    uid: 4fcfd5b9-f9ee-4cf7-99c5-3affc5558054
  spec:
    sourcePod: network-check-source-56d84b9f44-rp68z
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T08:13:33Z"
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 857.638µs
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:13:33Z"
    - latency: 838.213µs
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:12:33Z"
    - latency: 804.669µs
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:11:33Z"
    - latency: 641.599µs
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:10:33Z"
    - latency: 851.766µs
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:09:33Z"
    - latency: 854.718µs
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:08:33Z"
    - latency: 1.17341ms
      message: 'network-check-target-ip-10-0-143-2: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:07:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T08:06:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-2-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-2.ec2.internal
      uid: d2a65ca5-0bc5-43e4-8f6e-0a78c8bee59f
    resourceVersion: "14540"
    uid: f85cd313-8dda-4eeb-8f5e-60df65854e48
  spec:
    sourcePod: network-check-source-56d84b9f44-rp68z
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T08:12:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.101194ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:12:33Z"
    - latency: 1.50991ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T08:12:33Z"
    - latency: 752.394µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:11:33Z"
    - latency: 2.002904ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T08:11:33Z"
    - latency: 1.534365ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:10:33Z"
    - latency: 1.678189ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T08:10:33Z"
    - latency: 702.604µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:09:33Z"
    - latency: 1.623316ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T08:09:33Z"
    - latency: 784.783µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T08:08:33Z"
    - latency: 1.5895ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T08:08:33Z"
kind: List
metadata:
  resourceVersion: ""