apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T02:01:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-71-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-71.ec2.internal uid: b9f25ab3-4c04-479e-8b54-1d83610e4447 resourceVersion: "31728" uid: 7639b4b5-21e3-40f2-a24a-ab068c2d202d spec: sourcePod: network-check-source-56d84b9f44-ng2fv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T02:08:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.019053ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:15:25Z" - latency: 980.478µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:14:25Z" - latency: 1.069095ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:13:25Z" - latency: 1.03716ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:12:25Z" - latency: 1.493423ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:11:25Z" - latency: 1.161036ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:10:25Z" - latency: 874.216µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:09:25Z" - latency: 813.252µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:08:25Z" - latency: 995.017µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:07:25Z" - latency: 948.267µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:06:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T02:01:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-71-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-71.ec2.internal uid: b9f25ab3-4c04-479e-8b54-1d83610e4447 resourceVersion: "29701" uid: 7b5ef951-df1e-43f7-86f3-da08f8e4b30c spec: sourcePod: network-check-source-56d84b9f44-ng2fv targetEndpoint: ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T02:07:25Z" message: 'load-balancer-api-external: tcp connection to ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.19951ms message: 'load-balancer-api-external: tcp connection to ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:13:25Z" - latency: 12.009164ms message: 'load-balancer-api-external: resolved host name ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:13:25Z" - latency: 4.518925ms message: 'load-balancer-api-external: tcp connection to ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:12:25Z" - latency: 7.975921ms message: 'load-balancer-api-external: resolved host name ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:12:25Z" - latency: 4.229634ms message: 'load-balancer-api-external: tcp connection to ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:11:25Z" - latency: 7.262805ms message: 'load-balancer-api-external: resolved host name ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:11:25Z" - latency: 4.6114ms message: 'load-balancer-api-external: tcp connection to ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:10:25Z" - latency: 6.403303ms message: 'load-balancer-api-external: resolved host name ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:10:25Z" - latency: 4.803325ms message: 'load-balancer-api-external: tcp connection to ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:09:25Z" - latency: 9.541837ms message: 'load-balancer-api-external: resolved host name ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:09:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T02:01:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-71-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-71.ec2.internal uid: b9f25ab3-4c04-479e-8b54-1d83610e4447 resourceVersion: "29700" uid: f6394c4b-ffc4-49a1-9f0c-c6ce87491d13 spec: sourcePod: network-check-source-56d84b9f44-ng2fv targetEndpoint: ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T02:07:25Z" message: 'load-balancer-api-internal: tcp connection to ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.156452ms message: 'load-balancer-api-internal: tcp connection to ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:13:25Z" - latency: 12.035592ms message: 'load-balancer-api-internal: resolved host name ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:13:25Z" - latency: 4.878212ms message: 'load-balancer-api-internal: tcp connection to ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:12:25Z" - latency: 7.846761ms message: 'load-balancer-api-internal: resolved host name ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:12:25Z" - latency: 4.21427ms message: 'load-balancer-api-internal: tcp connection to ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:11:25Z" - latency: 7.326394ms message: 'load-balancer-api-internal: resolved host name ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:11:25Z" - latency: 4.651346ms message: 'load-balancer-api-internal: tcp connection to ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:10:25Z" - latency: 6.340608ms message: 'load-balancer-api-internal: resolved host name ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:10:25Z" - latency: 4.822563ms message: 'load-balancer-api-internal: tcp connection to ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:09:25Z" - latency: 9.566328ms message: 'load-balancer-api-internal: resolved host name ae766016852fe45e99f275aafbb27f98-220f7bf51113c319.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T02:09:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T02:01:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-71-to-network-check-target-ip-10-0-131-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-71.ec2.internal uid: b9f25ab3-4c04-479e-8b54-1d83610e4447 resourceVersion: "31726" uid: 55acd4e9-e129-4b1a-bd53-db725c0f5643 spec: sourcePod: network-check-source-56d84b9f44-ng2fv targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T02:08:25Z" message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.230115ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:15:25Z" - latency: 1.947521ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:14:25Z" - latency: 2.271366ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:13:25Z" - latency: 2.30143ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:12:25Z" - latency: 2.297374ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:11:25Z" - latency: 2.544286ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:10:25Z" - latency: 1.910271ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:09:25Z" - latency: 2.34864ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:08:25Z" - latency: 2.329119ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:07:25Z" - latency: 1.953303ms message: 'network-check-target-ip-10-0-131-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:06:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T02:01:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-71-to-network-check-target-ip-10-0-134-54 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-71.ec2.internal uid: b9f25ab3-4c04-479e-8b54-1d83610e4447 resourceVersion: "31727" uid: f86228a7-3768-407a-b6a8-aca5a2665d06 spec: sourcePod: network-check-source-56d84b9f44-ng2fv targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T02:08:25Z" message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.242544ms message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:15:25Z" - latency: 2.037308ms message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:14:25Z" - latency: 2.562243ms message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:13:25Z" - latency: 2.429838ms message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:12:25Z" - latency: 2.294723ms message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:11:25Z" - latency: 2.210048ms message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:10:25Z" - latency: 2.460487ms message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:09:25Z" - latency: 2.258082ms message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:08:25Z" - latency: 2.248195ms message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:07:25Z" - latency: 2.434095ms message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:06:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T02:01:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-71-to-network-check-target-ip-10-0-136-71 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-71.ec2.internal uid: b9f25ab3-4c04-479e-8b54-1d83610e4447 resourceVersion: "31725" uid: 52a7f9bd-99c6-435f-9448-279dd84a7d74 spec: sourcePod: network-check-source-56d84b9f44-ng2fv targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T02:08:25Z" message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 862.161µs message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:15:25Z" - latency: 868.664µs message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:14:25Z" - latency: 836.248µs message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:13:25Z" - latency: 872.434µs message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:12:25Z" - latency: 965.034µs message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:11:25Z" - latency: 1.027609ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:10:25Z" - latency: 1.054348ms message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:09:25Z" - latency: 823.642µs message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:08:25Z" - latency: 881.074µs message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:07:25Z" - latency: 801.012µs message: 'network-check-target-ip-10-0-136-71: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:06:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T02:01:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-71-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-71.ec2.internal uid: b9f25ab3-4c04-479e-8b54-1d83610e4447 resourceVersion: "29699" uid: 263ca67c-1448-4e47-b31b-91348956a4de spec: sourcePod: network-check-source-56d84b9f44-ng2fv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T02:07:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 961.322µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:13:25Z" - latency: 1.779655ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T02:13:25Z" - latency: 1.046065ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:12:25Z" - latency: 1.908703ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T02:12:25Z" - latency: 808.697µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:11:25Z" - latency: 1.667005ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T02:11:25Z" - latency: 915.731µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:10:25Z" - latency: 1.639337ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T02:10:25Z" - latency: 889.271µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:09:25Z" - latency: 1.680586ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T02:09:25Z" kind: List metadata: resourceVersion: ""