apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:20:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-125-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-125.ec2.internal
      uid: 877cf6cb-6655-47e8-aeb5-b104b3be86cc
    resourceVersion: "19791"
    uid: c458859c-9598-4dcb-a7a7-728aa292fea4
  spec:
    sourcePod: network-check-source-7b678d77c7-jtdhp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:27:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.124319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:27:12Z"
    - latency: 771.398µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:26:12Z"
    - latency: 1.113884ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:25:12Z"
    - latency: 740.062µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:24:12Z"
    - latency: 1.133702ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:23:12Z"
    - latency: 967.969µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:22:12Z"
    - latency: 1.627868ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:21:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:20:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-125-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-125.ec2.internal
      uid: 877cf6cb-6655-47e8-aeb5-b104b3be86cc
    resourceVersion: "22502"
    uid: 64b63bca-d900-455a-a7c4-5b8181ed700b
  spec:
    sourcePod: network-check-source-7b678d77c7-jtdhp
    targetEndpoint: a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:26:12Z"
      message: 'load-balancer-api-external: tcp connection to a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.677647ms
      message: 'load-balancer-api-external: tcp connection to a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:32:12Z"
    - latency: 6.086023ms
      message: 'load-balancer-api-external: resolved host name a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:32:12Z"
    - latency: 3.778764ms
      message: 'load-balancer-api-external: tcp connection to a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:31:12Z"
    - latency: 6.932089ms
      message: 'load-balancer-api-external: resolved host name a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:31:12Z"
    - latency: 4.321624ms
      message: 'load-balancer-api-external: tcp connection to a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:30:12Z"
    - latency: 6.262397ms
      message: 'load-balancer-api-external: resolved host name a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:30:12Z"
    - latency: 4.486859ms
      message: 'load-balancer-api-external: tcp connection to a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:29:12Z"
    - latency: 8.208422ms
      message: 'load-balancer-api-external: resolved host name a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:29:12Z"
    - latency: 4.47952ms
      message: 'load-balancer-api-external: tcp connection to a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:28:12Z"
    - latency: 6.42054ms
      message: 'load-balancer-api-external: resolved host name a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:28:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:20:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-125-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-125.ec2.internal
      uid: 877cf6cb-6655-47e8-aeb5-b104b3be86cc
    resourceVersion: "22503"
    uid: b49e76fa-b6f9-4338-8a12-5c9bae4967bd
  spec:
    sourcePod: network-check-source-7b678d77c7-jtdhp
    targetEndpoint: a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:26:12Z"
      message: 'load-balancer-api-internal: tcp connection to a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.653139ms
      message: 'load-balancer-api-internal: tcp connection to a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:32:12Z"
    - latency: 6.122447ms
      message: 'load-balancer-api-internal: resolved host name a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:32:12Z"
    - latency: 3.198624ms
      message: 'load-balancer-api-internal: tcp connection to a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:31:12Z"
    - latency: 6.883377ms
      message: 'load-balancer-api-internal: resolved host name a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:31:12Z"
    - latency: 4.322678ms
      message: 'load-balancer-api-internal: tcp connection to a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:30:12Z"
    - latency: 6.337181ms
      message: 'load-balancer-api-internal: resolved host name a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:30:12Z"
    - latency: 4.426317ms
      message: 'load-balancer-api-internal: tcp connection to a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:29:12Z"
    - latency: 8.286777ms
      message: 'load-balancer-api-internal: resolved host name a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:29:12Z"
    - latency: 4.448962ms
      message: 'load-balancer-api-internal: tcp connection to a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:28:12Z"
    - latency: 6.507485ms
      message: 'load-balancer-api-internal: resolved host name a863be9a5599c46b986854d99ac6e3f5-93f6d7ac5a1f2be5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:28:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:20:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-125-to-network-check-target-ip-10-0-130-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-125.ec2.internal
      uid: 877cf6cb-6655-47e8-aeb5-b104b3be86cc
    resourceVersion: "19788"
    uid: 6e00e363-ed85-41af-814c-f224dcaa0044
  spec:
    sourcePod: network-check-source-7b678d77c7-jtdhp
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:27:12Z"
      message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.234342ms
      message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:27:12Z"
    - latency: 2.577184ms
      message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:26:12Z"
    - latency: 1.978175ms
      message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:25:12Z"
    - latency: 1.891504ms
      message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:24:12Z"
    - latency: 2.033381ms
      message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:23:12Z"
    - latency: 2.144217ms
      message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:22:12Z"
    - latency: 2.23403ms
      message: 'network-check-target-ip-10-0-130-205: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:21:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:20:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-125-to-network-check-target-ip-10-0-135-125
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-125.ec2.internal
      uid: 877cf6cb-6655-47e8-aeb5-b104b3be86cc
    resourceVersion: "19790"
    uid: 676ec7d6-e0bb-49b0-9a7a-59d93091df75
  spec:
    sourcePod: network-check-source-7b678d77c7-jtdhp
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:27:12Z"
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 831.75µs
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:27:12Z"
    - latency: 731.328µs
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:26:12Z"
    - latency: 720.185µs
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:25:12Z"
    - latency: 805.697µs
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:24:12Z"
    - latency: 897.999µs
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:23:12Z"
    - latency: 679.291µs
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:22:12Z"
    - latency: 1.214048ms
      message: 'network-check-target-ip-10-0-135-125: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:21:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:20:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-125-to-network-check-target-ip-10-0-138-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-125.ec2.internal
      uid: 877cf6cb-6655-47e8-aeb5-b104b3be86cc
    resourceVersion: "19789"
    uid: ffa873b2-d201-458a-a394-8b67bf65f40c
  spec:
    sourcePod: network-check-source-7b678d77c7-jtdhp
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:27:12Z"
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.862406ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:27:12Z"
    - latency: 1.866464ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:26:12Z"
    - latency: 1.915412ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:25:12Z"
    - latency: 1.594446ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:24:12Z"
    - latency: 2.00924ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:23:12Z"
    - latency: 1.697899ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:22:12Z"
    - latency: 2.164711ms
      message: 'network-check-target-ip-10-0-138-22: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:21:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T18:20:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-125-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-125.ec2.internal
      uid: 877cf6cb-6655-47e8-aeb5-b104b3be86cc
    resourceVersion: "22501"
    uid: aaba4f78-26c9-4491-b3c8-f9c4aff9447d
  spec:
    sourcePod: network-check-source-7b678d77c7-jtdhp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T18:26:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 664.248µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:32:12Z"
    - latency: 1.825975ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:32:12Z"
    - latency: 885.48µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:31:12Z"
    - latency: 2.212322ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:31:12Z"
    - latency: 792.513µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:30:12Z"
    - latency: 1.575755ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:30:12Z"
    - latency: 1.016945ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:29:12Z"
    - latency: 1.50915ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:29:12Z"
    - latency: 679.718µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T18:28:12Z"
    - latency: 1.750052ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T18:28:12Z"
kind: List
metadata:
  resourceVersion: ""