apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:33:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-194-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-194.ec2.internal uid: 8ae7b730-3191-4cc6-a2bc-08b535afb175 resourceVersion: "43542" uid: 0ebce8a9-09c1-4d0a-bc4c-6e19d49c5c95 spec: sourcePod: network-check-source-7f44b6dd87-dpzf5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T11:40:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.376387ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:08:13Z" - latency: 846.877µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:07:13Z" - latency: 1.32512ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:06:13Z" - latency: 1.260445ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:05:13Z" - latency: 1.069973ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:04:13Z" - latency: 987.299µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:03:13Z" - latency: 1.617728ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:02:13Z" - latency: 929.508µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:01:13Z" - latency: 1.045514ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:00:13Z" - latency: 1.032083ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:59:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:33:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-194-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-194.ec2.internal uid: 8ae7b730-3191-4cc6-a2bc-08b535afb175 resourceVersion: "44182" uid: effaa0e0-a17e-4ce8-8da9-683ad035e258 spec: sourcePod: network-check-source-7f44b6dd87-dpzf5 targetEndpoint: aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T11:39:13Z" message: 'load-balancer-api-external: tcp connection to aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 8.637839ms message: 'load-balancer-api-external: tcp connection to aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:09:13Z" - latency: 11.841865ms message: 'load-balancer-api-external: resolved host name aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:09:13Z" - latency: 5.356437ms message: 'load-balancer-api-external: tcp connection to aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:08:13Z" - latency: 6.608875ms message: 'load-balancer-api-external: resolved host name aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:08:13Z" - latency: 5.450823ms message: 'load-balancer-api-external: tcp connection to aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:07:13Z" - latency: 6.990494ms message: 'load-balancer-api-external: resolved host name aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:07:13Z" - latency: 4.572843ms message: 'load-balancer-api-external: tcp connection to aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:06:13Z" - latency: 8.125226ms message: 'load-balancer-api-external: resolved host name aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:06:13Z" - latency: 4.861168ms message: 'load-balancer-api-external: tcp connection to aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:05:13Z" - latency: 9.058605ms message: 'load-balancer-api-external: resolved host name aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:05:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:33:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-194-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-194.ec2.internal uid: 8ae7b730-3191-4cc6-a2bc-08b535afb175 resourceVersion: "44181" uid: eb9528d0-8ea6-490b-9fa3-40bd24b4ec94 spec: sourcePod: network-check-source-7f44b6dd87-dpzf5 targetEndpoint: aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T11:39:13Z" message: 'load-balancer-api-internal: tcp connection to aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.57258ms message: 'load-balancer-api-internal: tcp connection to aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:09:13Z" - latency: 11.877941ms message: 'load-balancer-api-internal: resolved host name aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:09:13Z" - latency: 5.38676ms message: 'load-balancer-api-internal: tcp connection to aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:08:13Z" - latency: 6.652063ms message: 'load-balancer-api-internal: resolved host name aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:08:13Z" - latency: 5.434382ms message: 'load-balancer-api-internal: tcp connection to aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:07:13Z" - latency: 6.963854ms message: 'load-balancer-api-internal: resolved host name aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:07:13Z" - latency: 4.71517ms message: 'load-balancer-api-internal: tcp connection to aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:06:13Z" - latency: 8.0488ms message: 'load-balancer-api-internal: resolved host name aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:06:13Z" - latency: 5.449921ms message: 'load-balancer-api-internal: tcp connection to aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:05:13Z" - latency: 9.131282ms message: 'load-balancer-api-internal: resolved host name aa6d60eeddafa4c74a8ae95aeef2d8e0-83c2ca030e3ac548.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T12:05:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:33:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-194-to-network-check-target-ip-10-0-133-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-194.ec2.internal uid: 8ae7b730-3191-4cc6-a2bc-08b535afb175 resourceVersion: "43541" uid: 18bad008-5728-46b8-8b51-bb669b6cf338 spec: sourcePod: network-check-source-7f44b6dd87-dpzf5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-26T11:40:13Z" message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.2528ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:08:13Z" - latency: 2.244006ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:07:13Z" - latency: 2.211884ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:06:13Z" - latency: 2.364488ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:05:13Z" - latency: 2.556276ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:04:13Z" - latency: 1.778857ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:03:13Z" - latency: 1.796591ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:02:13Z" - latency: 2.130225ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:01:13Z" - latency: 2.160526ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:00:13Z" - latency: 2.022395ms message: 'network-check-target-ip-10-0-133-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:59:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:33:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-194-to-network-check-target-ip-10-0-136-194 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-194.ec2.internal uid: 8ae7b730-3191-4cc6-a2bc-08b535afb175 resourceVersion: "43539" uid: 0282577f-f21e-4cb9-a754-892a950d8af2 spec: sourcePod: network-check-source-7f44b6dd87-dpzf5 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-26T11:40:13Z" message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.508784ms message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:08:13Z" - latency: 1.115483ms message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:07:13Z" - latency: 1.539036ms message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:06:13Z" - latency: 1.20724ms message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:05:13Z" - latency: 1.614694ms message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:04:13Z" - latency: 964.064µs message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:03:13Z" - latency: 835.626µs message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:02:13Z" - latency: 771.079µs message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:01:13Z" - latency: 1.985262ms message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:00:13Z" - latency: 980.809µs message: 'network-check-target-ip-10-0-136-194: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:59:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:33:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-194-to-network-check-target-ip-10-0-136-225 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-194.ec2.internal uid: 8ae7b730-3191-4cc6-a2bc-08b535afb175 resourceVersion: "43540" uid: 4e320420-04b6-4fad-a421-f23c8f9cf549 spec: sourcePod: network-check-source-7f44b6dd87-dpzf5 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-26T11:40:13Z" message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.546267ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:08:13Z" - latency: 2.561739ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:07:13Z" - latency: 2.432273ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:06:13Z" - latency: 2.439066ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:05:13Z" - latency: 2.548331ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:04:13Z" - latency: 2.341409ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:03:13Z" - latency: 2.729912ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:02:13Z" - latency: 2.349677ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:01:13Z" - latency: 2.323982ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:00:13Z" - latency: 2.208495ms message: 'network-check-target-ip-10-0-136-225: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T11:59:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T11:33:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-194-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-194.ec2.internal uid: 8ae7b730-3191-4cc6-a2bc-08b535afb175 resourceVersion: "44180" uid: 29e70694-1327-4b86-999e-45930b30d6ec spec: sourcePod: network-check-source-7f44b6dd87-dpzf5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T11:39:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 723.415µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:09:13Z" - latency: 1.805277ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T12:09:13Z" - latency: 933.521µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:08:13Z" - latency: 2.376266ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T12:08:13Z" - latency: 836.9µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:07:13Z" - latency: 1.952692ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T12:07:13Z" - latency: 1.495216ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:06:13Z" - latency: 1.730086ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T12:06:13Z" - latency: 787.084µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T12:05:13Z" - latency: 2.086817ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T12:05:13Z" kind: List metadata: resourceVersion: ""