apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T15:59:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-217-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-217.ec2.internal
      uid: b40e208c-9a4a-47a6-b420-ee60ee38050d
    resourceVersion: "11248"
    uid: 27cd6630-d04e-4a2d-ae34-e0d0a6f398ed
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qgkv
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T15:59:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-217-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-217.ec2.internal
      uid: b40e208c-9a4a-47a6-b420-ee60ee38050d
    resourceVersion: "14955"
    uid: c91f88fb-aa1a-462b-857b-304541bd2754
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qgkv
    targetEndpoint: ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T16:05:18Z"
      message: 'load-balancer-api-external: tcp connection to ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.896695ms
      message: 'load-balancer-api-external: tcp connection to ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T16:05:18Z"
    - latency: 9.047531ms
      message: 'load-balancer-api-external: resolved host name ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T16:05:18Z"
    - latency: 5.256924ms
      message: 'load-balancer-api-external: tcp connection to ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T16:04:18Z"
    - latency: 7.172002ms
      message: 'load-balancer-api-external: resolved host name ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T16:04:18Z"
    - latency: 5.598494ms
      message: 'load-balancer-api-external: tcp connection to ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T16:03:18Z"
    - latency: 9.675076ms
      message: 'load-balancer-api-external: resolved host name ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T16:03:18Z"
    - latency: 5.464532ms
      message: 'load-balancer-api-external: tcp connection to ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T16:02:18Z"
    - latency: 12.116337ms
      message: 'load-balancer-api-external: resolved host name ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T16:02:18Z"
    - latency: 4.646483ms
      message: 'load-balancer-api-external: tcp connection to ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T16:01:18Z"
    - latency: 7.525402ms
      message: 'load-balancer-api-external: resolved host name ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T16:01:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T15:59:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-217-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-217.ec2.internal
      uid: b40e208c-9a4a-47a6-b420-ee60ee38050d
    resourceVersion: "14956"
    uid: ba27b608-6fa1-487d-826b-1ce7f75665d4
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qgkv
    targetEndpoint: ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T16:05:18Z"
      message: 'load-balancer-api-internal: tcp connection to ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.575735ms
      message: 'load-balancer-api-internal: tcp connection to ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T16:05:18Z"
    - latency: 8.978237ms
      message: 'load-balancer-api-internal: resolved host name ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T16:05:18Z"
    - latency: 5.24918ms
      message: 'load-balancer-api-internal: tcp connection to ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T16:04:18Z"
    - latency: 7.143623ms
      message: 'load-balancer-api-internal: resolved host name ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T16:04:18Z"
    - latency: 4.565644ms
      message: 'load-balancer-api-internal: tcp connection to ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T16:03:18Z"
    - latency: 9.648549ms
      message: 'load-balancer-api-internal: resolved host name ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T16:03:18Z"
    - latency: 5.337359ms
      message: 'load-balancer-api-internal: tcp connection to ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T16:02:18Z"
    - latency: 12.052362ms
      message: 'load-balancer-api-internal: resolved host name ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T16:02:18Z"
    - latency: 4.68807ms
      message: 'load-balancer-api-internal: tcp connection to ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T16:01:18Z"
    - latency: 7.536208ms
      message: 'load-balancer-api-internal: resolved host name ab08bc8c3dc4c44af9a3ed8fb7a6d76c-a9e9745a1d0ff649.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T16:01:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T15:59:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-217-to-network-check-target-ip-10-0-132-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-217.ec2.internal
      uid: b40e208c-9a4a-47a6-b420-ee60ee38050d
    resourceVersion: "11253"
    uid: b8f01b6f-824f-4903-bd38-19050853730a
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qgkv
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T15:59:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-217-to-network-check-target-ip-10-0-134-149
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-217.ec2.internal
      uid: b40e208c-9a4a-47a6-b420-ee60ee38050d
    resourceVersion: "11255"
    uid: 09399875-2cd5-437c-8967-6de4189f1b51
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qgkv
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T15:59:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-217-to-network-check-target-ip-10-0-138-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-217.ec2.internal
      uid: b40e208c-9a4a-47a6-b420-ee60ee38050d
    resourceVersion: "11254"
    uid: 72836591-8799-49dc-9787-1342f5cb243e
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qgkv
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T15:59:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-217-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-217.ec2.internal
      uid: b40e208c-9a4a-47a6-b420-ee60ee38050d
    resourceVersion: "14954"
    uid: c85d0dbd-d5e4-4550-a782-1903fc010e22
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qgkv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T16:05:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 987.595µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T16:05:18Z"
    - latency: 2.017927ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T16:05:18Z"
    - latency: 1.381119ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T16:04:18Z"
    - latency: 1.839499ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T16:04:18Z"
    - latency: 815.793µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T16:03:18Z"
    - latency: 2.006442ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T16:03:18Z"
    - latency: 886.32µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T16:02:18Z"
    - latency: 2.300874ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T16:02:18Z"
    - latency: 805.474µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T16:01:18Z"
    - latency: 1.833612ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T16:01:18Z"
kind: List
metadata:
  resourceVersion: ""