apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T00:50:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-60-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-60.ec2.internal uid: 5a418172-29e4-4fee-ad8a-1f5afd1fb3cf resourceVersion: "61953" uid: 1cdfb512-e0f1-4ab6-880f-4203582ebca8 spec: sourcePod: network-check-source-869dcfcdcd-jxlnl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T00:57:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 929.322µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:32:36Z" - latency: 1.156078ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:31:36Z" - latency: 1.352485ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:30:36Z" - latency: 994.426µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:29:36Z" - latency: 1.150514ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:28:36Z" - latency: 1.072905ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:27:36Z" - latency: 889.335µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:26:36Z" - latency: 1.691886ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:25:36Z" - latency: 1.520163ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:24:36Z" - latency: 736.34µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:23:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T00:50:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-60-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-60.ec2.internal uid: 5a418172-29e4-4fee-ad8a-1f5afd1fb3cf resourceVersion: "61955" uid: 37565746-4f53-4810-b2f0-0db962da7ea5 spec: sourcePod: network-check-source-869dcfcdcd-jxlnl targetEndpoint: ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T00:56:36Z" message: 'load-balancer-api-external: tcp connection to ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.181308ms message: 'load-balancer-api-external: tcp connection to ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:32:36Z" - latency: 8.374307ms message: 'load-balancer-api-external: resolved host name ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:32:36Z" - latency: 5.578717ms message: 'load-balancer-api-external: tcp connection to ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:31:36Z" - latency: 8.879665ms message: 'load-balancer-api-external: resolved host name ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:31:36Z" - latency: 5.152662ms message: 'load-balancer-api-external: tcp connection to ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:30:36Z" - latency: 8.602145ms message: 'load-balancer-api-external: resolved host name ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:30:36Z" - latency: 5.126604ms message: 'load-balancer-api-external: tcp connection to ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:29:36Z" - latency: 8.639157ms message: 'load-balancer-api-external: resolved host name ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:29:36Z" - latency: 4.73471ms message: 'load-balancer-api-external: tcp connection to ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:28:36Z" - latency: 8.282044ms message: 'load-balancer-api-external: resolved host name ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:28:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T00:50:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-60-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-60.ec2.internal uid: 5a418172-29e4-4fee-ad8a-1f5afd1fb3cf resourceVersion: "61954" uid: b2836cb7-922e-4939-9fc8-da866a0f001a spec: sourcePod: network-check-source-869dcfcdcd-jxlnl targetEndpoint: ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T00:56:36Z" message: 'load-balancer-api-internal: tcp connection to ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.044579ms message: 'load-balancer-api-internal: tcp connection to ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:32:36Z" - latency: 8.349415ms message: 'load-balancer-api-internal: resolved host name ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:32:36Z" - latency: 5.628177ms message: 'load-balancer-api-internal: tcp connection to ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:31:36Z" - latency: 8.847121ms message: 'load-balancer-api-internal: resolved host name ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:31:36Z" - latency: 5.152752ms message: 'load-balancer-api-internal: tcp connection to ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:30:36Z" - latency: 8.581597ms message: 'load-balancer-api-internal: resolved host name ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:30:36Z" - latency: 3.905921ms message: 'load-balancer-api-internal: tcp connection to ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:29:36Z" - latency: 8.718969ms message: 'load-balancer-api-internal: resolved host name ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:29:36Z" - latency: 4.627114ms message: 'load-balancer-api-internal: tcp connection to ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:28:36Z" - latency: 8.343847ms message: 'load-balancer-api-internal: resolved host name ada074aa9bb9f4e07843b6f1500cced7-fbe801fb73720595.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T01:28:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T00:50:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-60-to-network-check-target-ip-10-0-129-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-60.ec2.internal uid: 5a418172-29e4-4fee-ad8a-1f5afd1fb3cf resourceVersion: "61952" uid: 0f79b66d-7ae5-4a4a-8be9-c97e2f26a08d spec: sourcePod: network-check-source-869dcfcdcd-jxlnl targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T00:57:36Z" message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.320452ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:32:36Z" - latency: 1.672178ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:31:36Z" - latency: 2.004714ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:30:36Z" - latency: 1.768459ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:29:36Z" - latency: 1.992187ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:28:36Z" - latency: 2.00129ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:27:36Z" - latency: 1.877475ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:26:36Z" - latency: 2.091096ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:25:36Z" - latency: 1.699813ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:24:36Z" - latency: 1.905583ms message: 'network-check-target-ip-10-0-129-125: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:23:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T00:50:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-60-to-network-check-target-ip-10-0-131-60 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-60.ec2.internal uid: 5a418172-29e4-4fee-ad8a-1f5afd1fb3cf resourceVersion: "61949" uid: 51fbe7e3-71cf-48fd-be63-1d9cd91862dc spec: sourcePod: network-check-source-869dcfcdcd-jxlnl targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T00:57:36Z" message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.091139ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:32:36Z" - latency: 952.403µs message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:31:36Z" - latency: 1.367929ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:30:36Z" - latency: 1.159526ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:29:36Z" - latency: 1.472878ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:28:36Z" - latency: 893.386µs message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:27:36Z" - latency: 988.328µs message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:26:36Z" - latency: 940.934µs message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:25:36Z" - latency: 2.022149ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:24:36Z" - latency: 1.307081ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:23:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T00:50:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-60-to-network-check-target-ip-10-0-134-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-60.ec2.internal uid: 5a418172-29e4-4fee-ad8a-1f5afd1fb3cf resourceVersion: "61950" uid: d4429e30-bbe5-4294-918a-8c1cf68d9e15 spec: sourcePod: network-check-source-869dcfcdcd-jxlnl targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-14T00:57:36Z" message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.914287ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:32:36Z" - latency: 1.92021ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:31:36Z" - latency: 2.07479ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:30:36Z" - latency: 2.039519ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:29:36Z" - latency: 2.353636ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:28:36Z" - latency: 1.940607ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:27:36Z" - latency: 1.985892ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:26:36Z" - latency: 2.384637ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:25:36Z" - latency: 1.971946ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:24:36Z" - latency: 1.939296ms message: 'network-check-target-ip-10-0-134-143: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:23:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T00:50:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-60-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-60.ec2.internal uid: 5a418172-29e4-4fee-ad8a-1f5afd1fb3cf resourceVersion: "61951" uid: c75f281b-df2c-4fb1-aba4-0b5839acf457 spec: sourcePod: network-check-source-869dcfcdcd-jxlnl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T00:56:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.251404ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:32:36Z" - latency: 1.920229ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T01:32:36Z" - latency: 1.069781ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:31:36Z" - latency: 1.590318ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T01:31:36Z" - latency: 876.661µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:30:36Z" - latency: 1.702961ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T01:30:36Z" - latency: 907.54µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:29:36Z" - latency: 1.627531ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T01:29:36Z" - latency: 823.419µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T01:28:36Z" - latency: 1.8174ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T01:28:36Z" kind: List metadata: resourceVersion: ""