apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T11:39:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-249-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-249.ec2.internal uid: a5d42c79-2c23-4b34-b5e3-4d5765de6c12 resourceVersion: "16882" uid: 0c42d7d1-9dfe-4cb1-9ab5-4f49e9a7ba8a spec: sourcePod: network-check-source-7d88cb55d8-8kd2x targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T11:46:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.374524ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:53:27Z" - latency: 1.543415ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:52:27Z" - latency: 923.84µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:51:27Z" - latency: 974.77µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:50:27Z" - latency: 1.161997ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:49:27Z" - latency: 967.099µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:48:27Z" - latency: 977.188µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:47:27Z" - latency: 1.440601ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:46:27Z" - latency: 956.634µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:45:27Z" - latency: 1.055808ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:44:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T11:39:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-249-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-249.ec2.internal uid: a5d42c79-2c23-4b34-b5e3-4d5765de6c12 resourceVersion: "16060" uid: f9953f6d-f121-438e-a34e-c9042bafe9f8 spec: sourcePod: network-check-source-7d88cb55d8-8kd2x targetEndpoint: a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T11:45:27Z" message: 'load-balancer-api-external: tcp connection to a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.545374ms message: 'load-balancer-api-external: tcp connection to a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:51:27Z" - latency: 7.827481ms message: 'load-balancer-api-external: resolved host name a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:51:27Z" - latency: 4.791976ms message: 'load-balancer-api-external: tcp connection to a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:50:27Z" - latency: 8.227119ms message: 'load-balancer-api-external: resolved host name a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:50:27Z" - latency: 4.97358ms message: 'load-balancer-api-external: tcp connection to a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:49:27Z" - latency: 8.326049ms message: 'load-balancer-api-external: resolved host name a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:49:27Z" - latency: 4.932422ms message: 'load-balancer-api-external: tcp connection to a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:48:27Z" - latency: 9.009267ms message: 'load-balancer-api-external: resolved host name a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:48:27Z" - latency: 4.501426ms message: 'load-balancer-api-external: tcp connection to a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:47:27Z" - latency: 7.991222ms message: 'load-balancer-api-external: resolved host name a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:47:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T11:39:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-249-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-249.ec2.internal uid: a5d42c79-2c23-4b34-b5e3-4d5765de6c12 resourceVersion: "16061" uid: b5b1e722-b674-4283-88f0-4dbb818354ee spec: sourcePod: network-check-source-7d88cb55d8-8kd2x targetEndpoint: a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T11:45:27Z" message: 'load-balancer-api-internal: tcp connection to a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.989533ms message: 'load-balancer-api-internal: tcp connection to a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:51:27Z" - latency: 7.856686ms message: 'load-balancer-api-internal: resolved host name a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:51:27Z" - latency: 5.036492ms message: 'load-balancer-api-internal: tcp connection to a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:50:27Z" - latency: 8.160559ms message: 'load-balancer-api-internal: resolved host name a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:50:27Z" - latency: 4.94525ms message: 'load-balancer-api-internal: tcp connection to a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:49:27Z" - latency: 8.427746ms message: 'load-balancer-api-internal: resolved host name a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:49:27Z" - latency: 4.903998ms message: 'load-balancer-api-internal: tcp connection to a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:48:27Z" - latency: 8.919159ms message: 'load-balancer-api-internal: resolved host name a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:48:27Z" - latency: 5.176336ms message: 'load-balancer-api-internal: tcp connection to a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:47:27Z" - latency: 8.085116ms message: 'load-balancer-api-internal: resolved host name a1598d48dc67d49de8f6bbb5f4447cea-aaf81f9236cc9410.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T11:47:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T11:39:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-249-to-network-check-target-ip-10-0-128-89 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-249.ec2.internal uid: a5d42c79-2c23-4b34-b5e3-4d5765de6c12 resourceVersion: "16881" uid: 7af37cef-b207-4264-bed1-d02f17a1e340 spec: sourcePod: network-check-source-7d88cb55d8-8kd2x targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T11:46:27Z" message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.777646ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:53:27Z" - latency: 2.328691ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:52:27Z" - latency: 1.787135ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:51:27Z" - latency: 2.199804ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:50:27Z" - latency: 2.160698ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:49:27Z" - latency: 2.223558ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:48:27Z" - latency: 2.111947ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:47:27Z" - latency: 2.337431ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:46:27Z" - latency: 2.513118ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:45:27Z" - latency: 2.120517ms message: 'network-check-target-ip-10-0-128-89: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:44:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T11:39:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-249-to-network-check-target-ip-10-0-132-238 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-249.ec2.internal uid: a5d42c79-2c23-4b34-b5e3-4d5765de6c12 resourceVersion: "16879" uid: b5ddfa72-db82-42fd-ab61-506bae8cde4c spec: sourcePod: network-check-source-7d88cb55d8-8kd2x targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T11:46:27Z" message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.139403ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:53:27Z" - latency: 1.980683ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:52:27Z" - latency: 1.801797ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:51:27Z" - latency: 1.822194ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:50:27Z" - latency: 1.931708ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:49:27Z" - latency: 1.824166ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:48:27Z" - latency: 1.822203ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:47:27Z" - latency: 1.866955ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:46:27Z" - latency: 2.228114ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:45:27Z" - latency: 1.928523ms message: 'network-check-target-ip-10-0-132-238: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:44:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T11:39:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-249-to-network-check-target-ip-10-0-139-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-249.ec2.internal uid: a5d42c79-2c23-4b34-b5e3-4d5765de6c12 resourceVersion: "16880" uid: 8e1740ad-e76e-4b07-b640-a4738b8c0634 spec: sourcePod: network-check-source-7d88cb55d8-8kd2x targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T11:46:27Z" message: 'network-check-target-ip-10-0-139-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 896.359µs message: 'network-check-target-ip-10-0-139-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:53:27Z" - latency: 927.059µs message: 'network-check-target-ip-10-0-139-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:52:27Z" - latency: 834.674µs message: 'network-check-target-ip-10-0-139-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:51:27Z" - latency: 802.818µs message: 'network-check-target-ip-10-0-139-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:50:27Z" - latency: 849.352µs message: 'network-check-target-ip-10-0-139-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:49:27Z" - latency: 978.408µs message: 'network-check-target-ip-10-0-139-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:48:27Z" - latency: 881.292µs message: 'network-check-target-ip-10-0-139-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:47:27Z" - latency: 1.522395ms message: 'network-check-target-ip-10-0-139-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:46:27Z" - latency: 902.363µs message: 'network-check-target-ip-10-0-139-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:45:27Z" - latency: 855.497µs message: 'network-check-target-ip-10-0-139-249: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:44:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T11:39:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-249-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-249.ec2.internal uid: a5d42c79-2c23-4b34-b5e3-4d5765de6c12 resourceVersion: "16059" uid: e18c0eb3-926f-4d07-8761-c79eb8918f01 spec: sourcePod: network-check-source-7d88cb55d8-8kd2x targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T11:45:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 857.695µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:51:27Z" - latency: 1.69554ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T11:51:27Z" - latency: 722.221µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:50:27Z" - latency: 1.53746ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T11:50:27Z" - latency: 857.595µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:49:27Z" - latency: 1.837245ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T11:49:27Z" - latency: 784.618µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:48:27Z" - latency: 1.695881ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T11:48:27Z" - latency: 843.47µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T11:47:27Z" - latency: 1.657463ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T11:47:27Z" kind: List metadata: resourceVersion: ""