apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T21:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-173-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-173.ec2.internal uid: da30880e-dd48-4a14-86de-baf27a82e037 resourceVersion: "47980" uid: 072bcb01-c4bc-4fe1-920a-81add9fa916d spec: sourcePod: network-check-source-989f8b8dc-sjsjl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T22:05:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.221161ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:26:55Z" - latency: 796.101µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:25:55Z" - latency: 1.067102ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:24:55Z" - latency: 800.793µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:23:55Z" - latency: 1.144769ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:22:55Z" - latency: 1.067938ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:21:55Z" - latency: 1.154419ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:20:55Z" - latency: 791.807µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:19:55Z" - latency: 1.074322ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:18:55Z" - latency: 934.807µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:17:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T21:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-173-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-173.ec2.internal uid: da30880e-dd48-4a14-86de-baf27a82e037 resourceVersion: "50036" uid: 0505b5b0-2569-48e4-9fce-c81c7ee34a5d spec: sourcePod: network-check-source-989f8b8dc-sjsjl targetEndpoint: a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T22:04:55Z" message: 'load-balancer-api-external: tcp connection to a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.059102ms message: 'load-balancer-api-external: tcp connection to a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:28:55Z" - latency: 9.153388ms message: 'load-balancer-api-external: resolved host name a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:28:55Z" - latency: 5.489332ms message: 'load-balancer-api-external: tcp connection to a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:27:55Z" - latency: 9.558156ms message: 'load-balancer-api-external: resolved host name a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:27:55Z" - latency: 3.91233ms message: 'load-balancer-api-external: tcp connection to a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:26:55Z" - latency: 11.984933ms message: 'load-balancer-api-external: resolved host name a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:26:55Z" - latency: 3.571951ms message: 'load-balancer-api-external: tcp connection to a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:25:55Z" - latency: 10.480691ms message: 'load-balancer-api-external: resolved host name a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:25:55Z" - latency: 5.138879ms message: 'load-balancer-api-external: tcp connection to a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:24:55Z" - latency: 7.918923ms message: 'load-balancer-api-external: resolved host name a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:24:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T21:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-173-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-173.ec2.internal uid: da30880e-dd48-4a14-86de-baf27a82e037 resourceVersion: "50037" uid: 7a5e5c6d-ec93-4909-801d-cf76f7115df2 spec: sourcePod: network-check-source-989f8b8dc-sjsjl targetEndpoint: a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T22:04:55Z" message: 'load-balancer-api-internal: tcp connection to a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.53943ms message: 'load-balancer-api-internal: tcp connection to a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:28:55Z" - latency: 9.248752ms message: 'load-balancer-api-internal: resolved host name a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:28:55Z" - latency: 4.805799ms message: 'load-balancer-api-internal: tcp connection to a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:27:55Z" - latency: 9.552244ms message: 'load-balancer-api-internal: resolved host name a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:27:55Z" - latency: 3.843188ms message: 'load-balancer-api-internal: tcp connection to a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:26:55Z" - latency: 11.968373ms message: 'load-balancer-api-internal: resolved host name a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:26:55Z" - latency: 4.205375ms message: 'load-balancer-api-internal: tcp connection to a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:25:55Z" - latency: 10.459244ms message: 'load-balancer-api-internal: resolved host name a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:25:55Z" - latency: 5.125145ms message: 'load-balancer-api-internal: tcp connection to a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:24:55Z" - latency: 7.940046ms message: 'load-balancer-api-internal: resolved host name a04ba939bf90d442ab81c719bbf32a80-2206dc65900a9d7a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T22:24:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T21:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-173-to-network-check-target-ip-10-0-133-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-173.ec2.internal uid: da30880e-dd48-4a14-86de-baf27a82e037 resourceVersion: "47977" uid: 8f2f88cf-b194-4cbe-a4b4-58f64aa1bf45 spec: sourcePod: network-check-source-989f8b8dc-sjsjl targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T22:05:55Z" message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.056358ms message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:26:55Z" - latency: 751.441µs message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:25:55Z" - latency: 838.079µs message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:24:55Z" - latency: 931.75µs message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:23:55Z" - latency: 1.179785ms message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:22:55Z" - latency: 1.030114ms message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:21:55Z" - latency: 1.076066ms message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:20:55Z" - latency: 984.662µs message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:19:55Z" - latency: 1.278592ms message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:18:55Z" - latency: 850.903µs message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:17:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T21:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-173-to-network-check-target-ip-10-0-141-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-173.ec2.internal uid: da30880e-dd48-4a14-86de-baf27a82e037 resourceVersion: "47978" uid: 40417769-5233-468c-ab6d-18ce6b10a3d6 spec: sourcePod: network-check-source-989f8b8dc-sjsjl targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T22:05:55Z" message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.182691ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:26:55Z" - latency: 2.311161ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:25:55Z" - latency: 2.120203ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:24:55Z" - latency: 2.284705ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:23:55Z" - latency: 2.420487ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:22:55Z" - latency: 2.02856ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:21:55Z" - latency: 2.348381ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:20:55Z" - latency: 2.511289ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:19:55Z" - latency: 2.265117ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:18:55Z" - latency: 1.863073ms message: 'network-check-target-ip-10-0-141-101: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:17:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T21:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-173-to-network-check-target-ip-10-0-143-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-173.ec2.internal uid: da30880e-dd48-4a14-86de-baf27a82e037 resourceVersion: "47979" uid: a9e4d36a-73f3-4399-9335-cf7110d29600 spec: sourcePod: network-check-source-989f8b8dc-sjsjl targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T22:05:55Z" message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.409666ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:26:55Z" - latency: 2.328276ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:25:55Z" - latency: 2.315057ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:24:55Z" - latency: 2.213527ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:23:55Z" - latency: 1.994539ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:22:55Z" - latency: 2.213431ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:21:55Z" - latency: 2.537188ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:20:55Z" - latency: 2.396274ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:19:55Z" - latency: 2.442354ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:18:55Z" - latency: 2.608782ms message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:17:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T21:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-173-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-173.ec2.internal uid: da30880e-dd48-4a14-86de-baf27a82e037 resourceVersion: "50034" uid: 6b686969-fee5-4bcb-a85b-1515a5580727 spec: sourcePod: network-check-source-989f8b8dc-sjsjl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T22:04:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 758.682µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:28:55Z" - latency: 1.905577ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T22:28:55Z" - latency: 1.077375ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:27:55Z" - latency: 1.573097ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T22:27:55Z" - latency: 790.353µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:26:55Z" - latency: 1.82706ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T22:26:55Z" - latency: 1.168689ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:25:55Z" - latency: 1.939373ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T22:25:55Z" - latency: 906.359µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T22:24:55Z" - latency: 1.673783ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T22:24:55Z" kind: List metadata: resourceVersion: ""