apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T10:00:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-38-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-38.ec2.internal uid: 7b6665f5-3a23-4039-99c0-835d145e48bd resourceVersion: "14656" uid: ae23b36b-862b-4b3f-8977-2ce7b0646a48 spec: sourcePod: network-check-source-7d88cb55d8-z4n28 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T10:07:43Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 910.564µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:07:43Z" - latency: 951.554µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:06:43Z" - latency: 1.466566ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:05:43Z" - latency: 943.207µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:04:43Z" - latency: 1.160641ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:03:43Z" - latency: 895.393µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:02:43Z" - latency: 1.036537ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:01:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T10:00:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-38-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-38.ec2.internal uid: 7b6665f5-3a23-4039-99c0-835d145e48bd resourceVersion: "14195" uid: 9deccf2f-3bfb-4d70-99b6-ae720a7f51e6 spec: sourcePod: network-check-source-7d88cb55d8-z4n28 targetEndpoint: ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T10:06:43Z" message: 'load-balancer-api-external: tcp connection to ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.04233ms message: 'load-balancer-api-external: tcp connection to ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:06:43Z" - latency: 8.223451ms message: 'load-balancer-api-external: resolved host name ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T10:06:43Z" - latency: 4.387878ms message: 'load-balancer-api-external: tcp connection to ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:05:43Z" - latency: 7.911249ms message: 'load-balancer-api-external: resolved host name ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T10:05:43Z" - latency: 5.444819ms message: 'load-balancer-api-external: tcp connection to ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:04:43Z" - latency: 8.890475ms message: 'load-balancer-api-external: resolved host name ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T10:04:43Z" - latency: 4.251163ms message: 'load-balancer-api-external: tcp connection to ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:03:43Z" - latency: 11.965469ms message: 'load-balancer-api-external: resolved host name ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T10:03:43Z" - latency: 5.33683ms message: 'load-balancer-api-external: tcp connection to ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:02:43Z" - latency: 7.976224ms message: 'load-balancer-api-external: resolved host name ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T10:02:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T10:00:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-38-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-38.ec2.internal uid: 7b6665f5-3a23-4039-99c0-835d145e48bd resourceVersion: "14194" uid: af16c5c1-1afd-4a4e-ba6a-828108445197 spec: sourcePod: network-check-source-7d88cb55d8-z4n28 targetEndpoint: ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T10:06:43Z" message: 'load-balancer-api-internal: tcp connection to ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.310605ms message: 'load-balancer-api-internal: tcp connection to ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:06:43Z" - latency: 8.069055ms message: 'load-balancer-api-internal: resolved host name ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T10:06:43Z" - latency: 4.517008ms message: 'load-balancer-api-internal: tcp connection to ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:05:43Z" - latency: 7.843241ms message: 'load-balancer-api-internal: resolved host name ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T10:05:43Z" - latency: 5.444516ms message: 'load-balancer-api-internal: tcp connection to ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:04:43Z" - latency: 8.826742ms message: 'load-balancer-api-internal: resolved host name ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T10:04:43Z" - latency: 4.246822ms message: 'load-balancer-api-internal: tcp connection to ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:03:43Z" - latency: 11.840327ms message: 'load-balancer-api-internal: resolved host name ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T10:03:43Z" - latency: 5.258547ms message: 'load-balancer-api-internal: tcp connection to ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:02:43Z" - latency: 7.872826ms message: 'load-balancer-api-internal: resolved host name ab474de0e5d4a4b90ba4806d27f3632c-a4b466bd84ca2ff6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T10:02:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T10:00:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-38-to-network-check-target-ip-10-0-131-23 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-38.ec2.internal uid: 7b6665f5-3a23-4039-99c0-835d145e48bd resourceVersion: "14654" uid: 8e6d7c10-5c31-44c5-9491-9a37e20fd82e spec: sourcePod: network-check-source-7d88cb55d8-z4n28 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T10:07:43Z" message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.816831ms message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:07:43Z" - latency: 1.771904ms message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:06:43Z" - latency: 2.594042ms message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:05:43Z" - latency: 1.739534ms message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:04:43Z" - latency: 1.753985ms message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:03:43Z" - latency: 1.776958ms message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:02:43Z" - latency: 2.082133ms message: 'network-check-target-ip-10-0-131-23: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:01:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T10:00:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-38-to-network-check-target-ip-10-0-134-38 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-38.ec2.internal uid: 7b6665f5-3a23-4039-99c0-835d145e48bd resourceVersion: "14653" uid: 59b5823e-cf06-4589-97b2-005547ab6e6e spec: sourcePod: network-check-source-7d88cb55d8-z4n28 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T10:07:43Z" message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 834.533µs message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:07:43Z" - latency: 765.251µs message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:06:43Z" - latency: 1.506821ms message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:05:43Z" - latency: 847.288µs message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:04:43Z" - latency: 833.149µs message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:03:43Z" - latency: 1.103677ms message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:02:43Z" - latency: 1.186617ms message: 'network-check-target-ip-10-0-134-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:01:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T10:00:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-38-to-network-check-target-ip-10-0-136-247 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-38.ec2.internal uid: 7b6665f5-3a23-4039-99c0-835d145e48bd resourceVersion: "14655" uid: 70ce82fa-e980-4d9f-9eca-4679cced8d2e spec: sourcePod: network-check-source-7d88cb55d8-z4n28 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T10:07:43Z" message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.155995ms message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:07:43Z" - latency: 2.286705ms message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:06:43Z" - latency: 2.213217ms message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:05:43Z" - latency: 2.22125ms message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:04:43Z" - latency: 2.178608ms message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:03:43Z" - latency: 2.220882ms message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:02:43Z" - latency: 2.21203ms message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:01:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T10:00:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-38-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-38.ec2.internal uid: 7b6665f5-3a23-4039-99c0-835d145e48bd resourceVersion: "14193" uid: 2c555172-32a1-4bcd-b1ea-155d1a796b27 spec: sourcePod: network-check-source-7d88cb55d8-z4n28 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T10:06:43Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 739.599µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:06:43Z" - latency: 1.764279ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T10:06:43Z" - latency: 825.062µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:05:43Z" - latency: 1.703401ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T10:05:43Z" - latency: 755.363µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:04:43Z" - latency: 2.066376ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T10:04:43Z" - latency: 749.142µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:03:43Z" - latency: 1.628291ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T10:03:43Z" - latency: 1.117873ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T10:02:43Z" - latency: 1.772338ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T10:02:43Z" kind: List metadata: resourceVersion: ""