apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:55:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-221-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-221.ec2.internal
      uid: 8fdf7e6b-c057-4207-b1ed-a14f16c8a035
    resourceVersion: "21326"
    uid: eb7dfc59-7c30-4d3b-843b-48ffc6e85d02
  spec:
    sourcePod: network-check-source-6f8b768455-csm4f
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:02:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 919.111µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:02:56Z"
    - latency: 1.19265ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:01:56Z"
    - latency: 1.084891ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:00:56Z"
    - latency: 1.049745ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:59:56Z"
    - latency: 951.591µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:58:56Z"
    - latency: 1.327544ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:57:56Z"
    - latency: 1.126691ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:56:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:55:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-221-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-221.ec2.internal
      uid: 8fdf7e6b-c057-4207-b1ed-a14f16c8a035
    resourceVersion: "20724"
    uid: 49153a69-f644-4d5b-8045-71ceaca2a6f8
  spec:
    sourcePod: network-check-source-6f8b768455-csm4f
    targetEndpoint: aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:01:56Z"
      message: 'load-balancer-api-external: tcp connection to aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.755741ms
      message: 'load-balancer-api-external: tcp connection to aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:01:56Z"
    - latency: 10.942532ms
      message: 'load-balancer-api-external: resolved host name aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:01:56Z"
    - latency: 3.612898ms
      message: 'load-balancer-api-external: tcp connection to aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:00:56Z"
    - latency: 8.087545ms
      message: 'load-balancer-api-external: resolved host name aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:00:56Z"
    - latency: 5.357497ms
      message: 'load-balancer-api-external: tcp connection to aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:59:56Z"
    - latency: 7.781516ms
      message: 'load-balancer-api-external: resolved host name aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:59:56Z"
    - latency: 5.277345ms
      message: 'load-balancer-api-external: tcp connection to aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:58:56Z"
    - latency: 8.144974ms
      message: 'load-balancer-api-external: resolved host name aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:58:56Z"
    - latency: 5.110392ms
      message: 'load-balancer-api-external: tcp connection to aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:57:56Z"
    - latency: 9.56258ms
      message: 'load-balancer-api-external: resolved host name aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:57:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:55:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-221-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-221.ec2.internal
      uid: 8fdf7e6b-c057-4207-b1ed-a14f16c8a035
    resourceVersion: "20725"
    uid: 6bec229a-3b0f-40b0-ab15-2c31f13911a8
  spec:
    sourcePod: network-check-source-6f8b768455-csm4f
    targetEndpoint: aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:01:56Z"
      message: 'load-balancer-api-internal: tcp connection to aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.72702ms
      message: 'load-balancer-api-internal: tcp connection to aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:01:56Z"
    - latency: 10.881455ms
      message: 'load-balancer-api-internal: resolved host name aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:01:56Z"
    - latency: 3.590735ms
      message: 'load-balancer-api-internal: tcp connection to aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:00:56Z"
    - latency: 8.008065ms
      message: 'load-balancer-api-internal: resolved host name aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:00:56Z"
    - latency: 5.402233ms
      message: 'load-balancer-api-internal: tcp connection to aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:59:56Z"
    - latency: 7.686713ms
      message: 'load-balancer-api-internal: resolved host name aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:59:56Z"
    - latency: 4.60168ms
      message: 'load-balancer-api-internal: tcp connection to aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:58:56Z"
    - latency: 8.193518ms
      message: 'load-balancer-api-internal: resolved host name aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:58:56Z"
    - latency: 5.004714ms
      message: 'load-balancer-api-internal: tcp connection to aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:57:56Z"
    - latency: 9.601777ms
      message: 'load-balancer-api-internal: resolved host name aecc8346cecf94c0699694bf19271e9a-38795e195a63544f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:57:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:55:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-221-to-network-check-target-ip-10-0-130-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-221.ec2.internal
      uid: 8fdf7e6b-c057-4207-b1ed-a14f16c8a035
    resourceVersion: "21325"
    uid: 969126b8-e7e6-4fd8-b3a7-019e077fe101
  spec:
    sourcePod: network-check-source-6f8b768455-csm4f
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:02:56Z"
      message: 'network-check-target-ip-10-0-130-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.346291ms
      message: 'network-check-target-ip-10-0-130-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:02:56Z"
    - latency: 2.218456ms
      message: 'network-check-target-ip-10-0-130-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:01:56Z"
    - latency: 2.096382ms
      message: 'network-check-target-ip-10-0-130-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:00:56Z"
    - latency: 1.939032ms
      message: 'network-check-target-ip-10-0-130-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:59:56Z"
    - latency: 2.207957ms
      message: 'network-check-target-ip-10-0-130-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:58:56Z"
    - latency: 2.799046ms
      message: 'network-check-target-ip-10-0-130-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:57:56Z"
    - latency: 2.317255ms
      message: 'network-check-target-ip-10-0-130-168: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:56:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:55:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-221-to-network-check-target-ip-10-0-136-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-221.ec2.internal
      uid: 8fdf7e6b-c057-4207-b1ed-a14f16c8a035
    resourceVersion: "21324"
    uid: 98353fcd-a65b-454a-bf34-a412705d8324
  spec:
    sourcePod: network-check-source-6f8b768455-csm4f
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:02:56Z"
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.280526ms
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:02:56Z"
    - latency: 1.647375ms
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:01:56Z"
    - latency: 1.795688ms
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:00:56Z"
    - latency: 2.062264ms
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:59:56Z"
    - latency: 2.013976ms
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:58:56Z"
    - latency: 2.226528ms
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:57:56Z"
    - latency: 1.98162ms
      message: 'network-check-target-ip-10-0-136-74: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:56:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:55:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-221-to-network-check-target-ip-10-0-139-221
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-221.ec2.internal
      uid: 8fdf7e6b-c057-4207-b1ed-a14f16c8a035
    resourceVersion: "21323"
    uid: 6933e619-b517-48e1-b8a4-9161b42e3a1c
  spec:
    sourcePod: network-check-source-6f8b768455-csm4f
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:02:56Z"
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.3148ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:02:56Z"
    - latency: 945.443µs
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:01:56Z"
    - latency: 885.63µs
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:00:56Z"
    - latency: 1.326804ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:59:56Z"
    - latency: 1.361146ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:58:56Z"
    - latency: 1.81557ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:57:56Z"
    - latency: 1.347174ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:56:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:55:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-221-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-221.ec2.internal
      uid: 8fdf7e6b-c057-4207-b1ed-a14f16c8a035
    resourceVersion: "20723"
    uid: 7ff784d0-1b69-43c4-8838-6d015b3ad7a4
  spec:
    sourcePod: network-check-source-6f8b768455-csm4f
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:01:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 904.628µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:01:56Z"
    - latency: 1.861205ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:01:56Z"
    - latency: 823.43µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:00:56Z"
    - latency: 1.689152ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:00:56Z"
    - latency: 762.679µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:59:56Z"
    - latency: 1.695839ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:59:56Z"
    - latency: 960.954µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:58:56Z"
    - latency: 2.204971ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:58:56Z"
    - latency: 1.193851ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:57:56Z"
    - latency: 1.741798ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:57:56Z"
kind: List
metadata:
  resourceVersion: ""