apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T09:20:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-73-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-73.ec2.internal
      uid: 6c26c0a1-fd44-4c98-b43d-c69fe83f30ef
    resourceVersion: "14373"
    uid: 4d65cc33-0afb-4693-9503-97fbe8933058
  spec:
    sourcePod: network-check-source-7f44b6dd87-rj9jw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T09:27:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.056841ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:27:01Z"
    - latency: 951.602µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:26:01Z"
    - latency: 977.266µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:25:01Z"
    - latency: 1.349405ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:24:01Z"
    - latency: 1.177811ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:23:01Z"
    - latency: 1.052558ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:22:01Z"
    - latency: 933.44µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:21:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T09:20:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-73-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-73.ec2.internal
      uid: 6c26c0a1-fd44-4c98-b43d-c69fe83f30ef
    resourceVersion: "13645"
    uid: de63424f-13c5-46b4-8b94-15b1984aa088
  spec:
    sourcePod: network-check-source-7f44b6dd87-rj9jw
    targetEndpoint: a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T09:26:01Z"
      message: 'load-balancer-api-external: tcp connection to a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.41192ms
      message: 'load-balancer-api-external: tcp connection to a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:26:01Z"
    - latency: 9.899092ms
      message: 'load-balancer-api-external: resolved host name a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T09:26:01Z"
    - latency: 6.664535ms
      message: 'load-balancer-api-external: tcp connection to a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:25:01Z"
    - latency: 6.371142ms
      message: 'load-balancer-api-external: resolved host name a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T09:25:01Z"
    - latency: 5.555449ms
      message: 'load-balancer-api-external: tcp connection to a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:24:01Z"
    - latency: 6.475287ms
      message: 'load-balancer-api-external: resolved host name a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T09:24:01Z"
    - latency: 5.866422ms
      message: 'load-balancer-api-external: tcp connection to a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:23:01Z"
    - latency: 6.983579ms
      message: 'load-balancer-api-external: resolved host name a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T09:23:01Z"
    - latency: 5.989527ms
      message: 'load-balancer-api-external: tcp connection to a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:22:01Z"
    - latency: 6.919977ms
      message: 'load-balancer-api-external: resolved host name a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T09:22:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T09:20:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-73-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-73.ec2.internal
      uid: 6c26c0a1-fd44-4c98-b43d-c69fe83f30ef
    resourceVersion: "13646"
    uid: 07ec6902-f413-41b4-a5e9-4af13916cf69
  spec:
    sourcePod: network-check-source-7f44b6dd87-rj9jw
    targetEndpoint: a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T09:26:01Z"
      message: 'load-balancer-api-internal: tcp connection to a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.192341ms
      message: 'load-balancer-api-internal: tcp connection to a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:26:01Z"
    - latency: 9.936613ms
      message: 'load-balancer-api-internal: resolved host name a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T09:26:01Z"
    - latency: 6.390452ms
      message: 'load-balancer-api-internal: tcp connection to a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:25:01Z"
    - latency: 6.426481ms
      message: 'load-balancer-api-internal: resolved host name a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T09:25:01Z"
    - latency: 5.56687ms
      message: 'load-balancer-api-internal: tcp connection to a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:24:01Z"
    - latency: 6.423129ms
      message: 'load-balancer-api-internal: resolved host name a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T09:24:01Z"
    - latency: 6.330205ms
      message: 'load-balancer-api-internal: tcp connection to a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:23:01Z"
    - latency: 6.951168ms
      message: 'load-balancer-api-internal: resolved host name a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T09:23:01Z"
    - latency: 8.356672ms
      message: 'load-balancer-api-internal: tcp connection to a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:22:01Z"
    - latency: 6.858466ms
      message: 'load-balancer-api-internal: resolved host name a791eb8bb41d44a8d9f7a03750cc9f80-d9f3aec81f09ba7d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T09:22:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T09:20:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-73-to-network-check-target-ip-10-0-128-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-73.ec2.internal
      uid: 6c26c0a1-fd44-4c98-b43d-c69fe83f30ef
    resourceVersion: "14370"
    uid: 989a975b-b2ba-49f8-aaf9-5594beda2133
  spec:
    sourcePod: network-check-source-7f44b6dd87-rj9jw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T09:27:01Z"
      message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.039658ms
      message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:27:01Z"
    - latency: 895.162µs
      message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:26:01Z"
    - latency: 1.257261ms
      message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:25:01Z"
    - latency: 850.993µs
      message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:24:01Z"
    - latency: 919.547µs
      message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:23:01Z"
    - latency: 1.248729ms
      message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:22:01Z"
    - latency: 1.142316ms
      message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:21:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T09:20:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-73-to-network-check-target-ip-10-0-133-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-73.ec2.internal
      uid: 6c26c0a1-fd44-4c98-b43d-c69fe83f30ef
    resourceVersion: "14371"
    uid: d72cb1e9-fa02-4eb5-ab93-44e10dc0432e
  spec:
    sourcePod: network-check-source-7f44b6dd87-rj9jw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T09:27:01Z"
      message: 'network-check-target-ip-10-0-133-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.76544ms
      message: 'network-check-target-ip-10-0-133-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:27:01Z"
    - latency: 2.108955ms
      message: 'network-check-target-ip-10-0-133-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:26:01Z"
    - latency: 2.345206ms
      message: 'network-check-target-ip-10-0-133-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:25:01Z"
    - latency: 2.192275ms
      message: 'network-check-target-ip-10-0-133-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:24:01Z"
    - latency: 2.041074ms
      message: 'network-check-target-ip-10-0-133-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:23:01Z"
    - latency: 2.178255ms
      message: 'network-check-target-ip-10-0-133-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:22:01Z"
    - latency: 2.325286ms
      message: 'network-check-target-ip-10-0-133-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:21:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T09:20:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-73-to-network-check-target-ip-10-0-135-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-73.ec2.internal
      uid: 6c26c0a1-fd44-4c98-b43d-c69fe83f30ef
    resourceVersion: "14372"
    uid: 2662410f-be37-48de-9df2-4ebdfb83e98c
  spec:
    sourcePod: network-check-source-7f44b6dd87-rj9jw
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T09:27:01Z"
      message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.007471ms
      message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:27:01Z"
    - latency: 2.348697ms
      message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:26:01Z"
    - latency: 2.115103ms
      message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:25:01Z"
    - latency: 2.134108ms
      message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:24:01Z"
    - latency: 2.019658ms
      message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:23:01Z"
    - latency: 2.168619ms
      message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:22:01Z"
    - latency: 2.114842ms
      message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:21:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T09:20:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-73-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-73.ec2.internal
      uid: 6c26c0a1-fd44-4c98-b43d-c69fe83f30ef
    resourceVersion: "13644"
    uid: 116b69c1-233f-4316-bf03-18c80f065a83
  spec:
    sourcePod: network-check-source-7f44b6dd87-rj9jw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T09:26:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.083179ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:26:01Z"
    - latency: 1.720919ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T09:26:01Z"
    - latency: 943.424µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:25:01Z"
    - latency: 1.540238ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T09:25:01Z"
    - latency: 791.009µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:24:01Z"
    - latency: 1.642148ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T09:24:01Z"
    - latency: 831.786µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:23:01Z"
    - latency: 2.440361ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T09:23:01Z"
    - latency: 1.091414ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T09:22:01Z"
    - latency: 1.890274ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T09:22:01Z"
kind: List
metadata:
  resourceVersion: ""