apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T23:14:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-15-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-15.ec2.internal uid: 08602ff9-9ec2-420b-8eb2-fc46f6117acb resourceVersion: "55923" uid: e31c22ce-ab4f-4cda-8494-34a825b319d6 spec: sourcePod: network-check-source-989f8b8dc-dhvvn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T23:21:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.324526ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:49:28Z" - latency: 1.266786ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:48:28Z" - latency: 1.175939ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:47:28Z" - latency: 1.012748ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:46:28Z" - latency: 1.128728ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:45:28Z" - latency: 1.257365ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:44:28Z" - latency: 1.16161ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:43:28Z" - latency: 1.164444ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:42:28Z" - latency: 2.579791ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:41:28Z" - latency: 1.24043ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:40:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T23:14:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-15-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-15.ec2.internal uid: 08602ff9-9ec2-420b-8eb2-fc46f6117acb resourceVersion: "56774" uid: 7794c420-aa90-4cea-bbe1-29f9c6d6eb1a spec: sourcePod: network-check-source-989f8b8dc-dhvvn targetEndpoint: aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T23:20:28Z" message: 'load-balancer-api-external: tcp connection to aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.527867ms message: 'load-balancer-api-external: tcp connection to aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:50:28Z" - latency: 7.82357ms message: 'load-balancer-api-external: resolved host name aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T23:50:28Z" - latency: 5.032729ms message: 'load-balancer-api-external: tcp connection to aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:49:28Z" - latency: 7.65567ms message: 'load-balancer-api-external: resolved host name aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T23:49:28Z" - latency: 3.73496ms message: 'load-balancer-api-external: tcp connection to aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:48:28Z" - latency: 7.185665ms message: 'load-balancer-api-external: resolved host name aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T23:48:28Z" - latency: 4.634273ms message: 'load-balancer-api-external: tcp connection to aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:47:28Z" - latency: 6.558955ms message: 'load-balancer-api-external: resolved host name aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T23:47:28Z" - latency: 3.855024ms message: 'load-balancer-api-external: tcp connection to aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:46:28Z" - latency: 7.29709ms message: 'load-balancer-api-external: resolved host name aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T23:46:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T23:14:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-15-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-15.ec2.internal uid: 08602ff9-9ec2-420b-8eb2-fc46f6117acb resourceVersion: "56773" uid: 9bf33c9b-8fd9-4975-a9be-83075fa22778 spec: sourcePod: network-check-source-989f8b8dc-dhvvn targetEndpoint: aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T23:20:28Z" message: 'load-balancer-api-internal: tcp connection to aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.524338ms message: 'load-balancer-api-internal: tcp connection to aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:50:28Z" - latency: 7.854685ms message: 'load-balancer-api-internal: resolved host name aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T23:50:28Z" - latency: 4.083654ms message: 'load-balancer-api-internal: tcp connection to aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:49:28Z" - latency: 7.418802ms message: 'load-balancer-api-internal: resolved host name aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T23:49:28Z" - latency: 4.886312ms message: 'load-balancer-api-internal: tcp connection to aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:48:28Z" - latency: 7.196011ms message: 'load-balancer-api-internal: resolved host name aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T23:48:28Z" - latency: 4.078541ms message: 'load-balancer-api-internal: tcp connection to aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:47:28Z" - latency: 6.624603ms message: 'load-balancer-api-internal: resolved host name aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T23:47:28Z" - latency: 3.695664ms message: 'load-balancer-api-internal: tcp connection to aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:46:28Z" - latency: 7.277285ms message: 'load-balancer-api-internal: resolved host name aa34496e3ec5e4ea39c3cc95a74b50f1-55048fbc68e46075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T23:46:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T23:14:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-15-to-network-check-target-ip-10-0-130-115 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-15.ec2.internal uid: 08602ff9-9ec2-420b-8eb2-fc46f6117acb resourceVersion: "55922" uid: 4c216cd4-f1d8-42d4-9e73-9ec9f4ec658e spec: sourcePod: network-check-source-989f8b8dc-dhvvn targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T23:21:28Z" message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.573251ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:49:28Z" - latency: 2.398798ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:48:28Z" - latency: 2.145476ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:47:28Z" - latency: 2.403088ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:46:28Z" - latency: 2.292362ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:45:28Z" - latency: 2.124503ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:44:28Z" - latency: 1.979617ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:43:28Z" - latency: 2.199126ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:42:28Z" - latency: 2.424246ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:41:28Z" - latency: 1.80638ms message: 'network-check-target-ip-10-0-130-115: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:40:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T23:14:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-15-to-network-check-target-ip-10-0-133-37 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-15.ec2.internal uid: 08602ff9-9ec2-420b-8eb2-fc46f6117acb resourceVersion: "55921" uid: 3d289f5b-1033-4928-b6db-d9d79ab5f275 spec: sourcePod: network-check-source-989f8b8dc-dhvvn targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T23:21:28Z" message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.20513ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:49:28Z" - latency: 1.976523ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:48:28Z" - latency: 2.216448ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:47:28Z" - latency: 1.936517ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:46:28Z" - latency: 2.137655ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:45:28Z" - latency: 2.030404ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:44:28Z" - latency: 1.903871ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:43:28Z" - latency: 2.062681ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:42:28Z" - latency: 2.719925ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:41:28Z" - latency: 1.977192ms message: 'network-check-target-ip-10-0-133-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:40:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T23:14:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-15-to-network-check-target-ip-10-0-138-15 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-15.ec2.internal uid: 08602ff9-9ec2-420b-8eb2-fc46f6117acb resourceVersion: "55920" uid: b1602d2f-3a49-4e25-b804-adcba533bb3b spec: sourcePod: network-check-source-989f8b8dc-dhvvn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T23:21:28Z" message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.742748ms message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:49:28Z" - latency: 1.008091ms message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:48:28Z" - latency: 1.130739ms message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:47:28Z" - latency: 948.906µs message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:46:28Z" - latency: 1.150927ms message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:45:28Z" - latency: 1.087185ms message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:44:28Z" - latency: 1.581981ms message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:43:28Z" - latency: 1.063435ms message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:42:28Z" - latency: 1.364425ms message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:41:28Z" - latency: 1.044598ms message: 'network-check-target-ip-10-0-138-15: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:40:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T23:14:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-15-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-15.ec2.internal uid: 08602ff9-9ec2-420b-8eb2-fc46f6117acb resourceVersion: "56771" uid: c949afa9-8079-4eac-aad2-ae4e0d46a6b8 spec: sourcePod: network-check-source-989f8b8dc-dhvvn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T23:20:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 911.654µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:50:28Z" - latency: 2.017312ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T23:50:28Z" - latency: 1.000286ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:49:28Z" - latency: 1.810917ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T23:49:28Z" - latency: 1.140117ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:48:28Z" - latency: 1.889717ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T23:48:28Z" - latency: 775.104µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:47:28Z" - latency: 2.105637ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T23:47:28Z" - latency: 888.671µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T23:46:28Z" - latency: 1.868497ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T23:46:28Z" kind: List metadata: resourceVersion: ""