apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T21:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-209-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-209.ec2.internal uid: 079f8799-0eee-49c6-9039-34ccc36dc851 resourceVersion: "67865" uid: b3fae813-8f89-49e0-99e1-f0564957f52b spec: sourcePod: network-check-source-6f8b768455-c4ckq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-16T21:32:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.199226ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T22:00:06Z" - latency: 878.12µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:59:06Z" - latency: 1.367779ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:58:06Z" - latency: 1.395711ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:57:06Z" - latency: 1.280363ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:56:06Z" - latency: 1.179708ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:55:06Z" - latency: 940.941µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:54:06Z" - latency: 801.511µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:53:06Z" - latency: 1.747596ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:52:06Z" - latency: 1.617478ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:51:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T21:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-209-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-209.ec2.internal uid: 079f8799-0eee-49c6-9039-34ccc36dc851 resourceVersion: "68948" uid: 4546e8e1-0aa4-4d97-ad87-ff63737cb121 spec: sourcePod: network-check-source-6f8b768455-c4ckq targetEndpoint: a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T21:31:06Z" message: 'load-balancer-api-external: tcp connection to a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.122449ms message: 'load-balancer-api-external: tcp connection to a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T22:01:06Z" - latency: 13.543972ms message: 'load-balancer-api-external: resolved host name a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T22:01:06Z" - latency: 4.736728ms message: 'load-balancer-api-external: tcp connection to a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T22:00:06Z" - latency: 10.782293ms message: 'load-balancer-api-external: resolved host name a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T22:00:06Z" - latency: 4.496277ms message: 'load-balancer-api-external: tcp connection to a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:59:06Z" - latency: 11.440283ms message: 'load-balancer-api-external: resolved host name a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T21:59:06Z" - latency: 3.326417ms message: 'load-balancer-api-external: tcp connection to a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:58:06Z" - latency: 14.173313ms message: 'load-balancer-api-external: resolved host name a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T21:58:06Z" - latency: 4.09227ms message: 'load-balancer-api-external: tcp connection to a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:57:06Z" - latency: 16.52489ms message: 'load-balancer-api-external: resolved host name a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T21:57:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T21:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-209-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-209.ec2.internal uid: 079f8799-0eee-49c6-9039-34ccc36dc851 resourceVersion: "68947" uid: b557febc-821f-4129-8032-8c340b17905d spec: sourcePod: network-check-source-6f8b768455-c4ckq targetEndpoint: a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T21:31:06Z" message: 'load-balancer-api-internal: tcp connection to a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.149555ms message: 'load-balancer-api-internal: tcp connection to a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T22:01:06Z" - latency: 13.525431ms message: 'load-balancer-api-internal: resolved host name a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T22:01:06Z" - latency: 4.81931ms message: 'load-balancer-api-internal: tcp connection to a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T22:00:06Z" - latency: 10.6482ms message: 'load-balancer-api-internal: resolved host name a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T22:00:06Z" - latency: 4.438939ms message: 'load-balancer-api-internal: tcp connection to a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:59:06Z" - latency: 11.481322ms message: 'load-balancer-api-internal: resolved host name a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T21:59:06Z" - latency: 3.290476ms message: 'load-balancer-api-internal: tcp connection to a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:58:06Z" - latency: 14.073181ms message: 'load-balancer-api-internal: resolved host name a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T21:58:06Z" - latency: 5.499227ms message: 'load-balancer-api-internal: tcp connection to a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:57:06Z" - latency: 16.543942ms message: 'load-balancer-api-internal: resolved host name a47d90606290c46d2b07f2eaa603dd46-0b5c15596639b075.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T21:57:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T21:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-209-to-network-check-target-ip-10-0-135-209 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-209.ec2.internal uid: 079f8799-0eee-49c6-9039-34ccc36dc851 resourceVersion: "67862" uid: 2fdabf4d-6c2b-49d2-a089-20f2aec87e48 spec: sourcePod: network-check-source-6f8b768455-c4ckq targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-16T21:32:06Z" message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 972.136µs message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T22:00:06Z" - latency: 1.598942ms message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:59:06Z" - latency: 1.558534ms message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:58:06Z" - latency: 1.202852ms message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:57:06Z" - latency: 857.562µs message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:56:06Z" - latency: 889.184µs message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:55:06Z" - latency: 1.031458ms message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:54:06Z" - latency: 1.064878ms message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:53:06Z" - latency: 1.029674ms message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:52:06Z" - latency: 1.222368ms message: 'network-check-target-ip-10-0-135-209: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:51:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T21:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-209-to-network-check-target-ip-10-0-136-118 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-209.ec2.internal uid: 079f8799-0eee-49c6-9039-34ccc36dc851 resourceVersion: "67864" uid: 916e699a-6dd8-4fa0-86c6-9547a43e1a3a spec: sourcePod: network-check-source-6f8b768455-c4ckq targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-16T21:32:06Z" message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.116192ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T22:00:06Z" - latency: 1.733199ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:59:06Z" - latency: 1.975534ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:58:06Z" - latency: 1.856661ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:57:06Z" - latency: 2.175184ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:56:06Z" - latency: 2.041346ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:55:06Z" - latency: 2.265591ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:54:06Z" - latency: 1.87673ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:53:06Z" - latency: 2.16698ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:52:06Z" - latency: 2.269989ms message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:51:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T21:25:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-209-to-network-check-target-ip-10-0-140-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-209.ec2.internal uid: 079f8799-0eee-49c6-9039-34ccc36dc851 resourceVersion: "67863" uid: 4478763d-ed0f-41fe-a8be-9e72ad066c8d spec: sourcePod: network-check-source-6f8b768455-c4ckq targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-16T21:32:06Z" message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.107443ms message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T22:00:06Z" - latency: 2.288152ms message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:59:06Z" - latency: 2.461647ms message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:58:06Z" - latency: 1.931268ms message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:57:06Z" - latency: 2.079426ms message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:56:06Z" - latency: 2.200946ms message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:55:06Z" - latency: 2.263775ms message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:54:06Z" - latency: 2.010264ms message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:53:06Z" - latency: 2.116712ms message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:52:06Z" - latency: 2.600374ms message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:51:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T21:25:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-209-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-209.ec2.internal uid: 079f8799-0eee-49c6-9039-34ccc36dc851 resourceVersion: "68946" uid: 0e5c65fc-8e99-4b37-985f-2e4b90f32dec spec: sourcePod: network-check-source-6f8b768455-c4ckq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-16T21:31:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 966.501µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T22:01:06Z" - latency: 1.826993ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T22:01:06Z" - latency: 818.717µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T22:00:06Z" - latency: 2.388622ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T22:00:06Z" - latency: 908.767µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:59:06Z" - latency: 2.065695ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T21:59:06Z" - latency: 1.057705ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:58:06Z" - latency: 1.883154ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T21:58:06Z" - latency: 996.958µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T21:57:06Z" - latency: 2.046787ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T21:57:06Z" kind: List metadata: resourceVersion: ""