apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T14:49:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-34-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-34.ec2.internal uid: c3c5861a-7e72-4d6a-a9b6-e377c6ac8bb9 resourceVersion: "36641" uid: 35ea4bda-9633-46f8-b8b9-1c71650fa0f0 spec: sourcePod: network-check-source-869dcfcdcd-8hnxn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T14:56:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.033126ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:10:33Z" - latency: 1.209742ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:09:33Z" - latency: 1.086943ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:08:33Z" - latency: 1.199985ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:07:33Z" - latency: 1.000436ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:06:33Z" - latency: 1.004882ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:05:33Z" - latency: 900.446µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:04:33Z" - latency: 1.216819ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:03:33Z" - latency: 931.817µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:02:33Z" - latency: 948.375µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:01:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T14:49:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-34-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-34.ec2.internal uid: c3c5861a-7e72-4d6a-a9b6-e377c6ac8bb9 resourceVersion: "34271" uid: c3720c13-835a-450d-b2ec-e7ffdc94910b spec: sourcePod: network-check-source-869dcfcdcd-8hnxn targetEndpoint: aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T14:55:33Z" message: 'load-balancer-api-external: tcp connection to aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.955905ms message: 'load-balancer-api-external: tcp connection to aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:07:33Z" - latency: 9.892306ms message: 'load-balancer-api-external: resolved host name aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:07:33Z" - latency: 6.266963ms message: 'load-balancer-api-external: tcp connection to aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:06:33Z" - latency: 6.59731ms message: 'load-balancer-api-external: resolved host name aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:06:33Z" - latency: 4.58751ms message: 'load-balancer-api-external: tcp connection to aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:05:33Z" - latency: 7.606424ms message: 'load-balancer-api-external: resolved host name aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:05:33Z" - latency: 5.24734ms message: 'load-balancer-api-external: tcp connection to aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:04:33Z" - latency: 7.319766ms message: 'load-balancer-api-external: resolved host name aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:04:33Z" - latency: 10.499139ms message: 'load-balancer-api-external: tcp connection to aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:03:33Z" - latency: 7.811058ms message: 'load-balancer-api-external: resolved host name aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:03:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T14:49:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-34-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-34.ec2.internal uid: c3c5861a-7e72-4d6a-a9b6-e377c6ac8bb9 resourceVersion: "34272" uid: 6b69e751-1512-4e70-bb02-903f12afab8f spec: sourcePod: network-check-source-869dcfcdcd-8hnxn targetEndpoint: aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T14:55:33Z" message: 'load-balancer-api-internal: tcp connection to aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.012862ms message: 'load-balancer-api-internal: tcp connection to aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:07:33Z" - latency: 9.828069ms message: 'load-balancer-api-internal: resolved host name aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:07:33Z" - latency: 6.31532ms message: 'load-balancer-api-internal: tcp connection to aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:06:33Z" - latency: 6.562532ms message: 'load-balancer-api-internal: resolved host name aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:06:33Z" - latency: 4.021994ms message: 'load-balancer-api-internal: tcp connection to aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:05:33Z" - latency: 7.573725ms message: 'load-balancer-api-internal: resolved host name aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:05:33Z" - latency: 5.266615ms message: 'load-balancer-api-internal: tcp connection to aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:04:33Z" - latency: 7.248622ms message: 'load-balancer-api-internal: resolved host name aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:04:33Z" - latency: 16.303726ms message: 'load-balancer-api-internal: tcp connection to aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:03:33Z" - latency: 7.849499ms message: 'load-balancer-api-internal: resolved host name aaeff63acf3f74cb4bdd27512c7303f2-8d9a5af5fb1e6e64.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T15:03:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T14:49:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-34-to-network-check-target-ip-10-0-133-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-34.ec2.internal uid: c3c5861a-7e72-4d6a-a9b6-e377c6ac8bb9 resourceVersion: "36639" uid: a798ed34-d896-451d-8d38-fec387127787 spec: sourcePod: network-check-source-869dcfcdcd-8hnxn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T14:56:33Z" message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.232964ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:10:33Z" - latency: 2.241505ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:09:33Z" - latency: 2.13716ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:08:33Z" - latency: 2.151217ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:07:33Z" - latency: 2.137243ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:06:33Z" - latency: 2.159113ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:05:33Z" - latency: 2.273996ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:04:33Z" - latency: 2.581721ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:03:33Z" - latency: 2.115724ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:02:33Z" - latency: 2.004225ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:01:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T14:49:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-34-to-network-check-target-ip-10-0-142-186 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-34.ec2.internal uid: c3c5861a-7e72-4d6a-a9b6-e377c6ac8bb9 resourceVersion: "36638" uid: ef4f10cb-6bfa-449c-a229-4e74d6a9b480 spec: sourcePod: network-check-source-869dcfcdcd-8hnxn targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T14:56:33Z" message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.148715ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:10:33Z" - latency: 2.300944ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:09:33Z" - latency: 2.059901ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:08:33Z" - latency: 2.129149ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:07:33Z" - latency: 2.108696ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:06:33Z" - latency: 1.701224ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:05:33Z" - latency: 2.089154ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:04:33Z" - latency: 2.273827ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:03:33Z" - latency: 1.978242ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:02:33Z" - latency: 2.078423ms message: 'network-check-target-ip-10-0-142-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:01:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T14:49:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-34-to-network-check-target-ip-10-0-142-34 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-34.ec2.internal uid: c3c5861a-7e72-4d6a-a9b6-e377c6ac8bb9 resourceVersion: "36640" uid: 7b0616c8-c900-407b-b7b5-3d58402418a5 spec: sourcePod: network-check-source-869dcfcdcd-8hnxn targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T14:56:33Z" message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.290307ms message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:10:33Z" - latency: 1.389623ms message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:09:33Z" - latency: 1.356289ms message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:08:33Z" - latency: 812.222µs message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:07:33Z" - latency: 1.326982ms message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:06:33Z" - latency: 883.851µs message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:05:33Z" - latency: 1.517417ms message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:04:33Z" - latency: 1.149981ms message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:03:33Z" - latency: 1.307914ms message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:02:33Z" - latency: 764.961µs message: 'network-check-target-ip-10-0-142-34: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:01:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T14:49:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-34-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-34.ec2.internal uid: c3c5861a-7e72-4d6a-a9b6-e377c6ac8bb9 resourceVersion: "34270" uid: bcf81826-4900-410e-befb-115113456482 spec: sourcePod: network-check-source-869dcfcdcd-8hnxn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T14:55:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 694.423µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:07:33Z" - latency: 1.963319ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T15:07:33Z" - latency: 913.185µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:06:33Z" - latency: 1.674742ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T15:06:33Z" - latency: 931.683µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:05:33Z" - latency: 1.966749ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T15:05:33Z" - latency: 875.235µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:04:33Z" - latency: 1.644949ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T15:04:33Z" - latency: 1.457036ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T15:03:33Z" - latency: 1.995443ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T15:03:33Z" kind: List metadata: resourceVersion: ""