apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:31:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-40-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-40.ec2.internal
      uid: 157c9073-6231-464a-b3b3-62517e1bb408
    resourceVersion: "15593"
    uid: bf3a39cd-bc4a-47e4-85b5-63ae6d1327ea
  spec:
    sourcePod: network-check-source-7d88cb55d8-lrhjd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:38:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 922.23µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:38:08Z"
    - latency: 1.397506ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:37:08Z"
    - latency: 1.191079ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:36:08Z"
    - latency: 1.552985ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:35:08Z"
    - latency: 1.177982ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:34:08Z"
    - latency: 1.020788ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:33:08Z"
    - latency: 1.171324ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:32:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:31:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-40-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-40.ec2.internal
      uid: 157c9073-6231-464a-b3b3-62517e1bb408
    resourceVersion: "15171"
    uid: 1412f54f-238b-4c0a-9ca4-c90f6e298a49
  spec:
    sourcePod: network-check-source-7d88cb55d8-lrhjd
    targetEndpoint: aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:37:08Z"
      message: 'load-balancer-api-external: tcp connection to aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.356329ms
      message: 'load-balancer-api-external: tcp connection to aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:37:08Z"
    - latency: 5.998727ms
      message: 'load-balancer-api-external: resolved host name aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:37:08Z"
    - latency: 4.573565ms
      message: 'load-balancer-api-external: tcp connection to aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:36:08Z"
    - latency: 7.854461ms
      message: 'load-balancer-api-external: resolved host name aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:36:08Z"
    - latency: 5.688366ms
      message: 'load-balancer-api-external: tcp connection to aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:35:08Z"
    - latency: 7.093077ms
      message: 'load-balancer-api-external: resolved host name aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:35:08Z"
    - latency: 5.740774ms
      message: 'load-balancer-api-external: tcp connection to aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:34:08Z"
    - latency: 6.622356ms
      message: 'load-balancer-api-external: resolved host name aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:34:08Z"
    - latency: 4.965204ms
      message: 'load-balancer-api-external: tcp connection to aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:33:08Z"
    - latency: 6.157225ms
      message: 'load-balancer-api-external: resolved host name aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:33:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:31:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-40-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-40.ec2.internal
      uid: 157c9073-6231-464a-b3b3-62517e1bb408
    resourceVersion: "15172"
    uid: c5e9260d-afa5-4c9d-9768-d5458325fbc5
  spec:
    sourcePod: network-check-source-7d88cb55d8-lrhjd
    targetEndpoint: aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:37:08Z"
      message: 'load-balancer-api-internal: tcp connection to aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.284926ms
      message: 'load-balancer-api-internal: tcp connection to aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:37:08Z"
    - latency: 6.024461ms
      message: 'load-balancer-api-internal: resolved host name aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:37:08Z"
    - latency: 4.67204ms
      message: 'load-balancer-api-internal: tcp connection to aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:36:08Z"
    - latency: 8.06072ms
      message: 'load-balancer-api-internal: resolved host name aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:36:08Z"
    - latency: 5.745143ms
      message: 'load-balancer-api-internal: tcp connection to aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:35:08Z"
    - latency: 7.125508ms
      message: 'load-balancer-api-internal: resolved host name aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:35:08Z"
    - latency: 5.728638ms
      message: 'load-balancer-api-internal: tcp connection to aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:34:08Z"
    - latency: 6.652509ms
      message: 'load-balancer-api-internal: resolved host name aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:34:08Z"
    - latency: 4.977872ms
      message: 'load-balancer-api-internal: tcp connection to aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:33:08Z"
    - latency: 6.244104ms
      message: 'load-balancer-api-internal: resolved host name aac47b20600fa4108b4a90b9e5204393-ed0144ab164ecd7c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:33:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:31:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-40-to-network-check-target-ip-10-0-128-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-40.ec2.internal
      uid: 157c9073-6231-464a-b3b3-62517e1bb408
    resourceVersion: "15592"
    uid: d4e8682d-17e7-4f2c-970d-700f8a76224f
  spec:
    sourcePod: network-check-source-7d88cb55d8-lrhjd
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:38:08Z"
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.098505ms
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:38:08Z"
    - latency: 2.395459ms
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:37:08Z"
    - latency: 2.197913ms
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:36:08Z"
    - latency: 1.886534ms
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:35:08Z"
    - latency: 2.187377ms
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:34:08Z"
    - latency: 2.014197ms
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:33:08Z"
    - latency: 2.336367ms
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:32:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:31:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-40-to-network-check-target-ip-10-0-141-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-40.ec2.internal
      uid: 157c9073-6231-464a-b3b3-62517e1bb408
    resourceVersion: "15591"
    uid: 7d103f3b-9c7d-4e48-a5ad-742e8fc565ad
  spec:
    sourcePod: network-check-source-7d88cb55d8-lrhjd
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:38:08Z"
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.257572ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:38:08Z"
    - latency: 2.592934ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:37:08Z"
    - latency: 2.307322ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:36:08Z"
    - latency: 2.34575ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:35:08Z"
    - latency: 2.194844ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:34:08Z"
    - latency: 2.41247ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:33:08Z"
    - latency: 2.615777ms
      message: 'network-check-target-ip-10-0-141-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:32:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:31:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-40-to-network-check-target-ip-10-0-143-40
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-40.ec2.internal
      uid: 157c9073-6231-464a-b3b3-62517e1bb408
    resourceVersion: "15590"
    uid: 6151fd9d-4919-4e17-97e3-173c0aecee11
  spec:
    sourcePod: network-check-source-7d88cb55d8-lrhjd
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:38:08Z"
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 972.693µs
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:38:08Z"
    - latency: 1.577066ms
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:37:08Z"
    - latency: 935.982µs
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:36:08Z"
    - latency: 831.585µs
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:35:08Z"
    - latency: 861.29µs
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:34:08Z"
    - latency: 1.289978ms
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:33:08Z"
    - latency: 1.694293ms
      message: 'network-check-target-ip-10-0-143-40: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:32:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:31:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-40-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-40.ec2.internal
      uid: 157c9073-6231-464a-b3b3-62517e1bb408
    resourceVersion: "15170"
    uid: dd062523-614f-4cb2-9055-9ab00d610f81
  spec:
    sourcePod: network-check-source-7d88cb55d8-lrhjd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:37:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 850.832µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:37:08Z"
    - latency: 1.559297ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:37:08Z"
    - latency: 848.737µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:36:08Z"
    - latency: 2.352147ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:36:08Z"
    - latency: 1.080508ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:35:08Z"
    - latency: 1.916099ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:35:08Z"
    - latency: 873.701µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:34:08Z"
    - latency: 1.877422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:34:08Z"
    - latency: 1.219451ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T16:33:08Z"
    - latency: 1.749989ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T16:33:08Z"
kind: List
metadata:
  resourceVersion: ""