apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:54:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: d4fa76d8-66f6-416d-bec1-2f93f5061e71
    resourceVersion: "23414"
    uid: 0f01f6ff-da72-416e-8bca-c3cf3cc75bd4
  spec:
    sourcePod: network-check-source-685456655f-nwv9w
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:01:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.108288ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:01:05Z"
    - latency: 1.096429ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:05Z"
    - latency: 936.056µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:59:05Z"
    - latency: 933.192µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:58:05Z"
    - latency: 1.092098ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:57:05Z"
    - latency: 939.275µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:56:05Z"
    - latency: 1.077057ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:55:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:54:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: d4fa76d8-66f6-416d-bec1-2f93f5061e71
    resourceVersion: "21903"
    uid: ed49849b-6e5b-498c-a971-9b6b974a6bef
  spec:
    sourcePod: network-check-source-685456655f-nwv9w
    targetEndpoint: aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:00:05Z"
      message: 'load-balancer-api-external: tcp connection to aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.319019ms
      message: 'load-balancer-api-external: tcp connection to aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:05Z"
    - latency: 7.313321ms
      message: 'load-balancer-api-external: resolved host name aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:00:05Z"
    - latency: 3.657289ms
      message: 'load-balancer-api-external: tcp connection to aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:59:05Z"
    - latency: 6.281063ms
      message: 'load-balancer-api-external: resolved host name aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:59:05Z"
    - latency: 5.623392ms
      message: 'load-balancer-api-external: tcp connection to aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:58:05Z"
    - latency: 6.798646ms
      message: 'load-balancer-api-external: resolved host name aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:58:05Z"
    - latency: 5.053361ms
      message: 'load-balancer-api-external: tcp connection to aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:57:05Z"
    - latency: 8.384828ms
      message: 'load-balancer-api-external: resolved host name aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:57:05Z"
    - latency: 4.38053ms
      message: 'load-balancer-api-external: tcp connection to aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:56:05Z"
    - latency: 9.446455ms
      message: 'load-balancer-api-external: resolved host name aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:56:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:54:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: d4fa76d8-66f6-416d-bec1-2f93f5061e71
    resourceVersion: "21904"
    uid: e5f5f8c9-1f01-40c5-9b1b-1a0391b9db3d
  spec:
    sourcePod: network-check-source-685456655f-nwv9w
    targetEndpoint: aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:00:05Z"
      message: 'load-balancer-api-internal: tcp connection to aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.327972ms
      message: 'load-balancer-api-internal: tcp connection to aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:05Z"
    - latency: 7.222588ms
      message: 'load-balancer-api-internal: resolved host name aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:00:05Z"
    - latency: 3.646534ms
      message: 'load-balancer-api-internal: tcp connection to aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:59:05Z"
    - latency: 6.349475ms
      message: 'load-balancer-api-internal: resolved host name aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:59:05Z"
    - latency: 5.650232ms
      message: 'load-balancer-api-internal: tcp connection to aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:58:05Z"
    - latency: 6.900633ms
      message: 'load-balancer-api-internal: resolved host name aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:58:05Z"
    - latency: 4.431878ms
      message: 'load-balancer-api-internal: tcp connection to aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:57:05Z"
    - latency: 8.675386ms
      message: 'load-balancer-api-internal: resolved host name aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:57:05Z"
    - latency: 4.328804ms
      message: 'load-balancer-api-internal: tcp connection to aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:56:05Z"
    - latency: 9.503118ms
      message: 'load-balancer-api-internal: resolved host name aa62187d3c8794efe8ee0d4308d5cb6a-ea5b5631a7f88125.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:56:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:54:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-network-check-target-ip-10-0-132-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: d4fa76d8-66f6-416d-bec1-2f93f5061e71
    resourceVersion: "23416"
    uid: ddc5f280-4708-4a7d-a21a-0ef7366c345f
  spec:
    sourcePod: network-check-source-685456655f-nwv9w
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:01:05Z"
      message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.453669ms
      message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:01:05Z"
    - latency: 2.185026ms
      message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:05Z"
    - latency: 1.909908ms
      message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:59:05Z"
    - latency: 2.135714ms
      message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:58:05Z"
    - latency: 2.134399ms
      message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:57:05Z"
    - latency: 2.39834ms
      message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:56:05Z"
    - latency: 2.451173ms
      message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:55:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:54:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-network-check-target-ip-10-0-140-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: d4fa76d8-66f6-416d-bec1-2f93f5061e71
    resourceVersion: "23412"
    uid: b9b1b1d0-ec65-4d10-b319-cf255de75354
  spec:
    sourcePod: network-check-source-685456655f-nwv9w
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:01:05Z"
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 847.294µs
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:01:05Z"
    - latency: 781.766µs
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:05Z"
    - latency: 852.463µs
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:59:05Z"
    - latency: 1.340814ms
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:58:05Z"
    - latency: 1.043196ms
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:57:05Z"
    - latency: 798.949µs
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:56:05Z"
    - latency: 1.151017ms
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:55:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:54:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-network-check-target-ip-10-0-143-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: d4fa76d8-66f6-416d-bec1-2f93f5061e71
    resourceVersion: "23413"
    uid: 4ab7fb4d-6b91-41e0-8ca5-e40dfbfef4d8
  spec:
    sourcePod: network-check-source-685456655f-nwv9w
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:01:05Z"
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.982461ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:01:05Z"
    - latency: 1.955379ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:05Z"
    - latency: 1.866557ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:59:05Z"
    - latency: 1.931793ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:58:05Z"
    - latency: 2.147313ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:57:05Z"
    - latency: 2.127103ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:56:05Z"
    - latency: 2.073796ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:55:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:54:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: d4fa76d8-66f6-416d-bec1-2f93f5061e71
    resourceVersion: "21902"
    uid: 17372453-2d48-4803-b65f-692ceec3b547
  spec:
    sourcePod: network-check-source-685456655f-nwv9w
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:00:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 945.827µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:00:05Z"
    - latency: 2.107913ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:00:05Z"
    - latency: 979.707µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:59:05Z"
    - latency: 1.80177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:59:05Z"
    - latency: 1.111165ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:58:05Z"
    - latency: 1.791036ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:58:05Z"
    - latency: 1.194609ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:57:05Z"
    - latency: 1.851363ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:57:05Z"
    - latency: 903.179µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:56:05Z"
    - latency: 1.655491ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:56:05Z"
kind: List
metadata:
  resourceVersion: ""