apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:50:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-14-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-14.ec2.internal uid: f1ec3c12-1f2e-4715-825c-8e4263b8789f resourceVersion: "70099" uid: da233a20-da8e-4bc9-987f-8835f83c777e spec: sourcePod: network-check-source-7d88cb55d8-hv4ql targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T20:57:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 956.276µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:39:44Z" - latency: 962.581µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:38:44Z" - latency: 846.59µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:37:44Z" - latency: 1.119015ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:36:44Z" - latency: 1.160542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:35:44Z" - latency: 1.133474ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:34:44Z" - latency: 1.542839ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:33:44Z" - latency: 1.05603ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:32:44Z" - latency: 1.014404ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:31:44Z" - latency: 1.208232ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:30:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:50:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-14-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-14.ec2.internal uid: f1ec3c12-1f2e-4715-825c-8e4263b8789f resourceVersion: "69120" uid: 3ec53b09-ec1d-4b73-a0ff-bdc97e9587e4 spec: sourcePod: network-check-source-7d88cb55d8-hv4ql targetEndpoint: a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T20:56:44Z" message: 'load-balancer-api-external: tcp connection to a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.291933ms message: 'load-balancer-api-external: tcp connection to a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:38:44Z" - latency: 7.315684ms message: 'load-balancer-api-external: resolved host name a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:38:44Z" - latency: 3.883917ms message: 'load-balancer-api-external: tcp connection to a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:37:44Z" - latency: 12.638352ms message: 'load-balancer-api-external: resolved host name a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:37:44Z" - latency: 5.408751ms message: 'load-balancer-api-external: tcp connection to a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:36:44Z" - latency: 7.297522ms message: 'load-balancer-api-external: resolved host name a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:36:44Z" - latency: 3.203026ms message: 'load-balancer-api-external: tcp connection to a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:35:44Z" - latency: 7.08949ms message: 'load-balancer-api-external: resolved host name a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:35:44Z" - latency: 3.060469ms message: 'load-balancer-api-external: tcp connection to a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:34:44Z" - latency: 7.345412ms message: 'load-balancer-api-external: resolved host name a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:34:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:50:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-14-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-14.ec2.internal uid: f1ec3c12-1f2e-4715-825c-8e4263b8789f resourceVersion: "69119" uid: a99c8b14-25cb-4c0b-b855-813ac97f8037 spec: sourcePod: network-check-source-7d88cb55d8-hv4ql targetEndpoint: a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T20:56:44Z" message: 'load-balancer-api-internal: tcp connection to a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.229263ms message: 'load-balancer-api-internal: tcp connection to a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:38:44Z" - latency: 7.290723ms message: 'load-balancer-api-internal: resolved host name a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:38:44Z" - latency: 4.079215ms message: 'load-balancer-api-internal: tcp connection to a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:37:44Z" - latency: 12.535502ms message: 'load-balancer-api-internal: resolved host name a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:37:44Z" - latency: 7.869395ms message: 'load-balancer-api-internal: tcp connection to a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:36:44Z" - latency: 7.224739ms message: 'load-balancer-api-internal: resolved host name a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:36:44Z" - latency: 5.340266ms message: 'load-balancer-api-internal: tcp connection to a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:35:44Z" - latency: 7.034277ms message: 'load-balancer-api-internal: resolved host name a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:35:44Z" - latency: 4.861057ms message: 'load-balancer-api-internal: tcp connection to a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:34:44Z" - latency: 7.292549ms message: 'load-balancer-api-internal: resolved host name a68eea3e874c644df8d9e97f7223ce1e-bb17a0c0f4c56b30.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T21:34:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:50:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-14-to-network-check-target-ip-10-0-133-14 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-14.ec2.internal uid: f1ec3c12-1f2e-4715-825c-8e4263b8789f resourceVersion: "70096" uid: 7283b817-631d-4d9c-ae9c-ec52db5c9d38 spec: sourcePod: network-check-source-7d88cb55d8-hv4ql targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T20:57:44Z" message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 960.426µs message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:39:44Z" - latency: 1.393673ms message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:38:44Z" - latency: 964.676µs message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:37:44Z" - latency: 971.375µs message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:36:44Z" - latency: 853.576µs message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:35:44Z" - latency: 884.247µs message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:34:44Z" - latency: 1.216836ms message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:33:44Z" - latency: 1.656004ms message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:32:44Z" - latency: 1.004055ms message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:31:44Z" - latency: 976.473µs message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:30:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:50:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-14-to-network-check-target-ip-10-0-134-170 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-14.ec2.internal uid: f1ec3c12-1f2e-4715-825c-8e4263b8789f resourceVersion: "70098" uid: 2ef92ed2-efda-4331-a74a-f3402cac9253 spec: sourcePod: network-check-source-7d88cb55d8-hv4ql targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-28T20:57:44Z" message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.95397ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:39:44Z" - latency: 2.179192ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:38:44Z" - latency: 2.64446ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:37:44Z" - latency: 2.474108ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:36:44Z" - latency: 2.267983ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:35:44Z" - latency: 2.279411ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:34:44Z" - latency: 2.37472ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:33:44Z" - latency: 1.938922ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:32:44Z" - latency: 2.550243ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:31:44Z" - latency: 2.425788ms message: 'network-check-target-ip-10-0-134-170: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:30:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:50:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-14-to-network-check-target-ip-10-0-134-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-14.ec2.internal uid: f1ec3c12-1f2e-4715-825c-8e4263b8789f resourceVersion: "70097" uid: 344d7544-c3ad-4445-b3f0-0918bed3ffb5 spec: sourcePod: network-check-source-7d88cb55d8-hv4ql targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T20:57:44Z" message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.259844ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:39:44Z" - latency: 2.312721ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:38:44Z" - latency: 2.253054ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:37:44Z" - latency: 2.443284ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:36:44Z" - latency: 2.008539ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:35:44Z" - latency: 1.998234ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:34:44Z" - latency: 2.163514ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:33:44Z" - latency: 2.468233ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:32:44Z" - latency: 2.180506ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:31:44Z" - latency: 2.41293ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:30:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T20:50:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-14-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-14.ec2.internal uid: f1ec3c12-1f2e-4715-825c-8e4263b8789f resourceVersion: "69118" uid: 67fab957-9277-4b40-a9fe-ceea138b7f54 spec: sourcePod: network-check-source-7d88cb55d8-hv4ql targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T20:56:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.179199ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:38:44Z" - latency: 2.076203ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T21:38:44Z" - latency: 1.122675ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:37:44Z" - latency: 2.004227ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T21:37:44Z" - latency: 845.477µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:36:44Z" - latency: 1.778949ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T21:36:44Z" - latency: 1.008513ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:35:44Z" - latency: 2.087687ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T21:35:44Z" - latency: 1.053235ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T21:34:44Z" - latency: 1.736421ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T21:34:44Z" kind: List metadata: resourceVersion: ""