apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:26:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-223-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-223.ec2.internal
      uid: 2ddcf0a6-d439-4d25-a4c4-7f89fe881c9d
    resourceVersion: "15402"
    uid: 6b3f3ea1-9d92-4292-a6b3-8e33554a214e
  spec:
    sourcePod: network-check-source-7d88cb55d8-kc5pr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T14:34:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.107457ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:34:01Z"
    - latency: 1.27151ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:33:01Z"
    - latency: 1.442994ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:32:01Z"
    - latency: 1.10096ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:31:01Z"
    - latency: 1.553464ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:30:01Z"
    - latency: 1.270516ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:29:01Z"
    - latency: 1.002657ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:28:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:26:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-223-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-223.ec2.internal
      uid: 2ddcf0a6-d439-4d25-a4c4-7f89fe881c9d
    resourceVersion: "15076"
    uid: 02268d31-c18e-4e68-a602-15b9d637c999
  spec:
    sourcePod: network-check-source-7d88cb55d8-kc5pr
    targetEndpoint: a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T14:33:01Z"
      message: 'load-balancer-api-external: tcp connection to a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.089452ms
      message: 'load-balancer-api-external: tcp connection to a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:33:01Z"
    - latency: 8.374732ms
      message: 'load-balancer-api-external: resolved host name a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:33:01Z"
    - latency: 5.461233ms
      message: 'load-balancer-api-external: tcp connection to a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:32:01Z"
    - latency: 8.913054ms
      message: 'load-balancer-api-external: resolved host name a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:32:01Z"
    - latency: 5.316408ms
      message: 'load-balancer-api-external: tcp connection to a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:31:01Z"
    - latency: 7.87276ms
      message: 'load-balancer-api-external: resolved host name a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:31:01Z"
    - latency: 4.401402ms
      message: 'load-balancer-api-external: tcp connection to a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:30:01Z"
    - latency: 8.34196ms
      message: 'load-balancer-api-external: resolved host name a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:30:01Z"
    - latency: 4.606733ms
      message: 'load-balancer-api-external: tcp connection to a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:29:01Z"
    - latency: 8.333316ms
      message: 'load-balancer-api-external: resolved host name a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:29:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:26:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-223-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-223.ec2.internal
      uid: 2ddcf0a6-d439-4d25-a4c4-7f89fe881c9d
    resourceVersion: "15075"
    uid: c3e5fb5b-46e8-4adc-ae06-8c8971c4b5ad
  spec:
    sourcePod: network-check-source-7d88cb55d8-kc5pr
    targetEndpoint: a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T14:33:01Z"
      message: 'load-balancer-api-internal: tcp connection to a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.038785ms
      message: 'load-balancer-api-internal: tcp connection to a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:33:01Z"
    - latency: 8.318294ms
      message: 'load-balancer-api-internal: resolved host name a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:33:01Z"
    - latency: 4.553696ms
      message: 'load-balancer-api-internal: tcp connection to a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:32:01Z"
    - latency: 8.889926ms
      message: 'load-balancer-api-internal: resolved host name a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:32:01Z"
    - latency: 5.387878ms
      message: 'load-balancer-api-internal: tcp connection to a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:31:01Z"
    - latency: 7.824363ms
      message: 'load-balancer-api-internal: resolved host name a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:31:01Z"
    - latency: 6.002285ms
      message: 'load-balancer-api-internal: tcp connection to a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:30:01Z"
    - latency: 8.316576ms
      message: 'load-balancer-api-internal: resolved host name a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:30:01Z"
    - latency: 6.871353ms
      message: 'load-balancer-api-internal: tcp connection to a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:29:01Z"
    - latency: 8.318109ms
      message: 'load-balancer-api-internal: resolved host name a438a1d4b4fd042b78ea4f49f6eb2b60-8a1c1d8fdf3ef911.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:29:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:27:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-223-to-network-check-target-ip-10-0-128-100
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-223.ec2.internal
      uid: 2ddcf0a6-d439-4d25-a4c4-7f89fe881c9d
    resourceVersion: "15547"
    uid: 5006dbce-7922-4dd5-ab75-ff0579df53cf
  spec:
    sourcePod: network-check-source-7d88cb55d8-kc5pr
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T14:34:27Z"
      message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.353426ms
      message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:34:27Z"
    - latency: 2.350229ms
      message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:33:27Z"
    - latency: 2.175176ms
      message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:32:27Z"
    - latency: 2.473799ms
      message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:31:27Z"
    - latency: 2.503994ms
      message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:30:27Z"
    - latency: 2.11899ms
      message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:29:27Z"
    - latency: 2.530316ms
      message: 'network-check-target-ip-10-0-128-100: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:28:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:27:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-223-to-network-check-target-ip-10-0-128-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-223.ec2.internal
      uid: 2ddcf0a6-d439-4d25-a4c4-7f89fe881c9d
    resourceVersion: "15523"
    uid: 22289a49-5713-44af-bda8-215764250590
  spec:
    sourcePod: network-check-source-7d88cb55d8-kc5pr
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T14:34:22Z"
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.052071ms
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:34:22Z"
    - latency: 2.182124ms
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:33:22Z"
    - latency: 2.238791ms
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:32:22Z"
    - latency: 2.059469ms
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:31:22Z"
    - latency: 2.28335ms
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:30:22Z"
    - latency: 2.290931ms
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:29:22Z"
    - latency: 2.130655ms
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:28:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:26:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-223-to-network-check-target-ip-10-0-131-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-223.ec2.internal
      uid: 2ddcf0a6-d439-4d25-a4c4-7f89fe881c9d
    resourceVersion: "15401"
    uid: 262f54a2-cead-422b-a5c6-33f05a47714f
  spec:
    sourcePod: network-check-source-7d88cb55d8-kc5pr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T14:34:01Z"
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 978.836µs
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:34:01Z"
    - latency: 1.27762ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:33:01Z"
    - latency: 1.789631ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:32:01Z"
    - latency: 855.7µs
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:31:01Z"
    - latency: 1.139762ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:30:01Z"
    - latency: 1.518451ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:29:01Z"
    - latency: 1.496731ms
      message: 'network-check-target-ip-10-0-131-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:28:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T14:26:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-223-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-223.ec2.internal
      uid: 2ddcf0a6-d439-4d25-a4c4-7f89fe881c9d
    resourceVersion: "15074"
    uid: 4197503d-76ab-460b-83c3-77af5fbbff78
  spec:
    sourcePod: network-check-source-7d88cb55d8-kc5pr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T14:33:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 918.329µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:33:01Z"
    - latency: 1.884829ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:33:01Z"
    - latency: 2.189922ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:32:01Z"
    - latency: 1.782492ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:32:01Z"
    - latency: 2.22201ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:31:01Z"
    - latency: 1.891152ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:31:01Z"
    - latency: 2.195245ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:30:01Z"
    - latency: 1.813717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:30:01Z"
    - latency: 2.209149ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:29:01Z"
    - latency: 1.980086ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:29:01Z"
kind: List
metadata:
  resourceVersion: ""