apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T20:49:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-216-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-216.ec2.internal uid: 24ef861b-292f-4fe0-9344-04e5945012df resourceVersion: "83903" uid: cf539934-3f83-406c-8ef1-9dae192ce554 spec: sourcePod: network-check-source-7d88cb55d8-xrtjv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T20:56:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.289415ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:59:32Z" - latency: 1.293692ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:58:32Z" - latency: 1.291714ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:57:32Z" - latency: 938.229µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:56:32Z" - latency: 1.255037ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:55:32Z" - latency: 943.785µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:54:32Z" - latency: 844.44µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:53:32Z" - latency: 1.38152ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:52:32Z" - latency: 1.34857ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:51:32Z" - latency: 936.07µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:50:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T20:49:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-216-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-216.ec2.internal uid: 24ef861b-292f-4fe0-9344-04e5945012df resourceVersion: "85714" uid: 14432f25-ba56-4b41-ba51-be88d76bc41c spec: sourcePod: network-check-source-7d88cb55d8-xrtjv targetEndpoint: a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T20:55:32Z" message: 'load-balancer-api-external: tcp connection to a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.181158ms message: 'load-balancer-api-external: tcp connection to a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:01:32Z" - latency: 7.804793ms message: 'load-balancer-api-external: resolved host name a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T22:01:32Z" - latency: 4.217255ms message: 'load-balancer-api-external: tcp connection to a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:00:32Z" - latency: 7.028591ms message: 'load-balancer-api-external: resolved host name a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T22:00:32Z" - latency: 5.266128ms message: 'load-balancer-api-external: tcp connection to a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:59:32Z" - latency: 7.676601ms message: 'load-balancer-api-external: resolved host name a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:59:32Z" - latency: 3.942491ms message: 'load-balancer-api-external: tcp connection to a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:58:32Z" - latency: 6.832079ms message: 'load-balancer-api-external: resolved host name a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:58:32Z" - latency: 3.955176ms message: 'load-balancer-api-external: tcp connection to a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:57:32Z" - latency: 7.333885ms message: 'load-balancer-api-external: resolved host name a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:57:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T20:49:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-216-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-216.ec2.internal uid: 24ef861b-292f-4fe0-9344-04e5945012df resourceVersion: "85715" uid: 917842b1-184f-4e7f-87d4-c95b96a607b6 spec: sourcePod: network-check-source-7d88cb55d8-xrtjv targetEndpoint: a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T20:55:32Z" message: 'load-balancer-api-internal: tcp connection to a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.185115ms message: 'load-balancer-api-internal: tcp connection to a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:01:32Z" - latency: 7.778533ms message: 'load-balancer-api-internal: resolved host name a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T22:01:32Z" - latency: 4.203101ms message: 'load-balancer-api-internal: tcp connection to a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:00:32Z" - latency: 6.960626ms message: 'load-balancer-api-internal: resolved host name a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T22:00:32Z" - latency: 5.252733ms message: 'load-balancer-api-internal: tcp connection to a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:59:32Z" - latency: 7.644076ms message: 'load-balancer-api-internal: resolved host name a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:59:32Z" - latency: 3.93104ms message: 'load-balancer-api-internal: tcp connection to a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:58:32Z" - latency: 6.803529ms message: 'load-balancer-api-internal: resolved host name a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:58:32Z" - latency: 3.998192ms message: 'load-balancer-api-internal: tcp connection to a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:57:32Z" - latency: 7.314201ms message: 'load-balancer-api-internal: resolved host name a3f73a6e1c73947c0a7909fdb0076d8d-804f23f716abb310.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T21:57:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T20:49:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-216-to-network-check-target-ip-10-0-129-194 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-216.ec2.internal uid: 24ef861b-292f-4fe0-9344-04e5945012df resourceVersion: "83901" uid: 21ce90de-f6d8-41c9-8e7f-54384f031a79 spec: sourcePod: network-check-source-7d88cb55d8-xrtjv targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T20:56:32Z" message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.679841ms message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:59:32Z" - latency: 2.531237ms message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:58:32Z" - latency: 2.195914ms message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:57:32Z" - latency: 2.096322ms message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:56:32Z" - latency: 2.175901ms message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:55:32Z" - latency: 2.411685ms message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:54:32Z" - latency: 2.483494ms message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:53:32Z" - latency: 2.420345ms message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:52:32Z" - latency: 2.211332ms message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:51:32Z" - latency: 2.36729ms message: 'network-check-target-ip-10-0-129-194: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:50:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T20:49:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-216-to-network-check-target-ip-10-0-137-216 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-216.ec2.internal uid: 24ef861b-292f-4fe0-9344-04e5945012df resourceVersion: "83900" uid: af9481d1-bee1-49fc-8b88-6aee994325d8 spec: sourcePod: network-check-source-7d88cb55d8-xrtjv targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T20:56:32Z" message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.179198ms message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:59:32Z" - latency: 1.187333ms message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:58:32Z" - latency: 1.515221ms message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:57:32Z" - latency: 1.511297ms message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:56:32Z" - latency: 1.014475ms message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:55:32Z" - latency: 988.299µs message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:54:32Z" - latency: 1.037184ms message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:53:32Z" - latency: 1.024217ms message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:52:32Z" - latency: 962.086µs message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:51:32Z" - latency: 1.026858ms message: 'network-check-target-ip-10-0-137-216: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:50:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T20:49:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-216-to-network-check-target-ip-10-0-139-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-216.ec2.internal uid: 24ef861b-292f-4fe0-9344-04e5945012df resourceVersion: "83902" uid: dacdbee7-d414-479e-a9e8-b925c22a1e49 spec: sourcePod: network-check-source-7d88cb55d8-xrtjv targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T20:56:32Z" message: 'network-check-target-ip-10-0-139-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.749417ms message: 'network-check-target-ip-10-0-139-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:59:32Z" - latency: 2.517172ms message: 'network-check-target-ip-10-0-139-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:58:32Z" - latency: 2.085811ms message: 'network-check-target-ip-10-0-139-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:57:32Z" - latency: 2.599188ms message: 'network-check-target-ip-10-0-139-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:56:32Z" - latency: 2.189581ms message: 'network-check-target-ip-10-0-139-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:55:32Z" - latency: 2.094558ms message: 'network-check-target-ip-10-0-139-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:54:32Z" - latency: 2.517119ms message: 'network-check-target-ip-10-0-139-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:53:32Z" - latency: 2.020341ms message: 'network-check-target-ip-10-0-139-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:52:32Z" - latency: 2.041829ms message: 'network-check-target-ip-10-0-139-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:51:32Z" - latency: 2.701783ms message: 'network-check-target-ip-10-0-139-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:50:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T20:49:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-216-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-216.ec2.internal uid: 24ef861b-292f-4fe0-9344-04e5945012df resourceVersion: "85713" uid: 8c4ff142-9a4f-4409-a456-3b018c532e96 spec: sourcePod: network-check-source-7d88cb55d8-xrtjv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T20:55:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 900.574µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:01:32Z" - latency: 2.164722ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T22:01:32Z" - latency: 1.311098ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T22:00:32Z" - latency: 1.79487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T22:00:32Z" - latency: 977.238µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:59:32Z" - latency: 1.789517ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T21:59:32Z" - latency: 813.416µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:58:32Z" - latency: 1.855593ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T21:58:32Z" - latency: 1.002851ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T21:57:32Z" - latency: 2.102508ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T21:57:32Z" kind: List metadata: resourceVersion: ""