apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T16:48:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-153-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-153.ec2.internal uid: 655d95c4-bff2-40a0-90ab-e8c430b197b0 resourceVersion: "147632" uid: d380c2fe-22cc-41d6-bc59-deb6e63897b5 spec: sourcePod: network-check-source-6f78d59f99-jdsr5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T16:55:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.684429ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:51:28Z" - latency: 1.213664ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:50:28Z" - latency: 1.024441ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:49:28Z" - latency: 911.527µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:48:28Z" - latency: 972.145µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:47:28Z" - latency: 1.076648ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:46:28Z" - latency: 1.35519ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:45:28Z" - latency: 1.064138ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:44:28Z" - latency: 7.188179ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:43:28Z" - latency: 1.017892ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:42:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T16:48:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-153-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-153.ec2.internal uid: 655d95c4-bff2-40a0-90ab-e8c430b197b0 resourceVersion: "150654" uid: 603806f1-6a92-4377-a476-56a13ec4ff3f spec: sourcePod: network-check-source-6f78d59f99-jdsr5 targetEndpoint: a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T16:54:28Z" message: 'load-balancer-api-external: tcp connection to a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.074515ms message: 'load-balancer-api-external: tcp connection to a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:54:28Z" - latency: 9.700944ms message: 'load-balancer-api-external: resolved host name a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T17:54:28Z" - latency: 18.597131ms message: 'load-balancer-api-external: tcp connection to a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:53:28Z" - latency: 15.288699ms message: 'load-balancer-api-external: resolved host name a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T17:53:28Z" - latency: 19.361643ms message: 'load-balancer-api-external: tcp connection to a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:52:28Z" - latency: 11.979038ms message: 'load-balancer-api-external: resolved host name a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T17:52:28Z" - latency: 15.90149ms message: 'load-balancer-api-external: tcp connection to a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:51:28Z" - latency: 8.792786ms message: 'load-balancer-api-external: resolved host name a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T17:51:28Z" - latency: 19.39483ms message: 'load-balancer-api-external: tcp connection to a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:50:28Z" - latency: 7.296782ms message: 'load-balancer-api-external: resolved host name a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T17:50:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T16:48:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-153-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-153.ec2.internal uid: 655d95c4-bff2-40a0-90ab-e8c430b197b0 resourceVersion: "150653" uid: 098e0715-b1c8-4b42-93ed-e369c2db3d9c spec: sourcePod: network-check-source-6f78d59f99-jdsr5 targetEndpoint: a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T16:54:28Z" message: 'load-balancer-api-internal: tcp connection to a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 16.021536ms message: 'load-balancer-api-internal: tcp connection to a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:54:28Z" - latency: 9.752677ms message: 'load-balancer-api-internal: resolved host name a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T17:54:28Z" - latency: 18.091743ms message: 'load-balancer-api-internal: tcp connection to a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:53:28Z" - latency: 14.788078ms message: 'load-balancer-api-internal: resolved host name a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T17:53:28Z" - latency: 18.316739ms message: 'load-balancer-api-internal: tcp connection to a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:52:28Z" - latency: 12.724203ms message: 'load-balancer-api-internal: resolved host name a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T17:52:28Z" - latency: 16.269295ms message: 'load-balancer-api-internal: tcp connection to a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:51:28Z" - latency: 8.692244ms message: 'load-balancer-api-internal: resolved host name a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T17:51:28Z" - latency: 18.998667ms message: 'load-balancer-api-internal: tcp connection to a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:50:28Z" - latency: 7.217456ms message: 'load-balancer-api-internal: resolved host name a659c68b8ac284c288fcb210a4a2399f-3aaf74cda8b6e1da.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T17:50:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T16:48:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-153-to-network-check-target-ip-10-0-128-218 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-153.ec2.internal uid: 655d95c4-bff2-40a0-90ab-e8c430b197b0 resourceVersion: "147631" uid: 2606f68f-14f6-4165-ba49-d092c8f45c05 spec: sourcePod: network-check-source-6f78d59f99-jdsr5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T16:55:28Z" message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.89142ms message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:51:28Z" - latency: 2.371099ms message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:50:28Z" - latency: 2.108208ms message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:49:28Z" - latency: 2.254876ms message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:48:28Z" - latency: 1.954598ms message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:47:28Z" - latency: 2.689881ms message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:46:28Z" - latency: 2.197348ms message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:45:28Z" - latency: 2.64448ms message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:44:28Z" - latency: 11.097178ms message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:43:28Z" - latency: 2.439945ms message: 'network-check-target-ip-10-0-128-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:42:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T16:48:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-153-to-network-check-target-ip-10-0-131-13 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-153.ec2.internal uid: 655d95c4-bff2-40a0-90ab-e8c430b197b0 resourceVersion: "147630" uid: 7ab562a3-4010-4ec1-9bb1-65d252573af1 spec: sourcePod: network-check-source-6f78d59f99-jdsr5 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T16:55:28Z" message: 'network-check-target-ip-10-0-131-13: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.563428ms message: 'network-check-target-ip-10-0-131-13: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:51:28Z" - latency: 2.004673ms message: 'network-check-target-ip-10-0-131-13: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:50:28Z" - latency: 1.984229ms message: 'network-check-target-ip-10-0-131-13: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:49:28Z" - latency: 2.297433ms message: 'network-check-target-ip-10-0-131-13: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:48:28Z" - latency: 2.071984ms message: 'network-check-target-ip-10-0-131-13: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:47:28Z" - latency: 2.233261ms message: 'network-check-target-ip-10-0-131-13: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:46:28Z" - latency: 2.24337ms message: 'network-check-target-ip-10-0-131-13: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:45:28Z" - latency: 2.271786ms message: 'network-check-target-ip-10-0-131-13: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:44:28Z" - latency: 17.162852ms message: 'network-check-target-ip-10-0-131-13: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:43:28Z" - latency: 2.041768ms message: 'network-check-target-ip-10-0-131-13: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:42:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T16:48:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-153-to-network-check-target-ip-10-0-135-153 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-153.ec2.internal uid: 655d95c4-bff2-40a0-90ab-e8c430b197b0 resourceVersion: "147629" uid: 0a5231fa-725b-49b1-b592-ead69996c937 spec: sourcePod: network-check-source-6f78d59f99-jdsr5 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T16:55:28Z" message: 'network-check-target-ip-10-0-135-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.331368ms message: 'network-check-target-ip-10-0-135-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:51:28Z" - latency: 1.350954ms message: 'network-check-target-ip-10-0-135-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:50:28Z" - latency: 1.019395ms message: 'network-check-target-ip-10-0-135-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:49:28Z" - latency: 1.373323ms message: 'network-check-target-ip-10-0-135-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:48:28Z" - latency: 1.080417ms message: 'network-check-target-ip-10-0-135-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:47:28Z" - latency: 1.536855ms message: 'network-check-target-ip-10-0-135-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:46:28Z" - latency: 1.025267ms message: 'network-check-target-ip-10-0-135-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:45:28Z" - latency: 1.677237ms message: 'network-check-target-ip-10-0-135-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:44:28Z" - latency: 8.708144ms message: 'network-check-target-ip-10-0-135-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:43:28Z" - latency: 1.078959ms message: 'network-check-target-ip-10-0-135-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:42:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T16:48:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-153-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-153.ec2.internal uid: 655d95c4-bff2-40a0-90ab-e8c430b197b0 resourceVersion: "150650" uid: 8a0063a1-68c5-4940-8c56-a91d4d5a02b2 spec: sourcePod: network-check-source-6f78d59f99-jdsr5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T16:54:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.260293ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:54:28Z" - latency: 1.952576ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T17:54:28Z" - latency: 1.497958ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:53:28Z" - latency: 4.12325ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T17:53:28Z" - latency: 2.400396ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:52:28Z" - latency: 4.057184ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T17:52:28Z" - latency: 1.106361ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:51:28Z" - latency: 2.194132ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T17:51:28Z" - latency: 1.161068ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T17:50:28Z" - latency: 2.093299ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T17:50:28Z" kind: List metadata: resourceVersion: ""