apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T09:04:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-103-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-103.ec2.internal
      uid: 52a947d8-e4f4-451c-bca9-e5951929443c
    resourceVersion: "10931"
    uid: c4d8a87a-67b2-47bc-a0e2-0084f54a957a
  spec:
    sourcePod: network-check-source-7d88cb55d8-8hdcj
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T09:04:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-103-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-103.ec2.internal
      uid: 52a947d8-e4f4-451c-bca9-e5951929443c
    resourceVersion: "14542"
    uid: 6e31f477-dcea-475a-acf6-8233fbc6af2b
  spec:
    sourcePod: network-check-source-7d88cb55d8-8hdcj
    targetEndpoint: a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T09:10:48Z"
      message: 'load-balancer-api-external: tcp connection to a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.113406ms
      message: 'load-balancer-api-external: tcp connection to a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T09:10:48Z"
    - latency: 8.511378ms
      message: 'load-balancer-api-external: resolved host name a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T09:10:48Z"
    - latency: 4.815553ms
      message: 'load-balancer-api-external: tcp connection to a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T09:09:48Z"
    - latency: 8.800049ms
      message: 'load-balancer-api-external: resolved host name a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T09:09:48Z"
    - latency: 3.778456ms
      message: 'load-balancer-api-external: tcp connection to a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T09:08:48Z"
    - latency: 8.517764ms
      message: 'load-balancer-api-external: resolved host name a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T09:08:48Z"
    - latency: 4.874225ms
      message: 'load-balancer-api-external: tcp connection to a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T09:07:48Z"
    - latency: 11.940854ms
      message: 'load-balancer-api-external: resolved host name a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T09:07:48Z"
    - latency: 5.170283ms
      message: 'load-balancer-api-external: tcp connection to a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T09:06:48Z"
    - latency: 8.025125ms
      message: 'load-balancer-api-external: resolved host name a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T09:06:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T09:04:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-103-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-103.ec2.internal
      uid: 52a947d8-e4f4-451c-bca9-e5951929443c
    resourceVersion: "14543"
    uid: 07c7a923-c438-452c-ab86-89a837432243
  spec:
    sourcePod: network-check-source-7d88cb55d8-8hdcj
    targetEndpoint: a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T09:10:48Z"
      message: 'load-balancer-api-internal: tcp connection to a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.115493ms
      message: 'load-balancer-api-internal: tcp connection to a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T09:10:48Z"
    - latency: 8.474918ms
      message: 'load-balancer-api-internal: resolved host name a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T09:10:48Z"
    - latency: 4.847736ms
      message: 'load-balancer-api-internal: tcp connection to a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T09:09:48Z"
    - latency: 8.738089ms
      message: 'load-balancer-api-internal: resolved host name a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T09:09:48Z"
    - latency: 5.090086ms
      message: 'load-balancer-api-internal: tcp connection to a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T09:08:48Z"
    - latency: 8.477676ms
      message: 'load-balancer-api-internal: resolved host name a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T09:08:48Z"
    - latency: 4.140254ms
      message: 'load-balancer-api-internal: tcp connection to a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T09:07:48Z"
    - latency: 11.958249ms
      message: 'load-balancer-api-internal: resolved host name a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T09:07:48Z"
    - latency: 5.202101ms
      message: 'load-balancer-api-internal: tcp connection to a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T09:06:48Z"
    - latency: 8.014777ms
      message: 'load-balancer-api-internal: resolved host name a3e769518936941ab8d9f69d1975eb70-7bca3169c29276c9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T09:06:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T09:04:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-103-to-network-check-target-ip-10-0-136-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-103.ec2.internal
      uid: 52a947d8-e4f4-451c-bca9-e5951929443c
    resourceVersion: "10928"
    uid: 121d92cd-a23a-4bae-b950-71f47d00f0c5
  spec:
    sourcePod: network-check-source-7d88cb55d8-8hdcj
    targetEndpoint: 10.133.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T09:04:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-103-to-network-check-target-ip-10-0-136-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-103.ec2.internal
      uid: 52a947d8-e4f4-451c-bca9-e5951929443c
    resourceVersion: "10930"
    uid: edd34d28-10c3-4a3c-baec-7debe6f1108b
  spec:
    sourcePod: network-check-source-7d88cb55d8-8hdcj
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T09:04:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-103-to-network-check-target-ip-10-0-142-103
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-103.ec2.internal
      uid: 52a947d8-e4f4-451c-bca9-e5951929443c
    resourceVersion: "10927"
    uid: 9fb95bd6-4251-4b00-a87e-5030ca7394f4
  spec:
    sourcePod: network-check-source-7d88cb55d8-8hdcj
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T09:04:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-103-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-103.ec2.internal
      uid: 52a947d8-e4f4-451c-bca9-e5951929443c
    resourceVersion: "14541"
    uid: 297ee147-19f7-48cb-8b03-2745b8eb5692
  spec:
    sourcePod: network-check-source-7d88cb55d8-8hdcj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T09:10:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 731.478µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T09:10:48Z"
    - latency: 2.143422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T09:10:48Z"
    - latency: 859.118µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T09:09:48Z"
    - latency: 2.01985ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T09:09:48Z"
    - latency: 951.893µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T09:08:48Z"
    - latency: 1.787806ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T09:08:48Z"
    - latency: 832.457µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T09:07:48Z"
    - latency: 5.16597ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T09:07:48Z"
    - latency: 917.727µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T09:06:48Z"
    - latency: 1.890141ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T09:06:48Z"
kind: List
metadata:
  resourceVersion: ""