apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:20:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-136-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-136.ec2.internal
      uid: 21b989f4-90c4-44d6-b48d-41ad649789d4
    resourceVersion: "14536"
    uid: 5fe4a2c2-c708-4ea8-a169-7aaa36d25603
  spec:
    sourcePod: network-check-source-7d88cb55d8-r6285
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:27:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 900.448µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:27:28Z"
    - latency: 1.16158ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:26:28Z"
    - latency: 1.01929ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:25:28Z"
    - latency: 941.192µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:24:28Z"
    - latency: 948.289µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:23:28Z"
    - latency: 924.896µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:22:28Z"
    - latency: 994.156µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:21:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:20:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-136-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-136.ec2.internal
      uid: 21b989f4-90c4-44d6-b48d-41ad649789d4
    resourceVersion: "14126"
    uid: b3423af3-7fdf-43b8-bf85-ac1e6c364253
  spec:
    sourcePod: network-check-source-7d88cb55d8-r6285
    targetEndpoint: a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:26:28Z"
      message: 'load-balancer-api-external: tcp connection to a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.302519ms
      message: 'load-balancer-api-external: tcp connection to a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:26:28Z"
    - latency: 11.155312ms
      message: 'load-balancer-api-external: resolved host name a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:26:28Z"
    - latency: 4.874671ms
      message: 'load-balancer-api-external: tcp connection to a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:25:28Z"
    - latency: 6.815306ms
      message: 'load-balancer-api-external: resolved host name a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:25:28Z"
    - latency: 5.177323ms
      message: 'load-balancer-api-external: tcp connection to a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:24:28Z"
    - latency: 10.463206ms
      message: 'load-balancer-api-external: resolved host name a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:24:28Z"
    - latency: 4.95371ms
      message: 'load-balancer-api-external: tcp connection to a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:23:28Z"
    - latency: 7.092762ms
      message: 'load-balancer-api-external: resolved host name a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:23:28Z"
    - latency: 5.616933ms
      message: 'load-balancer-api-external: tcp connection to a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:22:28Z"
    - latency: 9.818807ms
      message: 'load-balancer-api-external: resolved host name a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:22:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:20:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-136-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-136.ec2.internal
      uid: 21b989f4-90c4-44d6-b48d-41ad649789d4
    resourceVersion: "14125"
    uid: 4a271dc5-a7c4-4276-9b50-2f851f959b31
  spec:
    sourcePod: network-check-source-7d88cb55d8-r6285
    targetEndpoint: a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:26:28Z"
      message: 'load-balancer-api-internal: tcp connection to a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.282622ms
      message: 'load-balancer-api-internal: tcp connection to a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:26:28Z"
    - latency: 11.047766ms
      message: 'load-balancer-api-internal: resolved host name a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:26:28Z"
    - latency: 4.876646ms
      message: 'load-balancer-api-internal: tcp connection to a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:25:28Z"
    - latency: 6.863853ms
      message: 'load-balancer-api-internal: resolved host name a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:25:28Z"
    - latency: 5.036381ms
      message: 'load-balancer-api-internal: tcp connection to a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:24:28Z"
    - latency: 10.524826ms
      message: 'load-balancer-api-internal: resolved host name a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:24:28Z"
    - latency: 5.117609ms
      message: 'load-balancer-api-internal: tcp connection to a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:23:28Z"
    - latency: 6.98733ms
      message: 'load-balancer-api-internal: resolved host name a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:23:28Z"
    - latency: 5.35127ms
      message: 'load-balancer-api-internal: tcp connection to a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:22:28Z"
    - latency: 9.684403ms
      message: 'load-balancer-api-internal: resolved host name a512bdf1aee3749549b640d79a924f76-1e87ca1db8dd1cab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:22:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:20:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-136-to-network-check-target-ip-10-0-128-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-136.ec2.internal
      uid: 21b989f4-90c4-44d6-b48d-41ad649789d4
    resourceVersion: "14535"
    uid: 2541f975-aeb4-467c-ac8d-a44c633a8260
  spec:
    sourcePod: network-check-source-7d88cb55d8-r6285
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:27:28Z"
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.324498ms
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:27:28Z"
    - latency: 2.20605ms
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:26:28Z"
    - latency: 2.063727ms
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:25:28Z"
    - latency: 2.081668ms
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:24:28Z"
    - latency: 2.234584ms
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:23:28Z"
    - latency: 2.192712ms
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:22:28Z"
    - latency: 2.29959ms
      message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:21:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:20:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-136-to-network-check-target-ip-10-0-134-136
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-136.ec2.internal
      uid: 21b989f4-90c4-44d6-b48d-41ad649789d4
    resourceVersion: "14533"
    uid: e914839e-8413-42eb-992c-5dac583923bf
  spec:
    sourcePod: network-check-source-7d88cb55d8-r6285
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:27:28Z"
      message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.574767ms
      message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:27:28Z"
    - latency: 1.18432ms
      message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:26:28Z"
    - latency: 1.285123ms
      message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:25:28Z"
    - latency: 841.938µs
      message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:24:28Z"
    - latency: 892.065µs
      message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:23:28Z"
    - latency: 880.564µs
      message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:22:28Z"
    - latency: 1.520656ms
      message: 'network-check-target-ip-10-0-134-136: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:21:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:20:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-136-to-network-check-target-ip-10-0-141-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-136.ec2.internal
      uid: 21b989f4-90c4-44d6-b48d-41ad649789d4
    resourceVersion: "14534"
    uid: 8cca52b9-d846-4c38-95ae-032808ebb2c9
  spec:
    sourcePod: network-check-source-7d88cb55d8-r6285
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:27:28Z"
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.26552ms
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:27:28Z"
    - latency: 5.979213ms
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:26:28Z"
    - latency: 2.30731ms
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:25:28Z"
    - latency: 2.094751ms
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:24:28Z"
    - latency: 2.085305ms
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:23:28Z"
    - latency: 2.102548ms
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:22:28Z"
    - latency: 2.199167ms
      message: 'network-check-target-ip-10-0-141-7: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:21:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T14:20:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-136-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-136.ec2.internal
      uid: 21b989f4-90c4-44d6-b48d-41ad649789d4
    resourceVersion: "14124"
    uid: 670b0496-7fa8-4c1a-90de-72ea1cd16b75
  spec:
    sourcePod: network-check-source-7d88cb55d8-r6285
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T14:26:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.088919ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:26:28Z"
    - latency: 1.587255ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:26:28Z"
    - latency: 885.17µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:25:28Z"
    - latency: 1.735068ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:25:28Z"
    - latency: 880.484µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:24:28Z"
    - latency: 1.686926ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:24:28Z"
    - latency: 758.676µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:23:28Z"
    - latency: 1.522944ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:23:28Z"
    - latency: 1.095103ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T14:22:28Z"
    - latency: 1.770968ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T14:22:28Z"
kind: List
metadata:
  resourceVersion: ""