apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:02:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-246-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-246.ec2.internal
      uid: 39795d94-8dc4-4ac2-a462-e5dd81dd9a28
    resourceVersion: "14181"
    uid: ed2cad2c-b3d7-4091-b9a5-f9f03cec44b5
  spec:
    sourcePod: network-check-source-685456655f-jl68n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:09:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.054863ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:09:24Z"
    - latency: 1.18348ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:08:24Z"
    - latency: 912.388µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:07:24Z"
    - latency: 1.027218ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:06:24Z"
    - latency: 1.072945ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:05:24Z"
    - latency: 1.034727ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:04:24Z"
    - latency: 1.421161ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:03:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:02:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-246-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-246.ec2.internal
      uid: 39795d94-8dc4-4ac2-a462-e5dd81dd9a28
    resourceVersion: "13844"
    uid: 7c35cec0-5df4-4e3b-abac-5727ca6a2ffc
  spec:
    sourcePod: network-check-source-685456655f-jl68n
    targetEndpoint: aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:08:24Z"
      message: 'load-balancer-api-external: tcp connection to aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.256186ms
      message: 'load-balancer-api-external: tcp connection to aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:08:24Z"
    - latency: 8.001397ms
      message: 'load-balancer-api-external: resolved host name aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:08:24Z"
    - latency: 5.455517ms
      message: 'load-balancer-api-external: tcp connection to aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:07:24Z"
    - latency: 8.094674ms
      message: 'load-balancer-api-external: resolved host name aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:07:24Z"
    - latency: 4.721968ms
      message: 'load-balancer-api-external: tcp connection to aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:06:24Z"
    - latency: 8.297669ms
      message: 'load-balancer-api-external: resolved host name aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:06:24Z"
    - latency: 5.899699ms
      message: 'load-balancer-api-external: tcp connection to aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:05:24Z"
    - latency: 8.290681ms
      message: 'load-balancer-api-external: resolved host name aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:05:24Z"
    - latency: 3.926369ms
      message: 'load-balancer-api-external: tcp connection to aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:04:24Z"
    - latency: 7.290127ms
      message: 'load-balancer-api-external: resolved host name aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:04:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:02:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-246-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-246.ec2.internal
      uid: 39795d94-8dc4-4ac2-a462-e5dd81dd9a28
    resourceVersion: "13843"
    uid: e3a51a9b-73ab-424f-803e-8521c32a80a7
  spec:
    sourcePod: network-check-source-685456655f-jl68n
    targetEndpoint: aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:08:24Z"
      message: 'load-balancer-api-internal: tcp connection to aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.246309ms
      message: 'load-balancer-api-internal: tcp connection to aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:08:24Z"
    - latency: 7.930948ms
      message: 'load-balancer-api-internal: resolved host name aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:08:24Z"
    - latency: 5.219541ms
      message: 'load-balancer-api-internal: tcp connection to aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:07:24Z"
    - latency: 8.146266ms
      message: 'load-balancer-api-internal: resolved host name aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:07:24Z"
    - latency: 5.734712ms
      message: 'load-balancer-api-internal: tcp connection to aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:06:24Z"
    - latency: 8.161038ms
      message: 'load-balancer-api-internal: resolved host name aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:06:24Z"
    - latency: 6.287809ms
      message: 'load-balancer-api-internal: tcp connection to aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:05:24Z"
    - latency: 8.369635ms
      message: 'load-balancer-api-internal: resolved host name aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:05:24Z"
    - latency: 4.016271ms
      message: 'load-balancer-api-internal: tcp connection to aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:04:24Z"
    - latency: 7.239707ms
      message: 'load-balancer-api-internal: resolved host name aeddb57e786884bb09b61ea191891fad-0c1f6151f5d48dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:04:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:02:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-246-to-network-check-target-ip-10-0-131-169
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-246.ec2.internal
      uid: 39795d94-8dc4-4ac2-a462-e5dd81dd9a28
    resourceVersion: "14179"
    uid: c9fff580-c135-4010-8b0f-ad9c5764c58b
  spec:
    sourcePod: network-check-source-685456655f-jl68n
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:09:24Z"
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.346261ms
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:09:24Z"
    - latency: 1.642982ms
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:08:24Z"
    - latency: 1.909441ms
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:07:24Z"
    - latency: 1.937207ms
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:06:24Z"
    - latency: 2.488213ms
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:05:24Z"
    - latency: 1.736236ms
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:04:24Z"
    - latency: 1.994414ms
      message: 'network-check-target-ip-10-0-131-169: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:03:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:02:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-246-to-network-check-target-ip-10-0-138-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-246.ec2.internal
      uid: 39795d94-8dc4-4ac2-a462-e5dd81dd9a28
    resourceVersion: "14180"
    uid: c50b4d11-bec8-451c-bde9-512dde62e833
  spec:
    sourcePod: network-check-source-685456655f-jl68n
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:09:24Z"
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.219107ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:09:24Z"
    - latency: 2.081503ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:08:24Z"
    - latency: 2.160075ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:07:24Z"
    - latency: 1.950825ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:06:24Z"
    - latency: 2.652557ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:05:24Z"
    - latency: 1.922673ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:04:24Z"
    - latency: 2.27661ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:03:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:02:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-246-to-network-check-target-ip-10-0-140-246
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-246.ec2.internal
      uid: 39795d94-8dc4-4ac2-a462-e5dd81dd9a28
    resourceVersion: "14178"
    uid: a31f799d-8c37-47a0-add6-2800a0bc38cd
  spec:
    sourcePod: network-check-source-685456655f-jl68n
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:09:24Z"
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 831.074µs
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:09:24Z"
    - latency: 924.464µs
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:08:24Z"
    - latency: 881.825µs
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:07:24Z"
    - latency: 1.528919ms
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:06:24Z"
    - latency: 967.101µs
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:05:24Z"
    - latency: 845.23µs
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:04:24Z"
    - latency: 1.833396ms
      message: 'network-check-target-ip-10-0-140-246: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:03:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:02:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-246-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-246.ec2.internal
      uid: 39795d94-8dc4-4ac2-a462-e5dd81dd9a28
    resourceVersion: "13842"
    uid: 6fb246bd-1076-4278-a97d-f2b0b27cebc8
  spec:
    sourcePod: network-check-source-685456655f-jl68n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:08:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 896.917µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:08:24Z"
    - latency: 1.785632ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:08:24Z"
    - latency: 1.016986ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:07:24Z"
    - latency: 1.880717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:07:24Z"
    - latency: 873.64µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:06:24Z"
    - latency: 1.762422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:06:24Z"
    - latency: 1.148252ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:05:24Z"
    - latency: 1.619926ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:05:24Z"
    - latency: 1.144678ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:04:24Z"
    - latency: 1.858913ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:04:24Z"
kind: List
metadata:
  resourceVersion: ""