apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T04:05:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-135-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-135.ec2.internal uid: dd3cac34-c2d4-4dc4-a9ec-46cd742e2464 resourceVersion: "23454" uid: 5cc92512-c18e-4bd3-a70a-119ea2015d36 spec: sourcePod: network-check-source-685456655f-mtblq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-07T04:12:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.039825ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:12:39Z" - latency: 1.15277ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:11:39Z" - latency: 1.034871ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:10:39Z" - latency: 997.381µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:09:39Z" - latency: 838.016µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:08:39Z" - latency: 875.25µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:07:39Z" - latency: 1.242348ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:06:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T04:05:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-135-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-135.ec2.internal uid: dd3cac34-c2d4-4dc4-a9ec-46cd742e2464 resourceVersion: "26613" uid: 0f668fc4-2ac6-4bbd-8604-83fac700ce62 spec: sourcePod: network-check-source-685456655f-mtblq targetEndpoint: a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-07T04:11:39Z" message: 'load-balancer-api-external: tcp connection to a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.321939ms message: 'load-balancer-api-external: tcp connection to a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:17:39Z" - latency: 10.124112ms message: 'load-balancer-api-external: resolved host name a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:17:39Z" - latency: 3.851183ms message: 'load-balancer-api-external: tcp connection to a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:16:39Z" - latency: 17.457771ms message: 'load-balancer-api-external: resolved host name a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:16:39Z" - latency: 4.037738ms message: 'load-balancer-api-external: tcp connection to a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:15:39Z" - latency: 8.720116ms message: 'load-balancer-api-external: resolved host name a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:15:39Z" - latency: 3.264302ms message: 'load-balancer-api-external: tcp connection to a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:14:39Z" - latency: 8.132153ms message: 'load-balancer-api-external: resolved host name a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:14:39Z" - latency: 4.607114ms message: 'load-balancer-api-external: tcp connection to a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:13:39Z" - latency: 8.334328ms message: 'load-balancer-api-external: resolved host name a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:13:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T04:05:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-135-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-135.ec2.internal uid: dd3cac34-c2d4-4dc4-a9ec-46cd742e2464 resourceVersion: "26612" uid: d8ba0611-4f97-47f7-825a-29694a1891a3 spec: sourcePod: network-check-source-685456655f-mtblq targetEndpoint: a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-07T04:11:39Z" message: 'load-balancer-api-internal: tcp connection to a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.629865ms message: 'load-balancer-api-internal: tcp connection to a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:17:39Z" - latency: 10.054314ms message: 'load-balancer-api-internal: resolved host name a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:17:39Z" - latency: 4.57276ms message: 'load-balancer-api-internal: tcp connection to a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:16:39Z" - latency: 17.371803ms message: 'load-balancer-api-internal: resolved host name a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:16:39Z" - latency: 4.09349ms message: 'load-balancer-api-internal: tcp connection to a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:15:39Z" - latency: 8.545884ms message: 'load-balancer-api-internal: resolved host name a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:15:39Z" - latency: 4.61014ms message: 'load-balancer-api-internal: tcp connection to a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:14:39Z" - latency: 7.943223ms message: 'load-balancer-api-internal: resolved host name a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:14:39Z" - latency: 4.618852ms message: 'load-balancer-api-internal: tcp connection to a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:13:39Z" - latency: 8.309388ms message: 'load-balancer-api-internal: resolved host name a6110eb9c941b48c29f894eba40ed613-6c56e4e9eab131e7.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-07T04:13:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T04:05:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-135-to-network-check-target-ip-10-0-135-135 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-135.ec2.internal uid: dd3cac34-c2d4-4dc4-a9ec-46cd742e2464 resourceVersion: "23451" uid: 9107d99f-5680-4896-b711-041c05574bdd spec: sourcePod: network-check-source-685456655f-mtblq targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-07T04:12:39Z" message: 'network-check-target-ip-10-0-135-135: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 820.293µs message: 'network-check-target-ip-10-0-135-135: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:12:39Z" - latency: 778.387µs message: 'network-check-target-ip-10-0-135-135: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:11:39Z" - latency: 999.311µs message: 'network-check-target-ip-10-0-135-135: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:10:39Z" - latency: 934.345µs message: 'network-check-target-ip-10-0-135-135: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:09:39Z" - latency: 1.104812ms message: 'network-check-target-ip-10-0-135-135: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:08:39Z" - latency: 913.129µs message: 'network-check-target-ip-10-0-135-135: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:07:39Z" - latency: 1.469283ms message: 'network-check-target-ip-10-0-135-135: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:06:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T04:05:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-135-to-network-check-target-ip-10-0-143-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-135.ec2.internal uid: dd3cac34-c2d4-4dc4-a9ec-46cd742e2464 resourceVersion: "23453" uid: d3052619-83bd-4adc-895c-e1e5a3d83ff6 spec: sourcePod: network-check-source-685456655f-mtblq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-07T04:12:39Z" message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.902557ms message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:12:39Z" - latency: 1.957641ms message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:11:39Z" - latency: 2.047354ms message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:10:39Z" - latency: 1.959297ms message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:09:39Z" - latency: 1.867647ms message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:08:39Z" - latency: 2.053875ms message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:07:39Z" - latency: 2.110573ms message: 'network-check-target-ip-10-0-143-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:06:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T04:05:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-135-to-network-check-target-ip-10-0-143-54 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-135.ec2.internal uid: dd3cac34-c2d4-4dc4-a9ec-46cd742e2464 resourceVersion: "23452" uid: 2fd7af21-7aeb-4c4f-8a8e-e17e01f7a45e spec: sourcePod: network-check-source-685456655f-mtblq targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-07T04:12:39Z" message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.23056ms message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:12:39Z" - latency: 2.131557ms message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:11:39Z" - latency: 2.152808ms message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:10:39Z" - latency: 2.437431ms message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:09:39Z" - latency: 2.129699ms message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:08:39Z" - latency: 2.498919ms message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:07:39Z" - latency: 2.646733ms message: 'network-check-target-ip-10-0-143-54: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:06:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-07T04:05:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-135-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-135.ec2.internal uid: dd3cac34-c2d4-4dc4-a9ec-46cd742e2464 resourceVersion: "26611" uid: 275917e3-faee-4048-9498-bfad9b69c30e spec: sourcePod: network-check-source-685456655f-mtblq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-07T04:11:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 811.121µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:17:39Z" - latency: 1.598138ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T04:17:39Z" - latency: 847.12µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:16:39Z" - latency: 1.978245ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T04:16:39Z" - latency: 1.01283ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:15:39Z" - latency: 1.880591ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T04:15:39Z" - latency: 1.123926ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:14:39Z" - latency: 1.863849ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T04:14:39Z" - latency: 949.137µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-07T04:13:39Z" - latency: 1.72766ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-07T04:13:39Z" kind: List metadata: resourceVersion: ""