apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-249-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-249.ec2.internal
      uid: 1da4e483-6daa-4ec7-a093-bb512b352e70
    resourceVersion: "10917"
    uid: 512ec774-68fd-4aa0-a994-428393bc9a50
  spec:
    sourcePod: network-check-source-989f8b8dc-dgcvl
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-249-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-249.ec2.internal
      uid: 1da4e483-6daa-4ec7-a093-bb512b352e70
    resourceVersion: "21438"
    uid: ffeb7b51-ea30-4753-b421-84b48f9f63f1
  spec:
    sourcePod: network-check-source-989f8b8dc-dgcvl
    targetEndpoint: acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T18:24:23Z"
      message: 'load-balancer-api-external: tcp connection to acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.125002ms
      message: 'load-balancer-api-external: tcp connection to acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:24:23Z"
    - latency: 6.840352ms
      message: 'load-balancer-api-external: resolved host name acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:24:23Z"
    - latency: 6.389229ms
      message: 'load-balancer-api-external: tcp connection to acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:23:23Z"
    - latency: 6.92678ms
      message: 'load-balancer-api-external: resolved host name acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:23:23Z"
    - latency: 3.841267ms
      message: 'load-balancer-api-external: tcp connection to acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:22:23Z"
    - latency: 6.660393ms
      message: 'load-balancer-api-external: resolved host name acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:22:23Z"
    - latency: 6.05993ms
      message: 'load-balancer-api-external: tcp connection to acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:21:23Z"
    - latency: 7.778168ms
      message: 'load-balancer-api-external: resolved host name acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:21:23Z"
    - latency: 5.209913ms
      message: 'load-balancer-api-external: tcp connection to acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:20:23Z"
    - latency: 8.346792ms
      message: 'load-balancer-api-external: resolved host name acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:20:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-249-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-249.ec2.internal
      uid: 1da4e483-6daa-4ec7-a093-bb512b352e70
    resourceVersion: "21439"
    uid: 633a32bd-4364-41d6-92ea-1a07d852f09e
  spec:
    sourcePod: network-check-source-989f8b8dc-dgcvl
    targetEndpoint: acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T18:24:23Z"
      message: 'load-balancer-api-internal: tcp connection to acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.166464ms
      message: 'load-balancer-api-internal: tcp connection to acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:24:23Z"
    - latency: 6.764633ms
      message: 'load-balancer-api-internal: resolved host name acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:24:23Z"
    - latency: 5.800808ms
      message: 'load-balancer-api-internal: tcp connection to acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:23:23Z"
    - latency: 6.948249ms
      message: 'load-balancer-api-internal: resolved host name acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:23:23Z"
    - latency: 3.635255ms
      message: 'load-balancer-api-internal: tcp connection to acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:22:23Z"
    - latency: 6.716429ms
      message: 'load-balancer-api-internal: resolved host name acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:22:23Z"
    - latency: 8.930798ms
      message: 'load-balancer-api-internal: tcp connection to acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:21:23Z"
    - latency: 7.825753ms
      message: 'load-balancer-api-internal: resolved host name acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:21:23Z"
    - latency: 5.178954ms
      message: 'load-balancer-api-internal: tcp connection to acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:20:23Z"
    - latency: 8.367232ms
      message: 'load-balancer-api-internal: resolved host name acbaa24389ffd44588d56bb8591077db-8c231ed3e1e768c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:20:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-249-to-network-check-target-ip-10-0-133-130
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-249.ec2.internal
      uid: 1da4e483-6daa-4ec7-a093-bb512b352e70
    resourceVersion: "10924"
    uid: 26eb2388-87da-4886-af2c-82a4c92194e4
  spec:
    sourcePod: network-check-source-989f8b8dc-dgcvl
    targetEndpoint: 10.134.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-249-to-network-check-target-ip-10-0-133-249
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-249.ec2.internal
      uid: 1da4e483-6daa-4ec7-a093-bb512b352e70
    resourceVersion: "10922"
    uid: c973c789-f007-4ed0-af0c-25467a178811
  spec:
    sourcePod: network-check-source-989f8b8dc-dgcvl
    targetEndpoint: 10.132.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-249-to-network-check-target-ip-10-0-142-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-249.ec2.internal
      uid: 1da4e483-6daa-4ec7-a093-bb512b352e70
    resourceVersion: "10923"
    uid: 6bf68a60-0213-477c-996c-747cb8a6df6b
  spec:
    sourcePod: network-check-source-989f8b8dc-dgcvl
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-249-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-249.ec2.internal
      uid: 1da4e483-6daa-4ec7-a093-bb512b352e70
    resourceVersion: "21437"
    uid: 0ec7eda1-87ca-4dcc-813b-3ef8d27f586e
  spec:
    sourcePod: network-check-source-989f8b8dc-dgcvl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T18:24:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 709.748µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:24:23Z"
    - latency: 1.860771ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:24:23Z"
    - latency: 2.033261ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:23:23Z"
    - latency: 1.951728ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:23:23Z"
    - latency: 1.071842ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:22:23Z"
    - latency: 1.700995ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:22:23Z"
    - latency: 1.867907ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:21:23Z"
    - latency: 1.602024ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:21:23Z"
    - latency: 1.004392ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:20:23Z"
    - latency: 2.027153ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:20:23Z"
kind: List
metadata:
  resourceVersion: ""