apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:21:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-85-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-85.ec2.internal
      uid: 0605189f-ba4b-4ce0-8af2-ec1013daacf4
    resourceVersion: "15903"
    uid: 05d89ac2-4e25-4989-9f5c-822a77f45fff
  spec:
    sourcePod: network-check-source-dbd9cf844-z57cl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:28:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.424329ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:28:52Z"
    - latency: 1.081338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:27:52Z"
    - latency: 1.072065ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:26:52Z"
    - latency: 1.23652ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:25:52Z"
    - latency: 1.521988ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:24:52Z"
    - latency: 1.027566ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:23:52Z"
    - latency: 1.066989ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:22:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:21:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-85-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-85.ec2.internal
      uid: 0605189f-ba4b-4ce0-8af2-ec1013daacf4
    resourceVersion: "15571"
    uid: 18c52293-7537-4a04-a71b-3e028820f483
  spec:
    sourcePod: network-check-source-dbd9cf844-z57cl
    targetEndpoint: a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:27:52Z"
      message: 'load-balancer-api-external: tcp connection to a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.683591ms
      message: 'load-balancer-api-external: tcp connection to a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:27:52Z"
    - latency: 8.896187ms
      message: 'load-balancer-api-external: resolved host name a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:27:52Z"
    - latency: 4.899627ms
      message: 'load-balancer-api-external: tcp connection to a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:26:52Z"
    - latency: 8.749943ms
      message: 'load-balancer-api-external: resolved host name a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:26:52Z"
    - latency: 4.423977ms
      message: 'load-balancer-api-external: tcp connection to a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:25:52Z"
    - latency: 8.119509ms
      message: 'load-balancer-api-external: resolved host name a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:25:52Z"
    - latency: 5.358336ms
      message: 'load-balancer-api-external: tcp connection to a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:24:52Z"
    - latency: 9.111783ms
      message: 'load-balancer-api-external: resolved host name a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:24:52Z"
    - latency: 4.413281ms
      message: 'load-balancer-api-external: tcp connection to a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:23:52Z"
    - latency: 8.006521ms
      message: 'load-balancer-api-external: resolved host name a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:23:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:21:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-85-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-85.ec2.internal
      uid: 0605189f-ba4b-4ce0-8af2-ec1013daacf4
    resourceVersion: "15572"
    uid: 3b49eb9f-40b7-4fdb-a25e-47603e2204eb
  spec:
    sourcePod: network-check-source-dbd9cf844-z57cl
    targetEndpoint: a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:27:52Z"
      message: 'load-balancer-api-internal: tcp connection to a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.635162ms
      message: 'load-balancer-api-internal: tcp connection to a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:27:52Z"
    - latency: 8.976655ms
      message: 'load-balancer-api-internal: resolved host name a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:27:52Z"
    - latency: 5.155456ms
      message: 'load-balancer-api-internal: tcp connection to a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:26:52Z"
    - latency: 8.726672ms
      message: 'load-balancer-api-internal: resolved host name a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:26:52Z"
    - latency: 4.785178ms
      message: 'load-balancer-api-internal: tcp connection to a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:25:52Z"
    - latency: 8.175204ms
      message: 'load-balancer-api-internal: resolved host name a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:25:52Z"
    - latency: 3.876863ms
      message: 'load-balancer-api-internal: tcp connection to a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:24:52Z"
    - latency: 9.196433ms
      message: 'load-balancer-api-internal: resolved host name a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:24:52Z"
    - latency: 4.430357ms
      message: 'load-balancer-api-internal: tcp connection to a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:23:52Z"
    - latency: 7.950355ms
      message: 'load-balancer-api-internal: resolved host name a9165ea70a69040cc8b6cc01001bef83-31e506e15286a93d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:23:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:21:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-85-to-network-check-target-ip-10-0-130-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-85.ec2.internal
      uid: 0605189f-ba4b-4ce0-8af2-ec1013daacf4
    resourceVersion: "15900"
    uid: 3e904e19-04d5-45bd-b0fc-a8e4309e3974
  spec:
    sourcePod: network-check-source-dbd9cf844-z57cl
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:28:52Z"
      message: 'network-check-target-ip-10-0-130-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.99737ms
      message: 'network-check-target-ip-10-0-130-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:28:52Z"
    - latency: 1.985523ms
      message: 'network-check-target-ip-10-0-130-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:27:52Z"
    - latency: 2.256158ms
      message: 'network-check-target-ip-10-0-130-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:26:52Z"
    - latency: 2.409043ms
      message: 'network-check-target-ip-10-0-130-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:25:52Z"
    - latency: 2.089208ms
      message: 'network-check-target-ip-10-0-130-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:24:52Z"
    - latency: 2.210004ms
      message: 'network-check-target-ip-10-0-130-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:23:52Z"
    - latency: 2.491515ms
      message: 'network-check-target-ip-10-0-130-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:22:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:21:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-85-to-network-check-target-ip-10-0-140-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-85.ec2.internal
      uid: 0605189f-ba4b-4ce0-8af2-ec1013daacf4
    resourceVersion: "15902"
    uid: ad610252-ead7-429d-bb7c-ae158d7b3739
  spec:
    sourcePod: network-check-source-dbd9cf844-z57cl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:28:52Z"
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.27296ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:28:52Z"
    - latency: 2.410755ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:27:52Z"
    - latency: 2.277267ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:26:52Z"
    - latency: 1.958023ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:25:52Z"
    - latency: 2.188958ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:24:52Z"
    - latency: 2.515783ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:23:52Z"
    - latency: 2.446464ms
      message: 'network-check-target-ip-10-0-140-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:22:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:21:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-85-to-network-check-target-ip-10-0-141-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-85.ec2.internal
      uid: 0605189f-ba4b-4ce0-8af2-ec1013daacf4
    resourceVersion: "15901"
    uid: 3dc6a486-f4c6-4b32-8922-26a29a9bc57e
  spec:
    sourcePod: network-check-source-dbd9cf844-z57cl
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:28:52Z"
      message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.263307ms
      message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:28:52Z"
    - latency: 940.921µs
      message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:27:52Z"
    - latency: 1.324996ms
      message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:26:52Z"
    - latency: 926.783µs
      message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:25:52Z"
    - latency: 949.146µs
      message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:24:52Z"
    - latency: 1.414783ms
      message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:23:52Z"
    - latency: 1.556952ms
      message: 'network-check-target-ip-10-0-141-85: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:22:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:21:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-85-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-85.ec2.internal
      uid: 0605189f-ba4b-4ce0-8af2-ec1013daacf4
    resourceVersion: "15570"
    uid: 9cb36f9c-1be7-4b5a-919e-54f7bca1e80a
  spec:
    sourcePod: network-check-source-dbd9cf844-z57cl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:27:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 988.428µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:27:52Z"
    - latency: 1.884509ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:27:52Z"
    - latency: 947.47µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:26:52Z"
    - latency: 2.072662ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:26:52Z"
    - latency: 1.148168ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:25:52Z"
    - latency: 1.846941ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:25:52Z"
    - latency: 863.533µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:24:52Z"
    - latency: 1.804157ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:24:52Z"
    - latency: 1.013327ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T15:23:52Z"
    - latency: 1.652821ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T15:23:52Z"
kind: List
metadata:
  resourceVersion: ""