apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T10:15:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-129-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-129.ec2.internal uid: dfc5476b-d665-40b1-8780-2d75e1689484 resourceVersion: "19475" uid: f2981cbe-6b2c-4475-81a5-1286a3698d34 spec: sourcePod: network-check-source-6f8b768455-kczcs targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-17T10:22:20Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 818.264µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:36:20Z" - latency: 1.350822ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:35:20Z" - latency: 860µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:34:20Z" - latency: 909.788µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:33:20Z" - latency: 851.355µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:32:20Z" - latency: 719.542µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:31:20Z" - latency: 1.063354ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:30:20Z" - latency: 950.09µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:29:20Z" - latency: 948.407µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:28:20Z" - latency: 980.892µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:27:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T10:15:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-129-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-129.ec2.internal uid: dfc5476b-d665-40b1-8780-2d75e1689484 resourceVersion: "20826" uid: 26059cdd-4126-4583-aa09-de12969fd49e spec: sourcePod: network-check-source-6f8b768455-kczcs targetEndpoint: aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T10:21:20Z" message: 'load-balancer-api-external: tcp connection to aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.706454ms message: 'load-balancer-api-external: tcp connection to aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:39:20Z" - latency: 14.244902ms message: 'load-balancer-api-external: resolved host name aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T10:39:20Z" - latency: 4.461172ms message: 'load-balancer-api-external: tcp connection to aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:38:20Z" - latency: 6.582212ms message: 'load-balancer-api-external: resolved host name aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T10:38:20Z" - latency: 5.366812ms message: 'load-balancer-api-external: tcp connection to aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:37:20Z" - latency: 9.070226ms message: 'load-balancer-api-external: resolved host name aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T10:37:20Z" - latency: 5.287318ms message: 'load-balancer-api-external: tcp connection to aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:36:20Z" - latency: 9.765247ms message: 'load-balancer-api-external: resolved host name aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T10:36:20Z" - latency: 6.358639ms message: 'load-balancer-api-external: tcp connection to aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:35:20Z" - latency: 11.514142ms message: 'load-balancer-api-external: resolved host name aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T10:35:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T10:15:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-129-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-129.ec2.internal uid: dfc5476b-d665-40b1-8780-2d75e1689484 resourceVersion: "20827" uid: 1e730955-af26-4797-8e95-5dffbc2e681b spec: sourcePod: network-check-source-6f8b768455-kczcs targetEndpoint: aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-17T10:21:20Z" message: 'load-balancer-api-internal: tcp connection to aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.891782ms message: 'load-balancer-api-internal: tcp connection to aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:39:20Z" - latency: 14.290394ms message: 'load-balancer-api-internal: resolved host name aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T10:39:20Z" - latency: 5.426388ms message: 'load-balancer-api-internal: tcp connection to aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:38:20Z" - latency: 6.623946ms message: 'load-balancer-api-internal: resolved host name aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T10:38:20Z" - latency: 4.69588ms message: 'load-balancer-api-internal: tcp connection to aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:37:20Z" - latency: 9.139464ms message: 'load-balancer-api-internal: resolved host name aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T10:37:20Z" - latency: 4.821045ms message: 'load-balancer-api-internal: tcp connection to aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:36:20Z" - latency: 9.79553ms message: 'load-balancer-api-internal: resolved host name aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T10:36:20Z" - latency: 6.355444ms message: 'load-balancer-api-internal: tcp connection to aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:35:20Z" - latency: 11.564181ms message: 'load-balancer-api-internal: resolved host name aeae16352900743b78a839d1cfc0105a-b11298ca0ee262df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-17T10:35:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T10:15:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-129-to-network-check-target-ip-10-0-134-129 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-129.ec2.internal uid: dfc5476b-d665-40b1-8780-2d75e1689484 resourceVersion: "19472" uid: f942e255-78e1-47fd-bd8d-d08f0750d848 spec: sourcePod: network-check-source-6f8b768455-kczcs targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T10:22:20Z" message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 815.723µs message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:36:20Z" - latency: 1.148665ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:35:20Z" - latency: 1.35697ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:34:20Z" - latency: 914.107µs message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:33:20Z" - latency: 1.507281ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:32:20Z" - latency: 897.25µs message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:31:20Z" - latency: 911.019µs message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:30:20Z" - latency: 990.507µs message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:29:20Z" - latency: 902.629µs message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:28:20Z" - latency: 1.278441ms message: 'network-check-target-ip-10-0-134-129: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:27:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T10:15:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-129-to-network-check-target-ip-10-0-137-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-129.ec2.internal uid: dfc5476b-d665-40b1-8780-2d75e1689484 resourceVersion: "19474" uid: 2a40c76a-fad6-46e9-a9f7-a5e48d94da66 spec: sourcePod: network-check-source-6f8b768455-kczcs targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-17T10:22:20Z" message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.64511ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:36:20Z" - latency: 2.729577ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:35:20Z" - latency: 2.421715ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:34:20Z" - latency: 2.202935ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:33:20Z" - latency: 2.187993ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:32:20Z" - latency: 2.155608ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:31:20Z" - latency: 2.188679ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:30:20Z" - latency: 2.278872ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:29:20Z" - latency: 2.602722ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:28:20Z" - latency: 2.111529ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:27:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T10:15:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-129-to-network-check-target-ip-10-0-139-189 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-129.ec2.internal uid: dfc5476b-d665-40b1-8780-2d75e1689484 resourceVersion: "19473" uid: f0d04deb-9daa-4cbe-8064-e2216452b3a3 spec: sourcePod: network-check-source-6f8b768455-kczcs targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-17T10:22:20Z" message: 'network-check-target-ip-10-0-139-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.041547ms message: 'network-check-target-ip-10-0-139-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:36:20Z" - latency: 2.475109ms message: 'network-check-target-ip-10-0-139-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:35:20Z" - latency: 2.185271ms message: 'network-check-target-ip-10-0-139-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:34:20Z" - latency: 2.115406ms message: 'network-check-target-ip-10-0-139-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:33:20Z" - latency: 2.603004ms message: 'network-check-target-ip-10-0-139-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:32:20Z" - latency: 6.934348ms message: 'network-check-target-ip-10-0-139-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:31:20Z" - latency: 2.142482ms message: 'network-check-target-ip-10-0-139-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:30:20Z" - latency: 2.19895ms message: 'network-check-target-ip-10-0-139-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:29:20Z" - latency: 1.874773ms message: 'network-check-target-ip-10-0-139-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:28:20Z" - latency: 2.029556ms message: 'network-check-target-ip-10-0-139-189: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:27:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-17T10:15:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-129-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-129.ec2.internal uid: dfc5476b-d665-40b1-8780-2d75e1689484 resourceVersion: "20825" uid: a6118ab0-beeb-40a8-9afe-9db8cc10933e spec: sourcePod: network-check-source-6f8b768455-kczcs targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-17T10:21:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 895.507µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:39:20Z" - latency: 1.957699ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T10:39:20Z" - latency: 832.282µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:38:20Z" - latency: 1.659579ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T10:38:20Z" - latency: 948.998µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:37:20Z" - latency: 1.646068ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T10:37:20Z" - latency: 846.63µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:36:20Z" - latency: 2.036174ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T10:36:20Z" - latency: 966.339µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-17T10:35:20Z" - latency: 2.285404ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-17T10:35:20Z" kind: List metadata: resourceVersion: ""