apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:57:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-83-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-83.ec2.internal uid: 7104e745-2272-4170-8739-14604609a5a9 resourceVersion: "32727" uid: bd8d048e-3fdf-4628-8d5a-14bd9ec78a89 spec: sourcePod: network-check-source-7d88cb55d8-gbqpx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T13:04:49Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.389417ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:39:49Z" - latency: 1.201695ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:38:49Z" - latency: 934.264µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:37:49Z" - latency: 1.371284ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:36:49Z" - latency: 989.372µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:35:49Z" - latency: 1.221696ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:34:49Z" - latency: 1.140093ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:33:49Z" - latency: 2.013513ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:32:49Z" - latency: 1.009895ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:31:49Z" - latency: 968.638µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:30:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:57:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-83-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-83.ec2.internal uid: 7104e745-2272-4170-8739-14604609a5a9 resourceVersion: "32728" uid: df6ff90b-464f-47c4-a31b-998a4ba55f60 spec: sourcePod: network-check-source-7d88cb55d8-gbqpx targetEndpoint: a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T13:03:49Z" message: 'load-balancer-api-external: tcp connection to a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.991665ms message: 'load-balancer-api-external: tcp connection to a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:39:49Z" - latency: 9.851023ms message: 'load-balancer-api-external: resolved host name a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:39:49Z" - latency: 4.918647ms message: 'load-balancer-api-external: tcp connection to a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:38:49Z" - latency: 8.562621ms message: 'load-balancer-api-external: resolved host name a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:38:49Z" - latency: 4.70975ms message: 'load-balancer-api-external: tcp connection to a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:37:49Z" - latency: 8.409296ms message: 'load-balancer-api-external: resolved host name a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:37:49Z" - latency: 5.031423ms message: 'load-balancer-api-external: tcp connection to a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:36:49Z" - latency: 10.594525ms message: 'load-balancer-api-external: resolved host name a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:36:49Z" - latency: 5.893002ms message: 'load-balancer-api-external: tcp connection to a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:35:49Z" - latency: 8.435337ms message: 'load-balancer-api-external: resolved host name a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:35:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:57:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-83-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-83.ec2.internal uid: 7104e745-2272-4170-8739-14604609a5a9 resourceVersion: "32729" uid: 551bddeb-48bc-49d3-8023-179cc2a085f3 spec: sourcePod: network-check-source-7d88cb55d8-gbqpx targetEndpoint: a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T13:03:49Z" message: 'load-balancer-api-internal: tcp connection to a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.948187ms message: 'load-balancer-api-internal: tcp connection to a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:39:49Z" - latency: 9.881586ms message: 'load-balancer-api-internal: resolved host name a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:39:49Z" - latency: 4.936386ms message: 'load-balancer-api-internal: tcp connection to a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:38:49Z" - latency: 8.586364ms message: 'load-balancer-api-internal: resolved host name a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:38:49Z" - latency: 6.653811ms message: 'load-balancer-api-internal: tcp connection to a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:37:49Z" - latency: 8.447462ms message: 'load-balancer-api-internal: resolved host name a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:37:49Z" - latency: 5.063874ms message: 'load-balancer-api-internal: tcp connection to a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:36:49Z" - latency: 10.6303ms message: 'load-balancer-api-internal: resolved host name a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:36:49Z" - latency: 5.862716ms message: 'load-balancer-api-internal: tcp connection to a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:35:49Z" - latency: 8.482629ms message: 'load-balancer-api-internal: resolved host name a8270be37693043b592324c250e83a42-01f51b489b2b5514.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T13:35:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:57:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-83-to-network-check-target-ip-10-0-132-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-83.ec2.internal uid: 7104e745-2272-4170-8739-14604609a5a9 resourceVersion: "32724" uid: 1cd9c473-2828-4e7e-bcb2-9cbddc8dca09 spec: sourcePod: network-check-source-7d88cb55d8-gbqpx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T13:04:49Z" message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.442573ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:39:49Z" - latency: 2.318382ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:38:49Z" - latency: 2.463698ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:37:49Z" - latency: 2.661233ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:36:49Z" - latency: 2.387956ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:35:49Z" - latency: 2.4269ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:34:49Z" - latency: 2.299013ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:33:49Z" - latency: 2.673773ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:32:49Z" - latency: 2.384405ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:31:49Z" - latency: 2.368307ms message: 'network-check-target-ip-10-0-132-6: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:30:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:57:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-83-to-network-check-target-ip-10-0-135-149 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-83.ec2.internal uid: 7104e745-2272-4170-8739-14604609a5a9 resourceVersion: "32725" uid: 9c73c643-077a-4973-8272-7ba13c59a5a5 spec: sourcePod: network-check-source-7d88cb55d8-gbqpx targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T13:04:49Z" message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.489284ms message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:39:49Z" - latency: 2.386917ms message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:38:49Z" - latency: 2.22877ms message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:37:49Z" - latency: 2.674647ms message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:36:49Z" - latency: 2.464426ms message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:35:49Z" - latency: 2.475983ms message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:34:49Z" - latency: 2.811478ms message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:33:49Z" - latency: 2.842757ms message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:32:49Z" - latency: 2.591367ms message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:31:49Z" - latency: 2.214293ms message: 'network-check-target-ip-10-0-135-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:30:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:57:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-83-to-network-check-target-ip-10-0-142-83 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-83.ec2.internal uid: 7104e745-2272-4170-8739-14604609a5a9 resourceVersion: "32723" uid: ec51b01e-0895-4ada-bbd8-55acf05da83e spec: sourcePod: network-check-source-7d88cb55d8-gbqpx targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T13:04:49Z" message: 'network-check-target-ip-10-0-142-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.60398ms message: 'network-check-target-ip-10-0-142-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:39:49Z" - latency: 1.274387ms message: 'network-check-target-ip-10-0-142-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:38:49Z" - latency: 986.85µs message: 'network-check-target-ip-10-0-142-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:37:49Z" - latency: 1.566345ms message: 'network-check-target-ip-10-0-142-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:36:49Z" - latency: 1.687529ms message: 'network-check-target-ip-10-0-142-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:35:49Z" - latency: 1.344223ms message: 'network-check-target-ip-10-0-142-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:34:49Z" - latency: 848.723µs message: 'network-check-target-ip-10-0-142-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:33:49Z" - latency: 1.133111ms message: 'network-check-target-ip-10-0-142-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:32:49Z" - latency: 1.284572ms message: 'network-check-target-ip-10-0-142-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:31:49Z" - latency: 1.063686ms message: 'network-check-target-ip-10-0-142-83: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:30:49Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T12:57:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-83-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-83.ec2.internal uid: 7104e745-2272-4170-8739-14604609a5a9 resourceVersion: "32726" uid: b5e8c02d-0c49-497f-91c7-a9b9c547ab1b spec: sourcePod: network-check-source-7d88cb55d8-gbqpx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T13:03:49Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.447477ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:39:49Z" - latency: 2.002667ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T13:39:49Z" - latency: 1.258544ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:38:49Z" - latency: 1.81313ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T13:38:49Z" - latency: 958.987µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:37:49Z" - latency: 1.884675ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T13:37:49Z" - latency: 894.307µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:36:49Z" - latency: 1.978984ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T13:36:49Z" - latency: 1.46438ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T13:35:49Z" - latency: 2.097667ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T13:35:49Z" kind: List metadata: resourceVersion: ""