apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T21:25:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-234-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-234.ec2.internal
      uid: c75b77f7-2174-4726-acec-b8d01b6e6518
    resourceVersion: "18825"
    uid: 891c0261-a113-4dbf-8903-514898f5afee
  spec:
    sourcePod: network-check-source-dbd9cf844-n6d52
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T21:32:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.107542ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:32:26Z"
    - latency: 908.785µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:31:26Z"
    - latency: 1.83669ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:30:26Z"
    - latency: 1.010218ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:29:26Z"
    - latency: 1.053682ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:28:26Z"
    - latency: 921.008µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:27:26Z"
    - latency: 1.023501ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:26:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T21:25:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-234-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-234.ec2.internal
      uid: c75b77f7-2174-4726-acec-b8d01b6e6518
    resourceVersion: "27049"
    uid: 5bd015cc-0592-4dbd-af0b-26fc9746e184
  spec:
    sourcePod: network-check-source-dbd9cf844-n6d52
    targetEndpoint: a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T21:31:26Z"
      message: 'load-balancer-api-external: tcp connection to a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.328848ms
      message: 'load-balancer-api-external: tcp connection to a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:37:26Z"
    - latency: 8.441998ms
      message: 'load-balancer-api-external: resolved host name a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:37:26Z"
    - latency: 4.976337ms
      message: 'load-balancer-api-external: tcp connection to a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:36:26Z"
    - latency: 9.161984ms
      message: 'load-balancer-api-external: resolved host name a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:36:26Z"
    - latency: 4.449924ms
      message: 'load-balancer-api-external: tcp connection to a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:35:26Z"
    - latency: 9.681192ms
      message: 'load-balancer-api-external: resolved host name a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:35:26Z"
    - latency: 5.089056ms
      message: 'load-balancer-api-external: tcp connection to a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:34:26Z"
    - latency: 9.137266ms
      message: 'load-balancer-api-external: resolved host name a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:34:26Z"
    - latency: 5.039735ms
      message: 'load-balancer-api-external: tcp connection to a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:33:26Z"
    - latency: 10.28091ms
      message: 'load-balancer-api-external: resolved host name a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:33:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T21:25:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-234-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-234.ec2.internal
      uid: c75b77f7-2174-4726-acec-b8d01b6e6518
    resourceVersion: "27050"
    uid: 507a1915-0184-4457-bb06-1f6ec4dc6eee
  spec:
    sourcePod: network-check-source-dbd9cf844-n6d52
    targetEndpoint: a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T21:31:26Z"
      message: 'load-balancer-api-internal: tcp connection to a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.327732ms
      message: 'load-balancer-api-internal: tcp connection to a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:37:26Z"
    - latency: 8.407212ms
      message: 'load-balancer-api-internal: resolved host name a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:37:26Z"
    - latency: 4.961411ms
      message: 'load-balancer-api-internal: tcp connection to a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:36:26Z"
    - latency: 8.383791ms
      message: 'load-balancer-api-internal: resolved host name a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:36:26Z"
    - latency: 4.420855ms
      message: 'load-balancer-api-internal: tcp connection to a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:35:26Z"
    - latency: 9.665161ms
      message: 'load-balancer-api-internal: resolved host name a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:35:26Z"
    - latency: 5.054666ms
      message: 'load-balancer-api-internal: tcp connection to a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:34:26Z"
    - latency: 9.156266ms
      message: 'load-balancer-api-internal: resolved host name a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:34:26Z"
    - latency: 3.423838ms
      message: 'load-balancer-api-internal: tcp connection to a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:33:26Z"
    - latency: 10.264494ms
      message: 'load-balancer-api-internal: resolved host name a362b8502b287490b8eeb13c522ce093-39aee1e3c6a6d96c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:33:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T21:25:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-234-to-network-check-target-ip-10-0-135-237
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-234.ec2.internal
      uid: c75b77f7-2174-4726-acec-b8d01b6e6518
    resourceVersion: "18824"
    uid: 59be233c-4953-4ade-9490-a7c17cff7f24
  spec:
    sourcePod: network-check-source-dbd9cf844-n6d52
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T21:32:26Z"
      message: 'network-check-target-ip-10-0-135-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.344356ms
      message: 'network-check-target-ip-10-0-135-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:32:26Z"
    - latency: 1.908621ms
      message: 'network-check-target-ip-10-0-135-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:31:26Z"
    - latency: 3.213655ms
      message: 'network-check-target-ip-10-0-135-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:30:26Z"
    - latency: 1.984324ms
      message: 'network-check-target-ip-10-0-135-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:29:26Z"
    - latency: 2.233426ms
      message: 'network-check-target-ip-10-0-135-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:28:26Z"
    - latency: 1.948795ms
      message: 'network-check-target-ip-10-0-135-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:27:26Z"
    - latency: 2.087693ms
      message: 'network-check-target-ip-10-0-135-237: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:26:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T21:25:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-234-to-network-check-target-ip-10-0-136-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-234.ec2.internal
      uid: c75b77f7-2174-4726-acec-b8d01b6e6518
    resourceVersion: "18823"
    uid: db98505c-7372-4d0a-8a83-481796158f87
  spec:
    sourcePod: network-check-source-dbd9cf844-n6d52
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T21:32:26Z"
      message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.998596ms
      message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:32:26Z"
    - latency: 1.752034ms
      message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:31:26Z"
    - latency: 4.554017ms
      message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:30:26Z"
    - latency: 1.894332ms
      message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:29:26Z"
    - latency: 1.976232ms
      message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:28:26Z"
    - latency: 1.69743ms
      message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:27:26Z"
    - latency: 1.845498ms
      message: 'network-check-target-ip-10-0-136-105: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:26:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T21:25:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-234-to-network-check-target-ip-10-0-136-234
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-234.ec2.internal
      uid: c75b77f7-2174-4726-acec-b8d01b6e6518
    resourceVersion: "18822"
    uid: 71a0be19-a724-4d4a-8ec0-0dd2bd4f829c
  spec:
    sourcePod: network-check-source-dbd9cf844-n6d52
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T21:32:26Z"
      message: 'network-check-target-ip-10-0-136-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 796.099µs
      message: 'network-check-target-ip-10-0-136-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:32:26Z"
    - latency: 786.198µs
      message: 'network-check-target-ip-10-0-136-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:31:26Z"
    - latency: 2.321952ms
      message: 'network-check-target-ip-10-0-136-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:30:26Z"
    - latency: 872.555µs
      message: 'network-check-target-ip-10-0-136-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:29:26Z"
    - latency: 1.441505ms
      message: 'network-check-target-ip-10-0-136-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:28:26Z"
    - latency: 826.072µs
      message: 'network-check-target-ip-10-0-136-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:27:26Z"
    - latency: 1.171816ms
      message: 'network-check-target-ip-10-0-136-234: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:26:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T21:25:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-234-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-234.ec2.internal
      uid: c75b77f7-2174-4726-acec-b8d01b6e6518
    resourceVersion: "27048"
    uid: 83e206c1-bc01-4dbb-83e1-0dab1f854370
  spec:
    sourcePod: network-check-source-dbd9cf844-n6d52
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T21:31:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 960.615µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:37:26Z"
    - latency: 1.838309ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:37:26Z"
    - latency: 935.105µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:36:26Z"
    - latency: 2.946315ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:36:26Z"
    - latency: 1.111401ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:35:26Z"
    - latency: 2.495634ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:35:26Z"
    - latency: 907.523µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:34:26Z"
    - latency: 2.460666ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:34:26Z"
    - latency: 1.106041ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T21:33:26Z"
    - latency: 1.764031ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T21:33:26Z"
kind: List
metadata:
  resourceVersion: ""