apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:50:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-108-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-108.ec2.internal
      uid: f24eada1-543a-43da-b111-7e03ccd4c498
    resourceVersion: "14581"
    uid: a7ab3a99-cb3c-4179-8944-701e315a0e6f
  spec:
    sourcePod: network-check-source-6f8b768455-pcgrw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:57:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.012µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:57:27Z"
    - latency: 1.029948ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:56:27Z"
    - latency: 1.263673ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:55:27Z"
    - latency: 896.599µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:54:27Z"
    - latency: 1.193211ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:53:27Z"
    - latency: 903.141µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:52:27Z"
    - latency: 1.103174ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:51:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:50:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-108-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-108.ec2.internal
      uid: f24eada1-543a-43da-b111-7e03ccd4c498
    resourceVersion: "16772"
    uid: b35f39c3-557e-4261-968a-bff66e3dad7d
  spec:
    sourcePod: network-check-source-6f8b768455-pcgrw
    targetEndpoint: a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:56:27Z"
      message: 'load-balancer-api-external: tcp connection to a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.55127ms
      message: 'load-balancer-api-external: tcp connection to a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T04:02:27Z"
    - latency: 8.116912ms
      message: 'load-balancer-api-external: resolved host name a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T04:02:27Z"
    - latency: 4.8316ms
      message: 'load-balancer-api-external: tcp connection to a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T04:01:27Z"
    - latency: 8.342835ms
      message: 'load-balancer-api-external: resolved host name a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T04:01:27Z"
    - latency: 4.579343ms
      message: 'load-balancer-api-external: tcp connection to a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T04:00:27Z"
    - latency: 9.747027ms
      message: 'load-balancer-api-external: resolved host name a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T04:00:27Z"
    - latency: 5.281191ms
      message: 'load-balancer-api-external: tcp connection to a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:59:27Z"
    - latency: 9.617076ms
      message: 'load-balancer-api-external: resolved host name a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:59:27Z"
    - latency: 3.838957ms
      message: 'load-balancer-api-external: tcp connection to a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:58:27Z"
    - latency: 7.558836ms
      message: 'load-balancer-api-external: resolved host name a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:58:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:50:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-108-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-108.ec2.internal
      uid: f24eada1-543a-43da-b111-7e03ccd4c498
    resourceVersion: "16771"
    uid: ba897a0d-5bf7-4be0-84ec-0eb2fae6315c
  spec:
    sourcePod: network-check-source-6f8b768455-pcgrw
    targetEndpoint: a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:56:27Z"
      message: 'load-balancer-api-internal: tcp connection to a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.576259ms
      message: 'load-balancer-api-internal: tcp connection to a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T04:02:27Z"
    - latency: 8.037737ms
      message: 'load-balancer-api-internal: resolved host name a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T04:02:27Z"
    - latency: 4.65896ms
      message: 'load-balancer-api-internal: tcp connection to a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T04:01:27Z"
    - latency: 8.240178ms
      message: 'load-balancer-api-internal: resolved host name a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T04:01:27Z"
    - latency: 4.650314ms
      message: 'load-balancer-api-internal: tcp connection to a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T04:00:27Z"
    - latency: 9.677243ms
      message: 'load-balancer-api-internal: resolved host name a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T04:00:27Z"
    - latency: 5.267302ms
      message: 'load-balancer-api-internal: tcp connection to a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:59:27Z"
    - latency: 9.796043ms
      message: 'load-balancer-api-internal: resolved host name a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:59:27Z"
    - latency: 3.878287ms
      message: 'load-balancer-api-internal: tcp connection to a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:58:27Z"
    - latency: 7.454412ms
      message: 'load-balancer-api-internal: resolved host name a3370bfc4f69042fcab5c89a1ba25d34-539734f78fc0a5cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:58:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:50:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-108-to-network-check-target-ip-10-0-135-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-108.ec2.internal
      uid: f24eada1-543a-43da-b111-7e03ccd4c498
    resourceVersion: "14580"
    uid: 60aa8c3e-5603-4028-ae9d-2f0e2069f494
  spec:
    sourcePod: network-check-source-6f8b768455-pcgrw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:57:27Z"
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.382217ms
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:57:27Z"
    - latency: 2.327513ms
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:56:27Z"
    - latency: 2.438165ms
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:55:27Z"
    - latency: 8.718529ms
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:54:27Z"
    - latency: 2.51708ms
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:53:27Z"
    - latency: 2.397021ms
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:52:27Z"
    - latency: 2.426095ms
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:51:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:50:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-108-to-network-check-target-ip-10-0-140-252
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-108.ec2.internal
      uid: f24eada1-543a-43da-b111-7e03ccd4c498
    resourceVersion: "14579"
    uid: c9555d54-8e07-4370-a3ab-6669886c4292
  spec:
    sourcePod: network-check-source-6f8b768455-pcgrw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:57:27Z"
      message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.355167ms
      message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:57:27Z"
    - latency: 2.209044ms
      message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:56:27Z"
    - latency: 2.407035ms
      message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:55:27Z"
    - latency: 2.002592ms
      message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:54:27Z"
    - latency: 2.564838ms
      message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:53:27Z"
    - latency: 1.968847ms
      message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:52:27Z"
    - latency: 2.059176ms
      message: 'network-check-target-ip-10-0-140-252: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:51:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:50:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-108-to-network-check-target-ip-10-0-142-108
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-108.ec2.internal
      uid: f24eada1-543a-43da-b111-7e03ccd4c498
    resourceVersion: "14578"
    uid: e7ef37d0-1e5d-4bd6-9717-6dfe3385c1cc
  spec:
    sourcePod: network-check-source-6f8b768455-pcgrw
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:57:27Z"
      message: 'network-check-target-ip-10-0-142-108: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 855.05µs
      message: 'network-check-target-ip-10-0-142-108: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:57:27Z"
    - latency: 900.115µs
      message: 'network-check-target-ip-10-0-142-108: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:56:27Z"
    - latency: 1.013256ms
      message: 'network-check-target-ip-10-0-142-108: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:55:27Z"
    - latency: 794.624µs
      message: 'network-check-target-ip-10-0-142-108: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:54:27Z"
    - latency: 1.442523ms
      message: 'network-check-target-ip-10-0-142-108: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:53:27Z"
    - latency: 959.753µs
      message: 'network-check-target-ip-10-0-142-108: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:52:27Z"
    - latency: 1.736718ms
      message: 'network-check-target-ip-10-0-142-108: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:51:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:50:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-108-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-108.ec2.internal
      uid: f24eada1-543a-43da-b111-7e03ccd4c498
    resourceVersion: "16770"
    uid: 483b332f-a9c3-4c8e-aea6-8f8dd85da8df
  spec:
    sourcePod: network-check-source-6f8b768455-pcgrw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:56:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 957.87µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T04:02:27Z"
    - latency: 1.71765ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T04:02:27Z"
    - latency: 842.421µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T04:01:27Z"
    - latency: 1.728326ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T04:01:27Z"
    - latency: 859.781µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T04:00:27Z"
    - latency: 2.436664ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T04:00:27Z"
    - latency: 843.931µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:59:27Z"
    - latency: 2.272208ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:59:27Z"
    - latency: 785.236µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:58:27Z"
    - latency: 1.780719ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:58:27Z"
kind: List
metadata:
  resourceVersion: ""