apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T16:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-122-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-122.us-west-2.compute.internal uid: a1e33c67-650b-4782-af37-c24bcb822f77 resourceVersion: "117652" uid: ddcd0ccf-c801-4693-893d-41a0390c08e9 spec: sourcePod: network-check-source-6f78d59f99-65942 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T16:19:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.023391ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:29:56Z" - latency: 1.311097ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:28:56Z" - latency: 1.460076ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:27:56Z" - latency: 1.029661ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:26:56Z" - latency: 893.222µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:25:56Z" - latency: 1.094313ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:24:56Z" - latency: 955.938µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:23:56Z" - latency: 1.03593ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:22:56Z" - latency: 1.057856ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:21:56Z" - latency: 1.757542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:20:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T16:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-122-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-122.us-west-2.compute.internal uid: a1e33c67-650b-4782-af37-c24bcb822f77 resourceVersion: "114842" uid: 018c5a65-eda5-4c3e-8d3b-329bc26d597a spec: sourcePod: network-check-source-6f78d59f99-65942 targetEndpoint: a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T16:18:56Z" message: 'load-balancer-api-external: tcp connection to a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.43079ms message: 'load-balancer-api-external: tcp connection to a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:24:56Z" - latency: 7.15816ms message: 'load-balancer-api-external: resolved host name a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T17:24:56Z" - latency: 50.649005ms message: 'load-balancer-api-external: tcp connection to a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:23:56Z" - latency: 7.251132ms message: 'load-balancer-api-external: resolved host name a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T17:23:56Z" - latency: 51.529729ms message: 'load-balancer-api-external: tcp connection to a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:22:56Z" - latency: 7.508392ms message: 'load-balancer-api-external: resolved host name a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T17:22:56Z" - latency: 56.92134ms message: 'load-balancer-api-external: tcp connection to a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:21:56Z" - latency: 6.658642ms message: 'load-balancer-api-external: resolved host name a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T17:21:56Z" - latency: 56.671256ms message: 'load-balancer-api-external: tcp connection to a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:20:56Z" - latency: 7.586689ms message: 'load-balancer-api-external: resolved host name a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T17:20:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T16:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-122-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-122.us-west-2.compute.internal uid: a1e33c67-650b-4782-af37-c24bcb822f77 resourceVersion: "114841" uid: 1ef469a0-aee5-4cda-80cd-bef0c3d66d09 spec: sourcePod: network-check-source-6f78d59f99-65942 targetEndpoint: a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T16:18:56Z" message: 'load-balancer-api-internal: tcp connection to a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 49.978312ms message: 'load-balancer-api-internal: tcp connection to a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:24:56Z" - latency: 7.066161ms message: 'load-balancer-api-internal: resolved host name a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T17:24:56Z" - latency: 49.709343ms message: 'load-balancer-api-internal: tcp connection to a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:23:56Z" - latency: 7.270346ms message: 'load-balancer-api-internal: resolved host name a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T17:23:56Z" - latency: 52.959251ms message: 'load-balancer-api-internal: tcp connection to a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:22:56Z" - latency: 7.396171ms message: 'load-balancer-api-internal: resolved host name a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T17:22:56Z" - latency: 56.886608ms message: 'load-balancer-api-internal: tcp connection to a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:21:56Z" - latency: 6.727629ms message: 'load-balancer-api-internal: resolved host name a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T17:21:56Z" - latency: 56.734125ms message: 'load-balancer-api-internal: tcp connection to a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:20:56Z" - latency: 7.553656ms message: 'load-balancer-api-internal: resolved host name a7ccfbe3a02a843d98ab5cd19bd85dc7-f84d5194377c4192.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T17:20:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T16:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-122-to-network-check-target-ip-10-0-135-216 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-122.us-west-2.compute.internal uid: a1e33c67-650b-4782-af37-c24bcb822f77 resourceVersion: "117650" uid: 11308dd5-99de-4e9d-a6a6-22ba9556acab spec: sourcePod: network-check-source-6f78d59f99-65942 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T16:19:56Z" message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.342054ms message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:29:56Z" - latency: 2.178599ms message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:28:56Z" - latency: 2.318202ms message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:27:56Z" - latency: 2.375552ms message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:26:56Z" - latency: 2.326978ms message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:25:56Z" - latency: 2.478955ms message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:24:56Z" - latency: 2.317092ms message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:23:56Z" - latency: 2.250933ms message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:22:56Z" - latency: 2.346359ms message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:21:56Z" - latency: 2.546611ms message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:20:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T16:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-122-to-network-check-target-ip-10-0-137-122 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-122.us-west-2.compute.internal uid: a1e33c67-650b-4782-af37-c24bcb822f77 resourceVersion: "117649" uid: ea24340d-4837-4323-9e3f-f344a7f9206b spec: sourcePod: network-check-source-6f78d59f99-65942 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T16:19:56Z" message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.081428ms message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:29:56Z" - latency: 937.955µs message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:28:56Z" - latency: 965.371µs message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:27:56Z" - latency: 1.267585ms message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:26:56Z" - latency: 1.749646ms message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:25:56Z" - latency: 885.395µs message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:24:56Z" - latency: 1.306745ms message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:23:56Z" - latency: 1.538069ms message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:22:56Z" - latency: 1.324583ms message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:21:56Z" - latency: 1.023105ms message: 'network-check-target-ip-10-0-137-122: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:20:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T16:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-122-to-network-check-target-ip-10-0-142-22 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-122.us-west-2.compute.internal uid: a1e33c67-650b-4782-af37-c24bcb822f77 resourceVersion: "117651" uid: d6b4361b-cbdb-4cf8-9403-2bec704da567 spec: sourcePod: network-check-source-6f78d59f99-65942 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T16:19:56Z" message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.254909ms message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:29:56Z" - latency: 2.155414ms message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:28:56Z" - latency: 2.07913ms message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:27:56Z" - latency: 2.21681ms message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:26:56Z" - latency: 2.292886ms message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:25:56Z" - latency: 2.536535ms message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:24:56Z" - latency: 2.180906ms message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:23:56Z" - latency: 2.492362ms message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:22:56Z" - latency: 2.21894ms message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:21:56Z" - latency: 2.46524ms message: 'network-check-target-ip-10-0-142-22: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:20:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T16:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-122-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-122.us-west-2.compute.internal uid: a1e33c67-650b-4782-af37-c24bcb822f77 resourceVersion: "114839" uid: 04af7120-4db9-42d7-825e-700fba89e260 spec: sourcePod: network-check-source-6f78d59f99-65942 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T16:18:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 980.214µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:24:56Z" - latency: 1.780857ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T17:24:56Z" - latency: 1.048114ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:23:56Z" - latency: 2.161369ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T17:23:56Z" - latency: 1.760057ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:22:56Z" - latency: 1.937766ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T17:22:56Z" - latency: 992.65µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:21:56Z" - latency: 2.0334ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T17:21:56Z" - latency: 1.42223ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T17:20:56Z" - latency: 1.965707ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T17:20:56Z" kind: List metadata: resourceVersion: ""