apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T15:53:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-198-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-198.ec2.internal uid: 9133e2c7-299f-4b4c-9057-54a9fba59bd8 resourceVersion: "54546" uid: 2fb972c0-068e-47c7-93b4-d92db5fee2c3 spec: sourcePod: network-check-source-989f8b8dc-c46mt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T16:00:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.436325ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:28:59Z" - latency: 823.865µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:27:59Z" - latency: 1.018008ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:26:59Z" - latency: 1.068073ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:25:59Z" - latency: 999.218µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:24:59Z" - latency: 1.396014ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:23:59Z" - latency: 1.147939ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:22:59Z" - latency: 1.005955ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:21:59Z" - latency: 973.893µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:20:59Z" - latency: 1.172476ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:19:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T15:53:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-198-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-198.ec2.internal uid: 9133e2c7-299f-4b4c-9057-54a9fba59bd8 resourceVersion: "55525" uid: 52056901-2f57-4ea6-9f2c-39798adb8475 spec: sourcePod: network-check-source-989f8b8dc-c46mt targetEndpoint: a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T15:59:59Z" message: 'load-balancer-api-external: tcp connection to a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.527009ms message: 'load-balancer-api-external: tcp connection to a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:29:59Z" - latency: 6.610461ms message: 'load-balancer-api-external: resolved host name a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:29:59Z" - latency: 3.272404ms message: 'load-balancer-api-external: tcp connection to a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:28:59Z" - latency: 6.276383ms message: 'load-balancer-api-external: resolved host name a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:28:59Z" - latency: 3.801678ms message: 'load-balancer-api-external: tcp connection to a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:27:59Z" - latency: 7.390777ms message: 'load-balancer-api-external: resolved host name a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:27:59Z" - latency: 3.58426ms message: 'load-balancer-api-external: tcp connection to a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:26:59Z" - latency: 6.319525ms message: 'load-balancer-api-external: resolved host name a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:26:59Z" - latency: 5.166457ms message: 'load-balancer-api-external: tcp connection to a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:25:59Z" - latency: 7.498595ms message: 'load-balancer-api-external: resolved host name a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:25:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T15:53:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-198-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-198.ec2.internal uid: 9133e2c7-299f-4b4c-9057-54a9fba59bd8 resourceVersion: "55524" uid: 866bc981-265e-4222-8d7c-efd1cc950869 spec: sourcePod: network-check-source-989f8b8dc-c46mt targetEndpoint: a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T15:59:59Z" message: 'load-balancer-api-internal: tcp connection to a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.696114ms message: 'load-balancer-api-internal: tcp connection to a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:29:59Z" - latency: 6.628364ms message: 'load-balancer-api-internal: resolved host name a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:29:59Z" - latency: 3.172504ms message: 'load-balancer-api-internal: tcp connection to a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:28:59Z" - latency: 6.35865ms message: 'load-balancer-api-internal: resolved host name a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:28:59Z" - latency: 4.276966ms message: 'load-balancer-api-internal: tcp connection to a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:27:59Z" - latency: 7.427519ms message: 'load-balancer-api-internal: resolved host name a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:27:59Z" - latency: 4.687558ms message: 'load-balancer-api-internal: tcp connection to a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:26:59Z" - latency: 6.245682ms message: 'load-balancer-api-internal: resolved host name a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:26:59Z" - latency: 6.362023ms message: 'load-balancer-api-internal: tcp connection to a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:25:59Z" - latency: 7.47126ms message: 'load-balancer-api-internal: resolved host name a96876cdcc6d441fbb5d4ef7aeaf88f4-3387a15c5f8563b3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T16:25:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T15:53:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-198-to-network-check-target-ip-10-0-131-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-198.ec2.internal uid: 9133e2c7-299f-4b4c-9057-54a9fba59bd8 resourceVersion: "54544" uid: c321a685-e75a-4640-b6f7-b4ae96abe4d4 spec: sourcePod: network-check-source-989f8b8dc-c46mt targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:00:59Z" message: 'network-check-target-ip-10-0-131-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.95935ms message: 'network-check-target-ip-10-0-131-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:28:59Z" - latency: 1.971807ms message: 'network-check-target-ip-10-0-131-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:27:59Z" - latency: 2.142966ms message: 'network-check-target-ip-10-0-131-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:26:59Z" - latency: 1.837299ms message: 'network-check-target-ip-10-0-131-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:25:59Z" - latency: 1.976133ms message: 'network-check-target-ip-10-0-131-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:24:59Z" - latency: 1.986799ms message: 'network-check-target-ip-10-0-131-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:23:59Z" - latency: 1.800712ms message: 'network-check-target-ip-10-0-131-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:22:59Z" - latency: 2.164611ms message: 'network-check-target-ip-10-0-131-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:21:59Z" - latency: 2.097341ms message: 'network-check-target-ip-10-0-131-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:20:59Z" - latency: 1.960872ms message: 'network-check-target-ip-10-0-131-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:19:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T15:53:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-198-to-network-check-target-ip-10-0-132-153 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-198.ec2.internal uid: 9133e2c7-299f-4b4c-9057-54a9fba59bd8 resourceVersion: "54545" uid: 274e6ffc-30d6-4a22-b6e0-5e842537374e spec: sourcePod: network-check-source-989f8b8dc-c46mt targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:00:59Z" message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.141248ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:28:59Z" - latency: 2.128828ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:27:59Z" - latency: 1.99173ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:26:59Z" - latency: 2.199299ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:25:59Z" - latency: 2.085246ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:24:59Z" - latency: 1.738429ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:23:59Z" - latency: 2.292043ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:22:59Z" - latency: 2.193156ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:21:59Z" - latency: 2.075557ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:20:59Z" - latency: 2.189264ms message: 'network-check-target-ip-10-0-132-153: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:19:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T15:53:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-198-to-network-check-target-ip-10-0-136-198 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-198.ec2.internal uid: 9133e2c7-299f-4b4c-9057-54a9fba59bd8 resourceVersion: "54543" uid: b7e7cc3c-a82a-4a36-a2be-b0e8e99d78dd spec: sourcePod: network-check-source-989f8b8dc-c46mt targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T16:00:59Z" message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.075341ms message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:28:59Z" - latency: 1.095837ms message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:27:59Z" - latency: 878.727µs message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:26:59Z" - latency: 1.687335ms message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:25:59Z" - latency: 1.689683ms message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:24:59Z" - latency: 1.599669ms message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:23:59Z" - latency: 1.342548ms message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:22:59Z" - latency: 1.36297ms message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:21:59Z" - latency: 845.812µs message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:20:59Z" - latency: 978.807µs message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:19:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T15:53:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-198-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-198.ec2.internal uid: 9133e2c7-299f-4b4c-9057-54a9fba59bd8 resourceVersion: "55523" uid: 7e1cccb2-6922-40a3-b026-ade198e50e5e spec: sourcePod: network-check-source-989f8b8dc-c46mt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T15:59:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.4571ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:29:59Z" - latency: 1.872087ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:29:59Z" - latency: 960.85µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:28:59Z" - latency: 1.763466ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:28:59Z" - latency: 899.766µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:27:59Z" - latency: 1.917205ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:27:59Z" - latency: 1.004271ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:26:59Z" - latency: 1.70721ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:26:59Z" - latency: 899.582µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T16:25:59Z" - latency: 2.367729ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T16:25:59Z" kind: List metadata: resourceVersion: ""