apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:49:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-118-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-118.ec2.internal
      uid: a18a7d4b-88d2-4e07-ab0c-0c5c5f3b3d86
    resourceVersion: "24563"
    uid: 2477ed40-5227-4995-911b-44623c5caba4
  spec:
    sourcePod: network-check-source-6947749cfc-j95d8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:56:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.005263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:56:38Z"
    - latency: 881.991µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:55:38Z"
    - latency: 858.493µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:54:38Z"
    - latency: 1.473501ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:53:38Z"
    - latency: 1.262318ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:52:38Z"
    - latency: 1.411836ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:51:38Z"
    - latency: 1.591119ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:50:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:49:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-118-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-118.ec2.internal
      uid: a18a7d4b-88d2-4e07-ab0c-0c5c5f3b3d86
    resourceVersion: "23917"
    uid: 07e67db9-8fe2-428c-bf05-4c1076497910
  spec:
    sourcePod: network-check-source-6947749cfc-j95d8
    targetEndpoint: a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:55:38Z"
      message: 'load-balancer-api-external: tcp connection to a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.774436ms
      message: 'load-balancer-api-external: tcp connection to a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:55:38Z"
    - latency: 9.24299ms
      message: 'load-balancer-api-external: resolved host name a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:55:38Z"
    - latency: 6.148468ms
      message: 'load-balancer-api-external: tcp connection to a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:54:38Z"
    - latency: 8.375214ms
      message: 'load-balancer-api-external: resolved host name a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:54:38Z"
    - latency: 6.826054ms
      message: 'load-balancer-api-external: tcp connection to a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:53:38Z"
    - latency: 8.487547ms
      message: 'load-balancer-api-external: resolved host name a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:53:38Z"
    - latency: 4.119722ms
      message: 'load-balancer-api-external: tcp connection to a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:52:38Z"
    - latency: 8.26099ms
      message: 'load-balancer-api-external: resolved host name a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:52:38Z"
    - latency: 5.024671ms
      message: 'load-balancer-api-external: tcp connection to a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:51:38Z"
    - latency: 8.614235ms
      message: 'load-balancer-api-external: resolved host name a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:51:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:49:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-118-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-118.ec2.internal
      uid: a18a7d4b-88d2-4e07-ab0c-0c5c5f3b3d86
    resourceVersion: "23916"
    uid: 835a4224-71e2-4122-9625-134511aad072
  spec:
    sourcePod: network-check-source-6947749cfc-j95d8
    targetEndpoint: a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:55:38Z"
      message: 'load-balancer-api-internal: tcp connection to a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.994807ms
      message: 'load-balancer-api-internal: tcp connection to a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:55:38Z"
    - latency: 9.320436ms
      message: 'load-balancer-api-internal: resolved host name a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:55:38Z"
    - latency: 3.953149ms
      message: 'load-balancer-api-internal: tcp connection to a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:54:38Z"
    - latency: 8.412769ms
      message: 'load-balancer-api-internal: resolved host name a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:54:38Z"
    - latency: 5.176058ms
      message: 'load-balancer-api-internal: tcp connection to a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:53:38Z"
    - latency: 8.525687ms
      message: 'load-balancer-api-internal: resolved host name a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:53:38Z"
    - latency: 4.095499ms
      message: 'load-balancer-api-internal: tcp connection to a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:52:38Z"
    - latency: 8.301757ms
      message: 'load-balancer-api-internal: resolved host name a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:52:38Z"
    - latency: 5.030172ms
      message: 'load-balancer-api-internal: tcp connection to a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:51:38Z"
    - latency: 8.568767ms
      message: 'load-balancer-api-internal: resolved host name a0bbb83b42c7448eeaec2b594c563a14-82e4c8fad592674d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:51:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:49:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-118-to-network-check-target-ip-10-0-135-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-118.ec2.internal
      uid: a18a7d4b-88d2-4e07-ab0c-0c5c5f3b3d86
    resourceVersion: "24561"
    uid: d4da7020-a0ea-40fb-bbc3-073edb9046f1
  spec:
    sourcePod: network-check-source-6947749cfc-j95d8
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:56:38Z"
      message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.195204ms
      message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:56:38Z"
    - latency: 2.248906ms
      message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:55:38Z"
    - latency: 2.566549ms
      message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:54:38Z"
    - latency: 2.306114ms
      message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:53:38Z"
    - latency: 2.257635ms
      message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:52:38Z"
    - latency: 2.299661ms
      message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:51:38Z"
    - latency: 2.406485ms
      message: 'network-check-target-ip-10-0-135-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:50:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:49:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-118-to-network-check-target-ip-10-0-138-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-118.ec2.internal
      uid: a18a7d4b-88d2-4e07-ab0c-0c5c5f3b3d86
    resourceVersion: "24560"
    uid: 949a6b5f-c532-451a-b68a-a02be7a7af7b
  spec:
    sourcePod: network-check-source-6947749cfc-j95d8
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:56:38Z"
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 837.933µs
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:56:38Z"
    - latency: 1.205663ms
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:55:38Z"
    - latency: 1.373555ms
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:54:38Z"
    - latency: 808.36µs
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:53:38Z"
    - latency: 1.639377ms
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:52:38Z"
    - latency: 689.804µs
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:51:38Z"
    - latency: 1.144752ms
      message: 'network-check-target-ip-10-0-138-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:50:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:49:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-118-to-network-check-target-ip-10-0-141-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-118.ec2.internal
      uid: a18a7d4b-88d2-4e07-ab0c-0c5c5f3b3d86
    resourceVersion: "24562"
    uid: 032a2867-f57c-432e-bc40-a00a150b5b3a
  spec:
    sourcePod: network-check-source-6947749cfc-j95d8
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:56:38Z"
      message: 'network-check-target-ip-10-0-141-164: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.073904ms
      message: 'network-check-target-ip-10-0-141-164: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:56:38Z"
    - latency: 2.279099ms
      message: 'network-check-target-ip-10-0-141-164: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:55:38Z"
    - latency: 2.50109ms
      message: 'network-check-target-ip-10-0-141-164: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:54:38Z"
    - latency: 2.351046ms
      message: 'network-check-target-ip-10-0-141-164: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:53:38Z"
    - latency: 2.050433ms
      message: 'network-check-target-ip-10-0-141-164: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:52:38Z"
    - latency: 2.000905ms
      message: 'network-check-target-ip-10-0-141-164: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:51:38Z"
    - latency: 2.66309ms
      message: 'network-check-target-ip-10-0-141-164: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:50:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T21:49:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-118-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-118.ec2.internal
      uid: a18a7d4b-88d2-4e07-ab0c-0c5c5f3b3d86
    resourceVersion: "23915"
    uid: f1712532-34b6-4fd0-af64-ae9d98b857b4
  spec:
    sourcePod: network-check-source-6947749cfc-j95d8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T21:55:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 893.635µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:55:38Z"
    - latency: 1.654015ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:55:38Z"
    - latency: 803.904µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:54:38Z"
    - latency: 2.044884ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:54:38Z"
    - latency: 969.771µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:53:38Z"
    - latency: 2.02569ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:53:38Z"
    - latency: 1.082191ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:52:38Z"
    - latency: 1.766408ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:52:38Z"
    - latency: 775.094µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T21:51:38Z"
    - latency: 1.676538ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T21:51:38Z"
kind: List
metadata:
  resourceVersion: ""