apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-25-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-25.ec2.internal
      uid: d1060e80-361c-4d9f-9c8b-a4057c2f1fe6
    resourceVersion: "14045"
    uid: b48116a7-3758-47c3-b35e-43b28ae950a3
  spec:
    sourcePod: network-check-source-7d88cb55d8-v2xkg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:01:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 688.129µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:01:29Z"
    - latency: 975.145µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:00:29Z"
    - latency: 950.514µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:59:29Z"
    - latency: 875.348µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:58:29Z"
    - latency: 999.198µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:57:29Z"
    - latency: 981.83µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:56:29Z"
    - latency: 1.033745ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:55:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-25-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-25.ec2.internal
      uid: d1060e80-361c-4d9f-9c8b-a4057c2f1fe6
    resourceVersion: "15777"
    uid: 61b9b545-5f9e-4a07-9390-864bf952050e
  spec:
    sourcePod: network-check-source-7d88cb55d8-v2xkg
    targetEndpoint: aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:00:29Z"
      message: 'load-balancer-api-external: tcp connection to aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.542133ms
      message: 'load-balancer-api-external: tcp connection to aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:06:29Z"
    - latency: 8.156488ms
      message: 'load-balancer-api-external: resolved host name aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:06:29Z"
    - latency: 4.84485ms
      message: 'load-balancer-api-external: tcp connection to aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:05:29Z"
    - latency: 7.871446ms
      message: 'load-balancer-api-external: resolved host name aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:05:29Z"
    - latency: 4.971571ms
      message: 'load-balancer-api-external: tcp connection to aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:04:29Z"
    - latency: 8.319545ms
      message: 'load-balancer-api-external: resolved host name aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:04:29Z"
    - latency: 5.097547ms
      message: 'load-balancer-api-external: tcp connection to aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:03:29Z"
    - latency: 8.453851ms
      message: 'load-balancer-api-external: resolved host name aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:03:29Z"
    - latency: 4.75863ms
      message: 'load-balancer-api-external: tcp connection to aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:02:29Z"
    - latency: 8.020059ms
      message: 'load-balancer-api-external: resolved host name aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:02:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-25-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-25.ec2.internal
      uid: d1060e80-361c-4d9f-9c8b-a4057c2f1fe6
    resourceVersion: "15776"
    uid: e84b6c9c-7085-462d-b575-2ab04be7744c
  spec:
    sourcePod: network-check-source-7d88cb55d8-v2xkg
    targetEndpoint: aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:00:29Z"
      message: 'load-balancer-api-internal: tcp connection to aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.420062ms
      message: 'load-balancer-api-internal: tcp connection to aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:06:29Z"
    - latency: 8.074423ms
      message: 'load-balancer-api-internal: resolved host name aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:06:29Z"
    - latency: 4.941947ms
      message: 'load-balancer-api-internal: tcp connection to aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:05:29Z"
    - latency: 7.906479ms
      message: 'load-balancer-api-internal: resolved host name aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:05:29Z"
    - latency: 4.957677ms
      message: 'load-balancer-api-internal: tcp connection to aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:04:29Z"
    - latency: 8.40321ms
      message: 'load-balancer-api-internal: resolved host name aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:04:29Z"
    - latency: 5.068938ms
      message: 'load-balancer-api-internal: tcp connection to aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:03:29Z"
    - latency: 8.368795ms
      message: 'load-balancer-api-internal: resolved host name aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:03:29Z"
    - latency: 4.747431ms
      message: 'load-balancer-api-internal: tcp connection to aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:02:29Z"
    - latency: 7.9574ms
      message: 'load-balancer-api-internal: resolved host name aaa79f3386a1d41e389f88eaa445e899-8454a1ff24bc0403.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:02:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-25-to-network-check-target-ip-10-0-131-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-25.ec2.internal
      uid: d1060e80-361c-4d9f-9c8b-a4057c2f1fe6
    resourceVersion: "14042"
    uid: 5d149590-0bcf-4c18-a8e6-75eb197521d5
  spec:
    sourcePod: network-check-source-7d88cb55d8-v2xkg
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:01:29Z"
      message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.92µs
      message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:01:29Z"
    - latency: 839.601µs
      message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:00:29Z"
    - latency: 718.486µs
      message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:59:29Z"
    - latency: 1.307843ms
      message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:58:29Z"
    - latency: 1.374843ms
      message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:57:29Z"
    - latency: 1.18322ms
      message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:56:29Z"
    - latency: 1.074617ms
      message: 'network-check-target-ip-10-0-131-25: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:55:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-25-to-network-check-target-ip-10-0-141-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-25.ec2.internal
      uid: d1060e80-361c-4d9f-9c8b-a4057c2f1fe6
    resourceVersion: "14044"
    uid: 03397089-1b8e-4289-b6db-07b6b99db382
  spec:
    sourcePod: network-check-source-7d88cb55d8-v2xkg
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:01:29Z"
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.426316ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:01:29Z"
    - latency: 1.884968ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:00:29Z"
    - latency: 2.216164ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:59:29Z"
    - latency: 2.142764ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:58:29Z"
    - latency: 2.221295ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:57:29Z"
    - latency: 2.188999ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:56:29Z"
    - latency: 2.013487ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:55:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-25-to-network-check-target-ip-10-0-141-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-25.ec2.internal
      uid: d1060e80-361c-4d9f-9c8b-a4057c2f1fe6
    resourceVersion: "14043"
    uid: e55464ef-747f-4e1a-8cd0-203b6cedb05c
  spec:
    sourcePod: network-check-source-7d88cb55d8-v2xkg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:01:29Z"
      message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.95457ms
      message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:01:29Z"
    - latency: 1.756814ms
      message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:00:29Z"
    - latency: 1.810109ms
      message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:59:29Z"
    - latency: 1.973344ms
      message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:58:29Z"
    - latency: 1.963482ms
      message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:57:29Z"
    - latency: 1.783756ms
      message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:56:29Z"
    - latency: 2.013759ms
      message: 'network-check-target-ip-10-0-141-161: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T16:55:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-25-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-25.ec2.internal
      uid: d1060e80-361c-4d9f-9c8b-a4057c2f1fe6
    resourceVersion: "15775"
    uid: 53a7e985-8cf3-4471-97d8-b43931c7c064
  spec:
    sourcePod: network-check-source-7d88cb55d8-v2xkg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:00:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 799.155µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:06:29Z"
    - latency: 1.559291ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:06:29Z"
    - latency: 835.629µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:05:29Z"
    - latency: 1.594761ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:05:29Z"
    - latency: 1.248212ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:04:29Z"
    - latency: 1.618889ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:04:29Z"
    - latency: 728.422µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:03:29Z"
    - latency: 1.74853ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:03:29Z"
    - latency: 1.113083ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:02:29Z"
    - latency: 1.557716ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:02:29Z"
kind: List
metadata:
  resourceVersion: ""