apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:24:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-144-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-144.ec2.internal
      uid: 015378e8-d422-4136-9680-e01a58730a93
    resourceVersion: "10418"
    uid: e0e7cb8b-0b83-4c79-9516-b538136e5739
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pr2n5
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:24:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-144-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-144.ec2.internal
      uid: 015378e8-d422-4136-9680-e01a58730a93
    resourceVersion: "13988"
    uid: be953b2d-35e7-4a9b-8991-ec8b189b8097
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pr2n5
    targetEndpoint: ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:30:02Z"
      message: 'load-balancer-api-external: tcp connection to ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.782709ms
      message: 'load-balancer-api-external: tcp connection to ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:30:02Z"
    - latency: 19.202068ms
      message: 'load-balancer-api-external: resolved host name ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:30:02Z"
    - latency: 6.506391ms
      message: 'load-balancer-api-external: tcp connection to ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:29:02Z"
    - latency: 17.832022ms
      message: 'load-balancer-api-external: resolved host name ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:29:02Z"
    - latency: 5.300792ms
      message: 'load-balancer-api-external: tcp connection to ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:28:02Z"
    - latency: 14.347143ms
      message: 'load-balancer-api-external: resolved host name ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:28:02Z"
    - latency: 5.833141ms
      message: 'load-balancer-api-external: tcp connection to ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:27:02Z"
    - latency: 9.431551ms
      message: 'load-balancer-api-external: resolved host name ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:27:02Z"
    - latency: 5.68349ms
      message: 'load-balancer-api-external: tcp connection to ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:26:02Z"
    - latency: 10.568104ms
      message: 'load-balancer-api-external: resolved host name ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:26:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:24:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-144-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-144.ec2.internal
      uid: 015378e8-d422-4136-9680-e01a58730a93
    resourceVersion: "13987"
    uid: 9cdb2710-691c-4f45-80c7-659be5a0cb49
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pr2n5
    targetEndpoint: ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:30:02Z"
      message: 'load-balancer-api-internal: tcp connection to ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.776359ms
      message: 'load-balancer-api-internal: tcp connection to ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:30:02Z"
    - latency: 19.235063ms
      message: 'load-balancer-api-internal: resolved host name ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:30:02Z"
    - latency: 6.542995ms
      message: 'load-balancer-api-internal: tcp connection to ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:29:02Z"
    - latency: 17.770427ms
      message: 'load-balancer-api-internal: resolved host name ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:29:02Z"
    - latency: 4.909717ms
      message: 'load-balancer-api-internal: tcp connection to ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:28:02Z"
    - latency: 14.417148ms
      message: 'load-balancer-api-internal: resolved host name ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:28:02Z"
    - latency: 5.818209ms
      message: 'load-balancer-api-internal: tcp connection to ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:27:02Z"
    - latency: 9.488664ms
      message: 'load-balancer-api-internal: resolved host name ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:27:02Z"
    - latency: 5.702529ms
      message: 'load-balancer-api-internal: tcp connection to ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:26:02Z"
    - latency: 10.522875ms
      message: 'load-balancer-api-internal: resolved host name ad15010d9e8f849b9b2a95048b46a831-ec1d063f196b5fb6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:26:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:24:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-144-to-network-check-target-ip-10-0-136-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-144.ec2.internal
      uid: 015378e8-d422-4136-9680-e01a58730a93
    resourceVersion: "10417"
    uid: d5aac3d0-7f78-47c4-87c0-a902d1b06624
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pr2n5
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:24:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-144-to-network-check-target-ip-10-0-138-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-144.ec2.internal
      uid: 015378e8-d422-4136-9680-e01a58730a93
    resourceVersion: "10414"
    uid: 1e6281ab-37ff-4bb3-ac19-da298737bd7b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pr2n5
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:24:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-144-to-network-check-target-ip-10-0-139-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-144.ec2.internal
      uid: 015378e8-d422-4136-9680-e01a58730a93
    resourceVersion: "10415"
    uid: 85718d22-fe53-4869-b8d8-5371a00cd526
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pr2n5
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:24:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-144-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-144.ec2.internal
      uid: 015378e8-d422-4136-9680-e01a58730a93
    resourceVersion: "13986"
    uid: c118d71c-8a7a-487d-affc-d1597689fc21
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pr2n5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:30:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 963.71µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:30:02Z"
    - latency: 1.653124ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:30:02Z"
    - latency: 1.124197ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:29:02Z"
    - latency: 1.736872ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:29:02Z"
    - latency: 821.078µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:28:02Z"
    - latency: 2.069265ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:28:02Z"
    - latency: 862.411µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:27:02Z"
    - latency: 1.639582ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:27:02Z"
    - latency: 1.076796ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:26:02Z"
    - latency: 1.913692ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:26:02Z"
kind: List
metadata:
  resourceVersion: ""