apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T11:21:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-205-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-205.ec2.internal
      uid: d1ddafad-9138-486d-9d5f-d24caf8853e8
    resourceVersion: "21329"
    uid: 14e93fc8-19a2-4558-b3de-43416eb0d36d
  spec:
    sourcePod: network-check-source-8894fc9bd-mqf7t
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T11:28:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.007584ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:28:45Z"
    - latency: 817.497µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:27:45Z"
    - latency: 950.04µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:26:45Z"
    - latency: 1.009011ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:25:45Z"
    - latency: 1.073419ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:24:45Z"
    - latency: 987.059µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:23:45Z"
    - latency: 1.349152ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:22:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T11:21:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-205-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-205.ec2.internal
      uid: d1ddafad-9138-486d-9d5f-d24caf8853e8
    resourceVersion: "20406"
    uid: 931794cf-569c-4191-b169-1e70962c98b3
  spec:
    sourcePod: network-check-source-8894fc9bd-mqf7t
    targetEndpoint: a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T11:27:45Z"
      message: 'load-balancer-api-external: tcp connection to a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.67949ms
      message: 'load-balancer-api-external: tcp connection to a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:27:45Z"
    - latency: 6.597553ms
      message: 'load-balancer-api-external: resolved host name a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T11:27:45Z"
    - latency: 5.037818ms
      message: 'load-balancer-api-external: tcp connection to a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:26:45Z"
    - latency: 6.50616ms
      message: 'load-balancer-api-external: resolved host name a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T11:26:45Z"
    - latency: 4.781743ms
      message: 'load-balancer-api-external: tcp connection to a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:25:45Z"
    - latency: 6.463923ms
      message: 'load-balancer-api-external: resolved host name a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T11:25:45Z"
    - latency: 4.991071ms
      message: 'load-balancer-api-external: tcp connection to a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:24:45Z"
    - latency: 7.838038ms
      message: 'load-balancer-api-external: resolved host name a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T11:24:45Z"
    - latency: 4.331468ms
      message: 'load-balancer-api-external: tcp connection to a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:23:45Z"
    - latency: 5.422201ms
      message: 'load-balancer-api-external: resolved host name a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T11:23:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T11:21:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-205-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-205.ec2.internal
      uid: d1ddafad-9138-486d-9d5f-d24caf8853e8
    resourceVersion: "20405"
    uid: 38a8390a-fae7-4ef5-8641-43e00c582968
  spec:
    sourcePod: network-check-source-8894fc9bd-mqf7t
    targetEndpoint: a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T11:27:45Z"
      message: 'load-balancer-api-internal: tcp connection to a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.29414ms
      message: 'load-balancer-api-internal: tcp connection to a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:27:45Z"
    - latency: 6.653262ms
      message: 'load-balancer-api-internal: resolved host name a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T11:27:45Z"
    - latency: 4.617096ms
      message: 'load-balancer-api-internal: tcp connection to a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:26:45Z"
    - latency: 6.400113ms
      message: 'load-balancer-api-internal: resolved host name a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T11:26:45Z"
    - latency: 4.795917ms
      message: 'load-balancer-api-internal: tcp connection to a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:25:45Z"
    - latency: 6.382584ms
      message: 'load-balancer-api-internal: resolved host name a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T11:25:45Z"
    - latency: 5.024933ms
      message: 'load-balancer-api-internal: tcp connection to a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:24:45Z"
    - latency: 7.857847ms
      message: 'load-balancer-api-internal: resolved host name a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T11:24:45Z"
    - latency: 4.04899ms
      message: 'load-balancer-api-internal: tcp connection to a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:23:45Z"
    - latency: 5.558225ms
      message: 'load-balancer-api-internal: resolved host name a9f452ada8ad2477f964e89bdc5db5a6-75d56c191d4fbcfa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T11:23:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T11:21:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-205-to-network-check-target-ip-10-0-128-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-205.ec2.internal
      uid: d1ddafad-9138-486d-9d5f-d24caf8853e8
    resourceVersion: "21325"
    uid: c407d1bc-c45d-4275-ba5e-e094cb8b1818
  spec:
    sourcePod: network-check-source-8894fc9bd-mqf7t
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T11:28:45Z"
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 958.65µs
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:28:45Z"
    - latency: 854.174µs
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:27:45Z"
    - latency: 903.855µs
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:26:45Z"
    - latency: 1.426974ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:25:45Z"
    - latency: 885.704µs
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:24:45Z"
    - latency: 1.040791ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:23:45Z"
    - latency: 1.283228ms
      message: 'network-check-target-ip-10-0-128-205: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:22:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T11:21:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-205-to-network-check-target-ip-10-0-129-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-205.ec2.internal
      uid: d1ddafad-9138-486d-9d5f-d24caf8853e8
    resourceVersion: "21327"
    uid: bab20bef-ced0-4adc-924e-8cf7160af949
  spec:
    sourcePod: network-check-source-8894fc9bd-mqf7t
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T11:28:45Z"
      message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.198371ms
      message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:28:45Z"
    - latency: 2.192903ms
      message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:27:45Z"
    - latency: 2.22211ms
      message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:26:45Z"
    - latency: 2.588289ms
      message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:25:45Z"
    - latency: 2.7935ms
      message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:24:45Z"
    - latency: 2.177287ms
      message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:23:45Z"
    - latency: 2.649912ms
      message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:22:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T11:21:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-205-to-network-check-target-ip-10-0-142-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-205.ec2.internal
      uid: d1ddafad-9138-486d-9d5f-d24caf8853e8
    resourceVersion: "21328"
    uid: 41bfd408-17b4-4d1f-b298-b97471fe717b
  spec:
    sourcePod: network-check-source-8894fc9bd-mqf7t
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T11:28:45Z"
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.314821ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:28:45Z"
    - latency: 1.922462ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:27:45Z"
    - latency: 2.286003ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:26:45Z"
    - latency: 2.155019ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:25:45Z"
    - latency: 2.745653ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:24:45Z"
    - latency: 2.178669ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:23:45Z"
    - latency: 2.282878ms
      message: 'network-check-target-ip-10-0-142-114: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:22:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T11:21:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-205-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-205.ec2.internal
      uid: d1ddafad-9138-486d-9d5f-d24caf8853e8
    resourceVersion: "20404"
    uid: 4eee8e41-7600-4aaf-a35d-4beb54d9083e
  spec:
    sourcePod: network-check-source-8894fc9bd-mqf7t
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T11:27:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 733.429µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:27:45Z"
    - latency: 1.543452ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T11:27:45Z"
    - latency: 927.642µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:26:45Z"
    - latency: 1.554366ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T11:26:45Z"
    - latency: 857.391µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:25:45Z"
    - latency: 1.756271ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T11:25:45Z"
    - latency: 1.272819ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:24:45Z"
    - latency: 1.64595ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T11:24:45Z"
    - latency: 1.314843ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T11:23:45Z"
    - latency: 1.424656ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T11:23:45Z"
kind: List
metadata:
  resourceVersion: ""