apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T18:59:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-51-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-51.ec2.internal uid: e81f8bdd-1058-47ef-8331-dadadb0ad371 resourceVersion: "63186" uid: f2a5b88b-ec3f-42e5-bddf-b259fea6c28b spec: sourcePod: network-check-source-7bc5b6bf85-qtmwq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T19:06:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 897.915µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:41:53Z" - latency: 1.088779ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:40:53Z" - latency: 961.592µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:39:53Z" - latency: 1.390906ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:38:53Z" - latency: 1.012984ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:37:53Z" - latency: 1.265762ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:36:53Z" - latency: 1.188429ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:35:53Z" - latency: 1.207693ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:34:53Z" - latency: 989.431µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:33:53Z" - latency: 950.399µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:32:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T18:59:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-51-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-51.ec2.internal uid: e81f8bdd-1058-47ef-8331-dadadb0ad371 resourceVersion: "63187" uid: da3a65c0-9c92-4b09-bd3b-1badb8e652b3 spec: sourcePod: network-check-source-7bc5b6bf85-qtmwq targetEndpoint: a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T19:05:53Z" message: 'load-balancer-api-external: tcp connection to a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.087698ms message: 'load-balancer-api-external: tcp connection to a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:41:53Z" - latency: 7.96026ms message: 'load-balancer-api-external: resolved host name a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:41:53Z" - latency: 5.021795ms message: 'load-balancer-api-external: tcp connection to a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:40:53Z" - latency: 7.430232ms message: 'load-balancer-api-external: resolved host name a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:40:53Z" - latency: 4.934205ms message: 'load-balancer-api-external: tcp connection to a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:39:53Z" - latency: 8.611904ms message: 'load-balancer-api-external: resolved host name a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:39:53Z" - latency: 4.607972ms message: 'load-balancer-api-external: tcp connection to a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:38:53Z" - latency: 9.233612ms message: 'load-balancer-api-external: resolved host name a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:38:53Z" - latency: 3.845011ms message: 'load-balancer-api-external: tcp connection to a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:37:53Z" - latency: 7.355088ms message: 'load-balancer-api-external: resolved host name a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:37:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T18:59:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-51-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-51.ec2.internal uid: e81f8bdd-1058-47ef-8331-dadadb0ad371 resourceVersion: "63188" uid: 699425c7-6c49-4a55-a463-db2dd34d5c06 spec: sourcePod: network-check-source-7bc5b6bf85-qtmwq targetEndpoint: a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T19:05:53Z" message: 'load-balancer-api-internal: tcp connection to a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.782018ms message: 'load-balancer-api-internal: tcp connection to a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:41:53Z" - latency: 7.973056ms message: 'load-balancer-api-internal: resolved host name a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:41:53Z" - latency: 3.660819ms message: 'load-balancer-api-internal: tcp connection to a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:40:53Z" - latency: 7.4471ms message: 'load-balancer-api-internal: resolved host name a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:40:53Z" - latency: 4.927566ms message: 'load-balancer-api-internal: tcp connection to a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:39:53Z" - latency: 8.64288ms message: 'load-balancer-api-internal: resolved host name a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:39:53Z" - latency: 4.613143ms message: 'load-balancer-api-internal: tcp connection to a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:38:53Z" - latency: 9.171911ms message: 'load-balancer-api-internal: resolved host name a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:38:53Z" - latency: 5.833104ms message: 'load-balancer-api-internal: tcp connection to a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:37:53Z" - latency: 7.326849ms message: 'load-balancer-api-internal: resolved host name a5cd44ce5cb634c17a6d377adb0b5853-e3e351f6ddf4f0a4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T19:37:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T18:59:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-51-to-network-check-target-ip-10-0-129-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-51.ec2.internal uid: e81f8bdd-1058-47ef-8331-dadadb0ad371 resourceVersion: "63184" uid: c72acd67-214b-44f3-a519-2e138439d5ca spec: sourcePod: network-check-source-7bc5b6bf85-qtmwq targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T19:06:53Z" message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.396004ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:41:53Z" - latency: 2.565924ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:40:53Z" - latency: 2.249382ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:39:53Z" - latency: 2.680474ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:38:53Z" - latency: 2.523509ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:37:53Z" - latency: 2.398757ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:36:53Z" - latency: 2.907771ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:35:53Z" - latency: 2.27674ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:34:53Z" - latency: 2.508657ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:33:53Z" - latency: 2.55033ms message: 'network-check-target-ip-10-0-129-246: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:32:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T18:59:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-51-to-network-check-target-ip-10-0-137-176 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-51.ec2.internal uid: e81f8bdd-1058-47ef-8331-dadadb0ad371 resourceVersion: "63183" uid: efd24cb5-df18-4a5c-89bd-9c6097c7c7e1 spec: sourcePod: network-check-source-7bc5b6bf85-qtmwq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T19:06:53Z" message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.042463ms message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:41:53Z" - latency: 2.410868ms message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:40:53Z" - latency: 2.369483ms message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:39:53Z" - latency: 2.534239ms message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:38:53Z" - latency: 2.36537ms message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:37:53Z" - latency: 2.30097ms message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:36:53Z" - latency: 3.054187ms message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:35:53Z" - latency: 2.177438ms message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:34:53Z" - latency: 2.161568ms message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:33:53Z" - latency: 2.321953ms message: 'network-check-target-ip-10-0-137-176: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:32:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T18:59:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-51-to-network-check-target-ip-10-0-139-51 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-51.ec2.internal uid: e81f8bdd-1058-47ef-8331-dadadb0ad371 resourceVersion: "63182" uid: e2355ceb-7883-4bf1-9e67-150a371a502e spec: sourcePod: network-check-source-7bc5b6bf85-qtmwq targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T19:06:53Z" message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.068263ms message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:41:53Z" - latency: 1.010864ms message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:40:53Z" - latency: 1.144888ms message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:39:53Z" - latency: 1.297106ms message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:38:53Z" - latency: 1.0075ms message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:37:53Z" - latency: 967.148µs message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:36:53Z" - latency: 977.476µs message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:35:53Z" - latency: 1.561665ms message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:34:53Z" - latency: 1.073252ms message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:33:53Z" - latency: 961.228µs message: 'network-check-target-ip-10-0-139-51: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:32:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T18:59:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-51-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-51.ec2.internal uid: e81f8bdd-1058-47ef-8331-dadadb0ad371 resourceVersion: "63185" uid: e5838a72-6895-4f1b-a7a5-defcb7eb7a99 spec: sourcePod: network-check-source-7bc5b6bf85-qtmwq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T19:05:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 881.702µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:41:53Z" - latency: 1.86856ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T19:41:53Z" - latency: 1.196378ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:40:53Z" - latency: 1.880264ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T19:40:53Z" - latency: 858.078µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:39:53Z" - latency: 1.792896ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T19:39:53Z" - latency: 999.093µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:38:53Z" - latency: 2.034733ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T19:38:53Z" - latency: 844.571µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T19:37:53Z" - latency: 1.808659ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T19:37:53Z" kind: List metadata: resourceVersion: ""