apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T13:21:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-86-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-86.ec2.internal uid: 9fbbf691-2f7e-40df-8d97-ee68a3bf9a3f resourceVersion: "24095" uid: d52743a6-2179-4725-ab9d-029cd8597fe5 spec: sourcePod: network-check-source-685456655f-dwf8v targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-08T13:28:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.441929ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:42:33Z" - latency: 1.038508ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:41:33Z" - latency: 811.675µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:40:33Z" - latency: 1.088619ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:39:33Z" - latency: 1.011246ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:38:33Z" - latency: 1.157105ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:37:33Z" - latency: 1.211687ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:36:33Z" - latency: 955.569µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:35:33Z" - latency: 1.460804ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:34:33Z" - latency: 1.122023ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:33:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T13:21:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-86-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-86.ec2.internal uid: 9fbbf691-2f7e-40df-8d97-ee68a3bf9a3f resourceVersion: "25894" uid: c1d6d6e9-f358-4c34-81af-a0d60e084f89 spec: sourcePod: network-check-source-685456655f-dwf8v targetEndpoint: a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T13:27:33Z" message: 'load-balancer-api-external: tcp connection to a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.097913ms message: 'load-balancer-api-external: tcp connection to a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:45:33Z" - latency: 8.757541ms message: 'load-balancer-api-external: resolved host name a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T13:45:33Z" - latency: 5.378012ms message: 'load-balancer-api-external: tcp connection to a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:44:33Z" - latency: 9.436415ms message: 'load-balancer-api-external: resolved host name a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T13:44:33Z" - latency: 5.026581ms message: 'load-balancer-api-external: tcp connection to a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:43:33Z" - latency: 5.955364ms message: 'load-balancer-api-external: resolved host name a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T13:43:33Z" - latency: 4.998224ms message: 'load-balancer-api-external: tcp connection to a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:42:33Z" - latency: 7.917522ms message: 'load-balancer-api-external: resolved host name a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T13:42:33Z" - latency: 6.859136ms message: 'load-balancer-api-external: tcp connection to a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:41:33Z" - latency: 8.806563ms message: 'load-balancer-api-external: resolved host name a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T13:41:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T13:21:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-86-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-86.ec2.internal uid: 9fbbf691-2f7e-40df-8d97-ee68a3bf9a3f resourceVersion: "25893" uid: 4535b397-6021-4e9e-8576-348af1f9b71c spec: sourcePod: network-check-source-685456655f-dwf8v targetEndpoint: a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T13:27:33Z" message: 'load-balancer-api-internal: tcp connection to a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.716316ms message: 'load-balancer-api-internal: tcp connection to a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:45:33Z" - latency: 8.691743ms message: 'load-balancer-api-internal: resolved host name a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T13:45:33Z" - latency: 5.84367ms message: 'load-balancer-api-internal: tcp connection to a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:44:33Z" - latency: 9.383102ms message: 'load-balancer-api-internal: resolved host name a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T13:44:33Z" - latency: 5.045326ms message: 'load-balancer-api-internal: tcp connection to a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:43:33Z" - latency: 5.898227ms message: 'load-balancer-api-internal: resolved host name a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T13:43:33Z" - latency: 4.252946ms message: 'load-balancer-api-internal: tcp connection to a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:42:33Z" - latency: 7.83965ms message: 'load-balancer-api-internal: resolved host name a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T13:42:33Z" - latency: 5.575459ms message: 'load-balancer-api-internal: tcp connection to a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:41:33Z" - latency: 8.763762ms message: 'load-balancer-api-internal: resolved host name a7c9d6921526a4d16898b501924949d7-b198e2db0066ba86.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T13:41:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T13:21:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-86-to-network-check-target-ip-10-0-134-224 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-86.ec2.internal uid: 9fbbf691-2f7e-40df-8d97-ee68a3bf9a3f resourceVersion: "24094" uid: 7eadef9d-e80b-4bf9-8bb7-9d3da047dc4e spec: sourcePod: network-check-source-685456655f-dwf8v targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-08T13:28:33Z" message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.498494ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:42:33Z" - latency: 2.381429ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:41:33Z" - latency: 2.233908ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:40:33Z" - latency: 2.453525ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:39:33Z" - latency: 2.428346ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:38:33Z" - latency: 2.507715ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:37:33Z" - latency: 2.417198ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:36:33Z" - latency: 2.317525ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:35:33Z" - latency: 2.366666ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:34:33Z" - latency: 2.512532ms message: 'network-check-target-ip-10-0-134-224: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:33:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T13:21:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-86-to-network-check-target-ip-10-0-136-211 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-86.ec2.internal uid: 9fbbf691-2f7e-40df-8d97-ee68a3bf9a3f resourceVersion: "24093" uid: 1b555396-0fb8-4d54-bce0-307ee4cfe854 spec: sourcePod: network-check-source-685456655f-dwf8v targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-08T13:28:33Z" message: 'network-check-target-ip-10-0-136-211: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.179455ms message: 'network-check-target-ip-10-0-136-211: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:42:33Z" - latency: 2.526164ms message: 'network-check-target-ip-10-0-136-211: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:41:33Z" - latency: 2.227074ms message: 'network-check-target-ip-10-0-136-211: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:40:33Z" - latency: 2.360032ms message: 'network-check-target-ip-10-0-136-211: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:39:33Z" - latency: 2.408016ms message: 'network-check-target-ip-10-0-136-211: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:38:33Z" - latency: 2.370058ms message: 'network-check-target-ip-10-0-136-211: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:37:33Z" - latency: 2.423054ms message: 'network-check-target-ip-10-0-136-211: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:36:33Z" - latency: 2.286274ms message: 'network-check-target-ip-10-0-136-211: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:35:33Z" - latency: 2.43415ms message: 'network-check-target-ip-10-0-136-211: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:34:33Z" - latency: 2.362898ms message: 'network-check-target-ip-10-0-136-211: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:33:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T13:21:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-86-to-network-check-target-ip-10-0-142-86 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-86.ec2.internal uid: 9fbbf691-2f7e-40df-8d97-ee68a3bf9a3f resourceVersion: "24092" uid: 23f0734e-0e8e-4799-b210-df887554e48c spec: sourcePod: network-check-source-685456655f-dwf8v targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-08T13:28:33Z" message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 932.39µs message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:42:33Z" - latency: 1.019342ms message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:41:33Z" - latency: 855.424µs message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:40:33Z" - latency: 1.098767ms message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:39:33Z" - latency: 1.022084ms message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:38:33Z" - latency: 1.022698ms message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:37:33Z" - latency: 1.007092ms message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:36:33Z" - latency: 931.658µs message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:35:33Z" - latency: 936.228µs message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:34:33Z" - latency: 855.425µs message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:33:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T13:21:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-86-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-86.ec2.internal uid: 9fbbf691-2f7e-40df-8d97-ee68a3bf9a3f resourceVersion: "25892" uid: 7e73ad8b-f5dc-458e-841f-5af930a39922 spec: sourcePod: network-check-source-685456655f-dwf8v targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-08T13:27:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 901.062µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:45:33Z" - latency: 1.766208ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T13:45:33Z" - latency: 1.181512ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:44:33Z" - latency: 1.730101ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T13:44:33Z" - latency: 989.907µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:43:33Z" - latency: 1.76444ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T13:43:33Z" - latency: 1.307458ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:42:33Z" - latency: 2.10874ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T13:42:33Z" - latency: 924.221µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T13:41:33Z" - latency: 1.776752ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T13:41:33Z" kind: List metadata: resourceVersion: ""