apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T00:33:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-8-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-8.ec2.internal
      uid: 2b3e3b3e-9d59-4860-9541-c755067cbfac
    resourceVersion: "25589"
    uid: b1eecf68-b97b-4d09-a140-eb5f6dabd469
  spec:
    sourcePod: network-check-source-6947749cfc-srm2g
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T00:40:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.530911ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:40:38Z"
    - latency: 730.394µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:39:38Z"
    - latency: 1.217057ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:38:38Z"
    - latency: 1.167627ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:37:38Z"
    - latency: 1.079985ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:36:38Z"
    - latency: 1.572026ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:35:38Z"
    - latency: 964.012µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:34:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T00:33:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-8-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-8.ec2.internal
      uid: 2b3e3b3e-9d59-4860-9541-c755067cbfac
    resourceVersion: "24358"
    uid: 23b561bb-0de0-4e31-8d2c-4e9565d57f6f
  spec:
    sourcePod: network-check-source-6947749cfc-srm2g
    targetEndpoint: ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T00:39:38Z"
      message: 'load-balancer-api-external: tcp connection to ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.690294ms
      message: 'load-balancer-api-external: tcp connection to ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:39:38Z"
    - latency: 7.126399ms
      message: 'load-balancer-api-external: resolved host name ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T00:39:38Z"
    - latency: 4.225251ms
      message: 'load-balancer-api-external: tcp connection to ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:38:38Z"
    - latency: 9.709151ms
      message: 'load-balancer-api-external: resolved host name ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T00:38:38Z"
    - latency: 5.144126ms
      message: 'load-balancer-api-external: tcp connection to ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:37:38Z"
    - latency: 9.450353ms
      message: 'load-balancer-api-external: resolved host name ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T00:37:38Z"
    - latency: 4.055957ms
      message: 'load-balancer-api-external: tcp connection to ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:36:38Z"
    - latency: 8.545555ms
      message: 'load-balancer-api-external: resolved host name ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T00:36:38Z"
    - latency: 3.944471ms
      message: 'load-balancer-api-external: tcp connection to ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:35:38Z"
    - latency: 10.935125ms
      message: 'load-balancer-api-external: resolved host name ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T00:35:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T00:33:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-8-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-8.ec2.internal
      uid: 2b3e3b3e-9d59-4860-9541-c755067cbfac
    resourceVersion: "24357"
    uid: 2b397d8a-7cae-4689-92f1-854693d489a7
  spec:
    sourcePod: network-check-source-6947749cfc-srm2g
    targetEndpoint: ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T00:39:38Z"
      message: 'load-balancer-api-internal: tcp connection to ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.25789ms
      message: 'load-balancer-api-internal: tcp connection to ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:39:38Z"
    - latency: 7.182652ms
      message: 'load-balancer-api-internal: resolved host name ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T00:39:38Z"
    - latency: 3.339705ms
      message: 'load-balancer-api-internal: tcp connection to ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:38:38Z"
    - latency: 9.815701ms
      message: 'load-balancer-api-internal: resolved host name ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T00:38:38Z"
    - latency: 5.126564ms
      message: 'load-balancer-api-internal: tcp connection to ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:37:38Z"
    - latency: 9.250875ms
      message: 'load-balancer-api-internal: resolved host name ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T00:37:38Z"
    - latency: 3.41116ms
      message: 'load-balancer-api-internal: tcp connection to ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:36:38Z"
    - latency: 8.516644ms
      message: 'load-balancer-api-internal: resolved host name ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T00:36:38Z"
    - latency: 3.213145ms
      message: 'load-balancer-api-internal: tcp connection to ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:35:38Z"
    - latency: 11.025921ms
      message: 'load-balancer-api-internal: resolved host name ac80cbea1c2aa418c8305f436bd876e5-31fc3f43fc04115e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T00:35:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T00:33:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-8-to-network-check-target-ip-10-0-131-151
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-8.ec2.internal
      uid: 2b3e3b3e-9d59-4860-9541-c755067cbfac
    resourceVersion: "25586"
    uid: 2e7a893d-f5af-4145-b2c4-eb1c7bc387fa
  spec:
    sourcePod: network-check-source-6947749cfc-srm2g
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T00:40:38Z"
      message: 'network-check-target-ip-10-0-131-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.07489ms
      message: 'network-check-target-ip-10-0-131-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:40:38Z"
    - latency: 1.911781ms
      message: 'network-check-target-ip-10-0-131-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:39:38Z"
    - latency: 2.741293ms
      message: 'network-check-target-ip-10-0-131-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:38:38Z"
    - latency: 2.352581ms
      message: 'network-check-target-ip-10-0-131-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:37:38Z"
    - latency: 2.132791ms
      message: 'network-check-target-ip-10-0-131-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:36:38Z"
    - latency: 1.90675ms
      message: 'network-check-target-ip-10-0-131-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:35:38Z"
    - latency: 2.081862ms
      message: 'network-check-target-ip-10-0-131-151: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:34:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T00:33:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-8-to-network-check-target-ip-10-0-141-24
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-8.ec2.internal
      uid: 2b3e3b3e-9d59-4860-9541-c755067cbfac
    resourceVersion: "25588"
    uid: f25f1948-128a-4bad-9f0d-70c0a7c6a722
  spec:
    sourcePod: network-check-source-6947749cfc-srm2g
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T00:40:38Z"
      message: 'network-check-target-ip-10-0-141-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.812373ms
      message: 'network-check-target-ip-10-0-141-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:40:38Z"
    - latency: 1.69679ms
      message: 'network-check-target-ip-10-0-141-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:39:38Z"
    - latency: 1.931645ms
      message: 'network-check-target-ip-10-0-141-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:38:38Z"
    - latency: 1.702025ms
      message: 'network-check-target-ip-10-0-141-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:37:38Z"
    - latency: 1.832656ms
      message: 'network-check-target-ip-10-0-141-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:36:38Z"
    - latency: 1.950739ms
      message: 'network-check-target-ip-10-0-141-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:35:38Z"
    - latency: 2.040622ms
      message: 'network-check-target-ip-10-0-141-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:34:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T00:33:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-8-to-network-check-target-ip-10-0-142-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-8.ec2.internal
      uid: 2b3e3b3e-9d59-4860-9541-c755067cbfac
    resourceVersion: "25587"
    uid: d3280787-a649-4a02-8288-349ed44f7a7b
  spec:
    sourcePod: network-check-source-6947749cfc-srm2g
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T00:40:38Z"
      message: 'network-check-target-ip-10-0-142-8: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.089652ms
      message: 'network-check-target-ip-10-0-142-8: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:40:38Z"
    - latency: 877.642µs
      message: 'network-check-target-ip-10-0-142-8: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:39:38Z"
    - latency: 1.645009ms
      message: 'network-check-target-ip-10-0-142-8: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:38:38Z"
    - latency: 1.5527ms
      message: 'network-check-target-ip-10-0-142-8: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:37:38Z"
    - latency: 738.777µs
      message: 'network-check-target-ip-10-0-142-8: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:36:38Z"
    - latency: 879.918µs
      message: 'network-check-target-ip-10-0-142-8: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:35:38Z"
    - latency: 1.097034ms
      message: 'network-check-target-ip-10-0-142-8: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:34:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T00:33:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-8-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-8.ec2.internal
      uid: 2b3e3b3e-9d59-4860-9541-c755067cbfac
    resourceVersion: "24356"
    uid: 43572639-dd43-4f2c-936c-550ddec3dbf0
  spec:
    sourcePod: network-check-source-6947749cfc-srm2g
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T00:39:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 808.84µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:39:38Z"
    - latency: 2.225989ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T00:39:38Z"
    - latency: 1.008647ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:38:38Z"
    - latency: 2.232971ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T00:38:38Z"
    - latency: 934.898µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:37:38Z"
    - latency: 2.367448ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T00:37:38Z"
    - latency: 1.050417ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:36:38Z"
    - latency: 1.861905ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T00:36:38Z"
    - latency: 679.563µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T00:35:38Z"
    - latency: 2.012656ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T00:35:38Z"
kind: List
metadata:
  resourceVersion: ""