apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:10:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-140-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-140.ec2.internal
      uid: a6ce1a7b-4e11-418e-a4cb-d9b472a86a18
    resourceVersion: "22757"
    uid: 805f9361-914f-4691-870d-60a532b12fae
  spec:
    sourcePod: network-check-source-685456655f-hxpnq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:17:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 897.292µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:17:27Z"
    - latency: 977.921µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:16:27Z"
    - latency: 1.040656ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:15:27Z"
    - latency: 1.058999ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:14:27Z"
    - latency: 1.057583ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:13:27Z"
    - latency: 1.333698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:12:27Z"
    - latency: 2.063519ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:11:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:10:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-140-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-140.ec2.internal
      uid: a6ce1a7b-4e11-418e-a4cb-d9b472a86a18
    resourceVersion: "21535"
    uid: 11ed803a-a5b9-4d15-8268-95c7905130df
  spec:
    sourcePod: network-check-source-685456655f-hxpnq
    targetEndpoint: a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:16:27Z"
      message: 'load-balancer-api-external: tcp connection to a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.218007ms
      message: 'load-balancer-api-external: tcp connection to a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:16:27Z"
    - latency: 7.871772ms
      message: 'load-balancer-api-external: resolved host name a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:16:27Z"
    - latency: 4.302548ms
      message: 'load-balancer-api-external: tcp connection to a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:15:27Z"
    - latency: 8.317057ms
      message: 'load-balancer-api-external: resolved host name a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:15:27Z"
    - latency: 5.019786ms
      message: 'load-balancer-api-external: tcp connection to a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:14:27Z"
    - latency: 7.544615ms
      message: 'load-balancer-api-external: resolved host name a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:14:27Z"
    - latency: 4.8927ms
      message: 'load-balancer-api-external: tcp connection to a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:13:27Z"
    - latency: 14.465185ms
      message: 'load-balancer-api-external: resolved host name a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:13:27Z"
    - latency: 10.843241ms
      message: 'load-balancer-api-external: tcp connection to a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:12:27Z"
    - latency: 8.242722ms
      message: 'load-balancer-api-external: resolved host name a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:12:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:10:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-140-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-140.ec2.internal
      uid: a6ce1a7b-4e11-418e-a4cb-d9b472a86a18
    resourceVersion: "21534"
    uid: fbf81229-052b-4939-999f-9d6d0ec484d4
  spec:
    sourcePod: network-check-source-685456655f-hxpnq
    targetEndpoint: a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:16:27Z"
      message: 'load-balancer-api-internal: tcp connection to a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.224469ms
      message: 'load-balancer-api-internal: tcp connection to a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:16:27Z"
    - latency: 7.809734ms
      message: 'load-balancer-api-internal: resolved host name a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:16:27Z"
    - latency: 5.989136ms
      message: 'load-balancer-api-internal: tcp connection to a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:15:27Z"
    - latency: 8.165448ms
      message: 'load-balancer-api-internal: resolved host name a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:15:27Z"
    - latency: 4.961372ms
      message: 'load-balancer-api-internal: tcp connection to a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:14:27Z"
    - latency: 7.43898ms
      message: 'load-balancer-api-internal: resolved host name a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:14:27Z"
    - latency: 5.254229ms
      message: 'load-balancer-api-internal: tcp connection to a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:13:27Z"
    - latency: 14.360884ms
      message: 'load-balancer-api-internal: resolved host name a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:13:27Z"
    - latency: 3.863283ms
      message: 'load-balancer-api-internal: tcp connection to a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:12:27Z"
    - latency: 8.156256ms
      message: 'load-balancer-api-internal: resolved host name a6aecd8ded907481892cad0509655c0e-ceaee76b4a848aae.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:12:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:10:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-140-to-network-check-target-ip-10-0-128-140
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-140.ec2.internal
      uid: a6ce1a7b-4e11-418e-a4cb-d9b472a86a18
    resourceVersion: "22754"
    uid: 19e15b7a-8aa1-4483-8eba-df130a0c9e8b
  spec:
    sourcePod: network-check-source-685456655f-hxpnq
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:17:27Z"
      message: 'network-check-target-ip-10-0-128-140: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.470933ms
      message: 'network-check-target-ip-10-0-128-140: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:17:27Z"
    - latency: 918.049µs
      message: 'network-check-target-ip-10-0-128-140: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:16:27Z"
    - latency: 1.061957ms
      message: 'network-check-target-ip-10-0-128-140: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:15:27Z"
    - latency: 1.382109ms
      message: 'network-check-target-ip-10-0-128-140: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:14:27Z"
    - latency: 910.026µs
      message: 'network-check-target-ip-10-0-128-140: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:13:27Z"
    - latency: 1.271126ms
      message: 'network-check-target-ip-10-0-128-140: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:12:27Z"
    - latency: 2.031732ms
      message: 'network-check-target-ip-10-0-128-140: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:11:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:10:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-140-to-network-check-target-ip-10-0-130-212
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-140.ec2.internal
      uid: a6ce1a7b-4e11-418e-a4cb-d9b472a86a18
    resourceVersion: "22756"
    uid: 33c95911-c0cd-4118-b5f9-2014f8b10f9b
  spec:
    sourcePod: network-check-source-685456655f-hxpnq
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:17:27Z"
      message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.312544ms
      message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:17:27Z"
    - latency: 2.6787ms
      message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:16:27Z"
    - latency: 2.436221ms
      message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:15:27Z"
    - latency: 2.650188ms
      message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:14:27Z"
    - latency: 2.379196ms
      message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:13:27Z"
    - latency: 2.237679ms
      message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:12:27Z"
    - latency: 2.829164ms
      message: 'network-check-target-ip-10-0-130-212: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:11:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:10:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-140-to-network-check-target-ip-10-0-141-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-140.ec2.internal
      uid: a6ce1a7b-4e11-418e-a4cb-d9b472a86a18
    resourceVersion: "22755"
    uid: 68cfc814-4685-40f2-8160-a67c071738d1
  spec:
    sourcePod: network-check-source-685456655f-hxpnq
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:17:27Z"
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.502284ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:17:27Z"
    - latency: 2.335186ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:16:27Z"
    - latency: 2.313666ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:15:27Z"
    - latency: 2.47913ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:14:27Z"
    - latency: 2.288718ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:13:27Z"
    - latency: 2.133576ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:12:27Z"
    - latency: 2.739696ms
      message: 'network-check-target-ip-10-0-141-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:11:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:10:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-140-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-140.ec2.internal
      uid: a6ce1a7b-4e11-418e-a4cb-d9b472a86a18
    resourceVersion: "21533"
    uid: d0cdfc80-edba-44a3-8296-bda2ce703ebc
  spec:
    sourcePod: network-check-source-685456655f-hxpnq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:16:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 977.699µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:16:27Z"
    - latency: 2.145659ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:16:27Z"
    - latency: 1.122969ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:15:27Z"
    - latency: 3.012615ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:15:27Z"
    - latency: 1.071394ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:14:27Z"
    - latency: 1.7671ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:14:27Z"
    - latency: 1.225794ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:13:27Z"
    - latency: 1.758549ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:13:27Z"
    - latency: 889.803µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T12:12:27Z"
    - latency: 2.137057ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T12:12:27Z"
kind: List
metadata:
  resourceVersion: ""