apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:37:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-192-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-192.ec2.internal uid: 338f7327-666b-41c9-b5b8-249501d19519 resourceVersion: "43154" uid: a9465791-54fa-41ca-a1fc-59db26be28b7 spec: sourcePod: network-check-source-7f44b6dd87-5t8kr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T18:44:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 940.622µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:05:42Z" - latency: 913.572µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:04:42Z" - latency: 1.211043ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:03:42Z" - latency: 1.094235ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:02:42Z" - latency: 1.149649ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:01:42Z" - latency: 1.231528ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:00:42Z" - latency: 1.210615ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:59:42Z" - latency: 1.008209ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:58:42Z" - latency: 1.120822ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:57:42Z" - latency: 1.381054ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:56:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:37:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-192-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-192.ec2.internal uid: 338f7327-666b-41c9-b5b8-249501d19519 resourceVersion: "45406" uid: 5e361b11-aa7b-4ad8-ab68-b1806ad57b7d spec: sourcePod: network-check-source-7f44b6dd87-5t8kr targetEndpoint: a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T18:43:42Z" message: 'load-balancer-api-external: tcp connection to a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.530509ms message: 'load-balancer-api-external: tcp connection to a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:07:42Z" - latency: 7.778394ms message: 'load-balancer-api-external: resolved host name a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T19:07:42Z" - latency: 5.610671ms message: 'load-balancer-api-external: tcp connection to a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:06:42Z" - latency: 14.816752ms message: 'load-balancer-api-external: resolved host name a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T19:06:42Z" - latency: 5.199444ms message: 'load-balancer-api-external: tcp connection to a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:05:42Z" - latency: 8.589949ms message: 'load-balancer-api-external: resolved host name a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T19:05:42Z" - latency: 5.456172ms message: 'load-balancer-api-external: tcp connection to a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:04:42Z" - latency: 8.630095ms message: 'load-balancer-api-external: resolved host name a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T19:04:42Z" - latency: 4.932714ms message: 'load-balancer-api-external: tcp connection to a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:03:42Z" - latency: 8.884101ms message: 'load-balancer-api-external: resolved host name a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T19:03:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:37:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-192-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-192.ec2.internal uid: 338f7327-666b-41c9-b5b8-249501d19519 resourceVersion: "45407" uid: 3f0b9b6b-18e3-45fb-b9a2-53f79a4e1df6 spec: sourcePod: network-check-source-7f44b6dd87-5t8kr targetEndpoint: a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T18:43:42Z" message: 'load-balancer-api-internal: tcp connection to a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.502274ms message: 'load-balancer-api-internal: tcp connection to a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:07:42Z" - latency: 7.741367ms message: 'load-balancer-api-internal: resolved host name a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T19:07:42Z" - latency: 5.636607ms message: 'load-balancer-api-internal: tcp connection to a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:06:42Z" - latency: 14.760456ms message: 'load-balancer-api-internal: resolved host name a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T19:06:42Z" - latency: 5.203135ms message: 'load-balancer-api-internal: tcp connection to a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:05:42Z" - latency: 8.466762ms message: 'load-balancer-api-internal: resolved host name a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T19:05:42Z" - latency: 5.505736ms message: 'load-balancer-api-internal: tcp connection to a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:04:42Z" - latency: 8.671665ms message: 'load-balancer-api-internal: resolved host name a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T19:04:42Z" - latency: 4.924469ms message: 'load-balancer-api-internal: tcp connection to a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:03:42Z" - latency: 8.969317ms message: 'load-balancer-api-internal: resolved host name a6d22352a7fe14bd1badba7fc4f3d720-f46d5be98b38d8f7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T19:03:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:37:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-192-to-network-check-target-ip-10-0-128-227 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-192.ec2.internal uid: 338f7327-666b-41c9-b5b8-249501d19519 resourceVersion: "43152" uid: abc81bf3-dad7-40c8-8a98-4d10b77cce12 spec: sourcePod: network-check-source-7f44b6dd87-5t8kr targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T18:44:42Z" message: 'network-check-target-ip-10-0-128-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.145493ms message: 'network-check-target-ip-10-0-128-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:05:42Z" - latency: 2.633403ms message: 'network-check-target-ip-10-0-128-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:04:42Z" - latency: 2.293357ms message: 'network-check-target-ip-10-0-128-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:03:42Z" - latency: 2.549152ms message: 'network-check-target-ip-10-0-128-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:02:42Z" - latency: 2.423149ms message: 'network-check-target-ip-10-0-128-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:01:42Z" - latency: 2.249847ms message: 'network-check-target-ip-10-0-128-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:00:42Z" - latency: 2.609546ms message: 'network-check-target-ip-10-0-128-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:59:42Z" - latency: 2.174757ms message: 'network-check-target-ip-10-0-128-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:58:42Z" - latency: 2.294043ms message: 'network-check-target-ip-10-0-128-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:57:42Z" - latency: 2.174509ms message: 'network-check-target-ip-10-0-128-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:56:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:37:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-192-to-network-check-target-ip-10-0-134-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-192.ec2.internal uid: 338f7327-666b-41c9-b5b8-249501d19519 resourceVersion: "43151" uid: c3c5768f-48ae-45ee-b337-c7472ab25c03 spec: sourcePod: network-check-source-7f44b6dd87-5t8kr targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T18:44:42Z" message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 807.988µs message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:05:42Z" - latency: 783.655µs message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:04:42Z" - latency: 899.382µs message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:03:42Z" - latency: 768.805µs message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:02:42Z" - latency: 1.256505ms message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:01:42Z" - latency: 803.686µs message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:00:42Z" - latency: 742.878µs message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:59:42Z" - latency: 858.876µs message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:58:42Z" - latency: 779.599µs message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:57:42Z" - latency: 868.969µs message: 'network-check-target-ip-10-0-134-192: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:56:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:37:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-192-to-network-check-target-ip-10-0-135-21 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-192.ec2.internal uid: 338f7327-666b-41c9-b5b8-249501d19519 resourceVersion: "43153" uid: f3ad2aee-c4ba-4fb5-a92a-eae431372d58 spec: sourcePod: network-check-source-7f44b6dd87-5t8kr targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T18:44:42Z" message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.640202ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:05:42Z" - latency: 2.271754ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:04:42Z" - latency: 2.315452ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:03:42Z" - latency: 2.407564ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:02:42Z" - latency: 2.171476ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:01:42Z" - latency: 2.167189ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:00:42Z" - latency: 2.195968ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:59:42Z" - latency: 2.204884ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:58:42Z" - latency: 2.578347ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:57:42Z" - latency: 2.270388ms message: 'network-check-target-ip-10-0-135-21: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:56:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:37:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-192-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-192.ec2.internal uid: 338f7327-666b-41c9-b5b8-249501d19519 resourceVersion: "45405" uid: b97276e5-98e3-4b60-8da7-518c768b315d spec: sourcePod: network-check-source-7f44b6dd87-5t8kr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T18:43:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 715.614µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:07:42Z" - latency: 1.5414ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T19:07:42Z" - latency: 881.122µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:06:42Z" - latency: 1.832791ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T19:06:42Z" - latency: 1.135027ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:05:42Z" - latency: 1.813121ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T19:05:42Z" - latency: 775.093µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:04:42Z" - latency: 1.74435ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T19:04:42Z" - latency: 1.102279ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T19:03:42Z" - latency: 1.981824ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T19:03:42Z" kind: List metadata: resourceVersion: ""