apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:40:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-135-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-135.ec2.internal uid: 96cd0c27-6f7d-4ecb-b46e-17051f0c8380 resourceVersion: "15176" uid: aa9171fd-e930-4445-9c43-e204641892f1 spec: sourcePod: network-check-source-7d88cb55d8-kl2tw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T18:47:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 923.034µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:47:55Z" - latency: 754.987µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:46:55Z" - latency: 1.020967ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:45:55Z" - latency: 984.823µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:44:55Z" - latency: 984.275µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:43:55Z" - latency: 1.237723ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:42:55Z" - latency: 911.343µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:41:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:40:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-135-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-135.ec2.internal uid: 96cd0c27-6f7d-4ecb-b46e-17051f0c8380 resourceVersion: "16907" uid: b5c8b781-bc3a-4630-8721-895d3ac2ea43 spec: sourcePod: network-check-source-7d88cb55d8-kl2tw targetEndpoint: a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T18:46:55Z" message: 'load-balancer-api-external: tcp connection to a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.410678ms message: 'load-balancer-api-external: tcp connection to a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:52:55Z" - latency: 7.894462ms message: 'load-balancer-api-external: resolved host name a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:52:55Z" - latency: 4.405048ms message: 'load-balancer-api-external: tcp connection to a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:51:55Z" - latency: 8.713498ms message: 'load-balancer-api-external: resolved host name a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:51:55Z" - latency: 5.062356ms message: 'load-balancer-api-external: tcp connection to a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:50:55Z" - latency: 7.677165ms message: 'load-balancer-api-external: resolved host name a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:50:55Z" - latency: 4.775185ms message: 'load-balancer-api-external: tcp connection to a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:49:55Z" - latency: 8.099691ms message: 'load-balancer-api-external: resolved host name a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:49:55Z" - latency: 4.884892ms message: 'load-balancer-api-external: tcp connection to a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:48:55Z" - latency: 8.263211ms message: 'load-balancer-api-external: resolved host name a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:48:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:40:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-135-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-135.ec2.internal uid: 96cd0c27-6f7d-4ecb-b46e-17051f0c8380 resourceVersion: "16906" uid: 24189ac2-9337-4081-a7c7-d4b26030a6a6 spec: sourcePod: network-check-source-7d88cb55d8-kl2tw targetEndpoint: a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T18:46:55Z" message: 'load-balancer-api-internal: tcp connection to a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.760926ms message: 'load-balancer-api-internal: tcp connection to a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:52:55Z" - latency: 8.014879ms message: 'load-balancer-api-internal: resolved host name a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:52:55Z" - latency: 4.396895ms message: 'load-balancer-api-internal: tcp connection to a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:51:55Z" - latency: 8.788131ms message: 'load-balancer-api-internal: resolved host name a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:51:55Z" - latency: 4.798643ms message: 'load-balancer-api-internal: tcp connection to a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:50:55Z" - latency: 7.599733ms message: 'load-balancer-api-internal: resolved host name a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:50:55Z" - latency: 3.990523ms message: 'load-balancer-api-internal: tcp connection to a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:49:55Z" - latency: 8.177982ms message: 'load-balancer-api-internal: resolved host name a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:49:55Z" - latency: 4.8995ms message: 'load-balancer-api-internal: tcp connection to a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:48:55Z" - latency: 8.335101ms message: 'load-balancer-api-internal: resolved host name a5023d8d1ff0a4cd09e37d39d9cc9de2-dd81c24cb86cb1e6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T18:48:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:40:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-135-to-network-check-target-ip-10-0-132-135 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-135.ec2.internal uid: 96cd0c27-6f7d-4ecb-b46e-17051f0c8380 resourceVersion: "15174" uid: d906024e-dbd4-474b-9906-d1acbabc29c9 spec: sourcePod: network-check-source-7d88cb55d8-kl2tw targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T18:47:55Z" message: 'network-check-target-ip-10-0-132-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 834.996µs message: 'network-check-target-ip-10-0-132-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:47:55Z" - latency: 1.417303ms message: 'network-check-target-ip-10-0-132-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:46:55Z" - latency: 776.271µs message: 'network-check-target-ip-10-0-132-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:45:55Z" - latency: 991.502µs message: 'network-check-target-ip-10-0-132-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:44:55Z" - latency: 865.151µs message: 'network-check-target-ip-10-0-132-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:43:55Z" - latency: 1.301861ms message: 'network-check-target-ip-10-0-132-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:42:55Z" - latency: 1.150638ms message: 'network-check-target-ip-10-0-132-135: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:41:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:40:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-135-to-network-check-target-ip-10-0-139-60 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-135.ec2.internal uid: 96cd0c27-6f7d-4ecb-b46e-17051f0c8380 resourceVersion: "15173" uid: e37baf11-0220-4ffd-9e42-ad2fb63d3327 spec: sourcePod: network-check-source-7d88cb55d8-kl2tw targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T18:47:55Z" message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.039073ms message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:47:55Z" - latency: 2.000713ms message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:46:55Z" - latency: 2.135698ms message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:45:55Z" - latency: 2.211334ms message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:44:55Z" - latency: 2.22197ms message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:43:55Z" - latency: 5.923848ms message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:42:55Z" - latency: 2.05199ms message: 'network-check-target-ip-10-0-139-60: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:41:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:40:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-135-to-network-check-target-ip-10-0-141-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-135.ec2.internal uid: 96cd0c27-6f7d-4ecb-b46e-17051f0c8380 resourceVersion: "15175" uid: 56d51e99-13e8-4b03-93a7-3dffb6db5fc8 spec: sourcePod: network-check-source-7d88cb55d8-kl2tw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T18:47:55Z" message: 'network-check-target-ip-10-0-141-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.232907ms message: 'network-check-target-ip-10-0-141-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:47:55Z" - latency: 2.135667ms message: 'network-check-target-ip-10-0-141-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:46:55Z" - latency: 2.253283ms message: 'network-check-target-ip-10-0-141-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:45:55Z" - latency: 2.488245ms message: 'network-check-target-ip-10-0-141-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:44:55Z" - latency: 2.554921ms message: 'network-check-target-ip-10-0-141-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:43:55Z" - latency: 2.971979ms message: 'network-check-target-ip-10-0-141-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:42:55Z" - latency: 2.418731ms message: 'network-check-target-ip-10-0-141-242: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:41:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T18:40:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-135-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-135.ec2.internal uid: 96cd0c27-6f7d-4ecb-b46e-17051f0c8380 resourceVersion: "16905" uid: b7cdd290-f5ab-4415-8322-90d24dc63f34 spec: sourcePod: network-check-source-7d88cb55d8-kl2tw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T18:46:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 776.016µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:52:55Z" - latency: 1.573846ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T18:52:55Z" - latency: 1.013188ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:51:55Z" - latency: 1.93037ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T18:51:55Z" - latency: 1.005613ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:50:55Z" - latency: 1.666929ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T18:50:55Z" - latency: 875.098µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:49:55Z" - latency: 1.565189ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T18:49:55Z" - latency: 757.425µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T18:48:55Z" - latency: 1.796502ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T18:48:55Z" kind: List metadata: resourceVersion: ""