apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:10:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-163-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-163.ec2.internal
      uid: 312f0600-03e1-42ff-9710-e5e2cfe3212c
    resourceVersion: "11118"
    uid: d94117a0-df4a-433d-937a-4c86bd452999
  spec:
    sourcePod: network-check-source-989f8b8dc-w7ng4
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:10:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-163-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-163.ec2.internal
      uid: 312f0600-03e1-42ff-9710-e5e2cfe3212c
    resourceVersion: "14697"
    uid: fc053fef-4100-4209-b96a-2cac84bda3e9
  spec:
    sourcePod: network-check-source-989f8b8dc-w7ng4
    targetEndpoint: a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:16:19Z"
      message: 'load-balancer-api-external: tcp connection to a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 10.671993ms
      message: 'load-balancer-api-external: tcp connection to a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:16:19Z"
    - latency: 8.670537ms
      message: 'load-balancer-api-external: resolved host name a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:16:19Z"
    - latency: 5.577612ms
      message: 'load-balancer-api-external: tcp connection to a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:15:19Z"
    - latency: 8.236946ms
      message: 'load-balancer-api-external: resolved host name a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:15:19Z"
    - latency: 21.567658ms
      message: 'load-balancer-api-external: tcp connection to a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:14:19Z"
    - latency: 8.055976ms
      message: 'load-balancer-api-external: resolved host name a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:14:19Z"
    - latency: 4.016039ms
      message: 'load-balancer-api-external: tcp connection to a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:13:19Z"
    - latency: 8.500268ms
      message: 'load-balancer-api-external: resolved host name a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:13:19Z"
    - latency: 5.22366ms
      message: 'load-balancer-api-external: tcp connection to a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:12:19Z"
    - latency: 8.356662ms
      message: 'load-balancer-api-external: resolved host name a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:12:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:10:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-163-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-163.ec2.internal
      uid: 312f0600-03e1-42ff-9710-e5e2cfe3212c
    resourceVersion: "14698"
    uid: a4905bcc-4af8-4fac-9f97-76344060681c
  spec:
    sourcePod: network-check-source-989f8b8dc-w7ng4
    targetEndpoint: a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:16:19Z"
      message: 'load-balancer-api-internal: tcp connection to a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 14.2494ms
      message: 'load-balancer-api-internal: tcp connection to a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:16:19Z"
    - latency: 8.696324ms
      message: 'load-balancer-api-internal: resolved host name a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:16:19Z"
    - latency: 5.505946ms
      message: 'load-balancer-api-internal: tcp connection to a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:15:19Z"
    - latency: 8.218966ms
      message: 'load-balancer-api-internal: resolved host name a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:15:19Z"
    - latency: 21.593736ms
      message: 'load-balancer-api-internal: tcp connection to a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:14:19Z"
    - latency: 7.990409ms
      message: 'load-balancer-api-internal: resolved host name a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:14:19Z"
    - latency: 4.68961ms
      message: 'load-balancer-api-internal: tcp connection to a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:13:19Z"
    - latency: 8.510081ms
      message: 'load-balancer-api-internal: resolved host name a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:13:19Z"
    - latency: 5.573839ms
      message: 'load-balancer-api-internal: tcp connection to a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:12:19Z"
    - latency: 8.402096ms
      message: 'load-balancer-api-internal: resolved host name a46927a0d8df74326aa1c10594fedb98-deaa7413966fb27a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:12:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:10:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-163-to-network-check-target-ip-10-0-131-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-163.ec2.internal
      uid: 312f0600-03e1-42ff-9710-e5e2cfe3212c
    resourceVersion: "11115"
    uid: 2787d7b4-08a6-45f3-9ce5-1f33b3cb47e0
  spec:
    sourcePod: network-check-source-989f8b8dc-w7ng4
    targetEndpoint: 10.133.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:10:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-163-to-network-check-target-ip-10-0-133-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-163.ec2.internal
      uid: 312f0600-03e1-42ff-9710-e5e2cfe3212c
    resourceVersion: "11114"
    uid: cdcdd295-01bb-4386-aa1e-18f0f0daf4be
  spec:
    sourcePod: network-check-source-989f8b8dc-w7ng4
    targetEndpoint: 10.132.0.3:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:10:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-163-to-network-check-target-ip-10-0-141-18
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-163.ec2.internal
      uid: 312f0600-03e1-42ff-9710-e5e2cfe3212c
    resourceVersion: "11117"
    uid: a22d35ce-9111-40a1-b87a-74a48c1133b1
  spec:
    sourcePod: network-check-source-989f8b8dc-w7ng4
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:10:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-163-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-163.ec2.internal
      uid: 312f0600-03e1-42ff-9710-e5e2cfe3212c
    resourceVersion: "14696"
    uid: 00f0eb13-a3cd-4de8-875f-ed745b1c650c
  spec:
    sourcePod: network-check-source-989f8b8dc-w7ng4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:16:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.007469ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:16:19Z"
    - latency: 1.921102ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:16:19Z"
    - latency: 1.098144ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:15:19Z"
    - latency: 1.779247ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:15:19Z"
    - latency: 875.247µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:14:19Z"
    - latency: 1.702206ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:14:19Z"
    - latency: 759.985µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:13:19Z"
    - latency: 1.946291ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:13:19Z"
    - latency: 1.03642ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:12:19Z"
    - latency: 1.849533ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:12:19Z"
kind: List
metadata:
  resourceVersion: ""