apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T08:08:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-77-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-77.ec2.internal uid: 222ca782-5c98-4f88-aa19-c9f69ca795fc resourceVersion: "31541" uid: 06314e28-18e1-4749-b3da-374e0f645156 spec: sourcePod: network-check-source-dbd9cf844-mkztw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-07T08:15:01Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 986.16µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:22:01Z" - latency: 844.164µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:21:01Z" - latency: 1.062987ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:20:01Z" - latency: 1.071393ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:19:01Z" - latency: 884.105µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:18:01Z" - latency: 1.375231ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:17:01Z" - latency: 1.292731ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:16:01Z" - latency: 1.173154ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:15:01Z" - latency: 889.522µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:14:01Z" - latency: 1.097374ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:13:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T08:08:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-77-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-77.ec2.internal uid: 222ca782-5c98-4f88-aa19-c9f69ca795fc resourceVersion: "30009" uid: 76cef081-55e4-4ef9-8324-bed7d4fafc20 spec: sourcePod: network-check-source-dbd9cf844-mkztw targetEndpoint: a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-07T08:14:01Z" message: 'load-balancer-api-external: tcp connection to a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.595593ms message: 'load-balancer-api-external: tcp connection to a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:20:01Z" - latency: 8.697674ms message: 'load-balancer-api-external: resolved host name a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T08:20:01Z" - latency: 4.688781ms message: 'load-balancer-api-external: tcp connection to a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:19:01Z" - latency: 8.255507ms message: 'load-balancer-api-external: resolved host name a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T08:19:01Z" - latency: 4.739115ms message: 'load-balancer-api-external: tcp connection to a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:18:01Z" - latency: 8.477493ms message: 'load-balancer-api-external: resolved host name a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T08:18:01Z" - latency: 4.620485ms message: 'load-balancer-api-external: tcp connection to a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:17:01Z" - latency: 8.361037ms message: 'load-balancer-api-external: resolved host name a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T08:17:01Z" - latency: 5.265829ms message: 'load-balancer-api-external: tcp connection to a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:16:01Z" - latency: 8.364122ms message: 'load-balancer-api-external: resolved host name a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T08:16:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T08:08:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-77-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-77.ec2.internal uid: 222ca782-5c98-4f88-aa19-c9f69ca795fc resourceVersion: "30010" uid: a66ece6e-66ab-4e2d-ac0f-fba94d7f9ae1 spec: sourcePod: network-check-source-dbd9cf844-mkztw targetEndpoint: a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-07T08:14:01Z" message: 'load-balancer-api-internal: tcp connection to a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.564297ms message: 'load-balancer-api-internal: tcp connection to a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:20:01Z" - latency: 8.807346ms message: 'load-balancer-api-internal: resolved host name a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T08:20:01Z" - latency: 5.094533ms message: 'load-balancer-api-internal: tcp connection to a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:19:01Z" - latency: 8.168108ms message: 'load-balancer-api-internal: resolved host name a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T08:19:01Z" - latency: 4.728729ms message: 'load-balancer-api-internal: tcp connection to a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:18:01Z" - latency: 8.522562ms message: 'load-balancer-api-internal: resolved host name a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T08:18:01Z" - latency: 4.909988ms message: 'load-balancer-api-internal: tcp connection to a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:17:01Z" - latency: 8.346866ms message: 'load-balancer-api-internal: resolved host name a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T08:17:01Z" - latency: 5.241568ms message: 'load-balancer-api-internal: tcp connection to a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:16:01Z" - latency: 8.344163ms message: 'load-balancer-api-internal: resolved host name a9e751a98f7d4429ba051f0f9a1ebcaa-e0ed54d2a973fd18.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T08:16:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T08:08:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-77-to-network-check-target-ip-10-0-130-77 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-77.ec2.internal uid: 222ca782-5c98-4f88-aa19-c9f69ca795fc resourceVersion: "31538" uid: ff15dc28-3ef7-40c2-8a37-eeb4cc426450 spec: sourcePod: network-check-source-dbd9cf844-mkztw targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-07T08:15:01Z" message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.128285ms message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:22:01Z" - latency: 1.657579ms message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:21:01Z" - latency: 931.532µs message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:20:01Z" - latency: 936.156µs message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:19:01Z" - latency: 768.694µs message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:18:01Z" - latency: 901.511µs message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:17:01Z" - latency: 1.408932ms message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:16:01Z" - latency: 1.368135ms message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:15:01Z" - latency: 897.639µs message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:14:01Z" - latency: 956.326µs message: 'network-check-target-ip-10-0-130-77: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:13:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T08:08:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-77-to-network-check-target-ip-10-0-134-126 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-77.ec2.internal uid: 222ca782-5c98-4f88-aa19-c9f69ca795fc resourceVersion: "31540" uid: d2f9c6b5-6c2a-4ae2-b1da-d6e282c48fab spec: sourcePod: network-check-source-dbd9cf844-mkztw targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-07T08:15:01Z" message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.595629ms message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:22:01Z" - latency: 2.158575ms message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:21:01Z" - latency: 2.267826ms message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:20:01Z" - latency: 2.41218ms message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:19:01Z" - latency: 2.020351ms message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:18:01Z" - latency: 3.039715ms message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:17:01Z" - latency: 2.369811ms message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:16:01Z" - latency: 2.282988ms message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:15:01Z" - latency: 2.546635ms message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:14:01Z" - latency: 2.460574ms message: 'network-check-target-ip-10-0-134-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:13:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T08:08:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-77-to-network-check-target-ip-10-0-142-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-77.ec2.internal uid: 222ca782-5c98-4f88-aa19-c9f69ca795fc resourceVersion: "31539" uid: 7e9469de-ba8e-488a-bd9d-c524543b7aac spec: sourcePod: network-check-source-dbd9cf844-mkztw targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-07T08:15:01Z" message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.390348ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:22:01Z" - latency: 2.032283ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:21:01Z" - latency: 2.250563ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:20:01Z" - latency: 2.432024ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:19:01Z" - latency: 2.012785ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:18:01Z" - latency: 2.200173ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:17:01Z" - latency: 2.309717ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:16:01Z" - latency: 2.166736ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:15:01Z" - latency: 2.463849ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:14:01Z" - latency: 2.206173ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:13:01Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T08:08:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-77-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-77.ec2.internal uid: 222ca782-5c98-4f88-aa19-c9f69ca795fc resourceVersion: "30008" uid: 23026516-4cd7-4d85-81da-ea1bcd6d606d spec: sourcePod: network-check-source-dbd9cf844-mkztw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-07T08:14:01Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 887.662µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:20:01Z" - latency: 1.700362ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T08:20:01Z" - latency: 785.454µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:19:01Z" - latency: 1.755559ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T08:19:01Z" - latency: 751.682µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:18:01Z" - latency: 2.0543ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T08:18:01Z" - latency: 1.176547ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:17:01Z" - latency: 1.865735ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T08:17:01Z" - latency: 791.33µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T08:16:01Z" - latency: 1.673686ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T08:16:01Z" kind: List metadata: resourceVersion: ""