apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:14:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-149-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-149.ec2.internal uid: 140c27c5-2493-4ad6-8de1-a581c6a941a8 resourceVersion: "23270" uid: 20cdf9e0-3c6d-44ce-bbaf-742f97ed7972 spec: sourcePod: network-check-source-685456655f-mnn2h targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-09T20:21:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.5646ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:35:02Z" - latency: 1.05612ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:34:02Z" - latency: 1.134095ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:33:02Z" - latency: 1.415835ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:32:02Z" - latency: 929.338µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:31:02Z" - latency: 1.142199ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:30:02Z" - latency: 1.763975ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:29:02Z" - latency: 1.057862ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:28:02Z" - latency: 1.13681ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:27:02Z" - latency: 926.726µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:26:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:14:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-149-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-149.ec2.internal uid: 140c27c5-2493-4ad6-8de1-a581c6a941a8 resourceVersion: "24695" uid: 327cf921-2ba4-4077-bf34-df4492d2ada2 spec: sourcePod: network-check-source-685456655f-mnn2h targetEndpoint: ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T20:20:02Z" message: 'load-balancer-api-external: tcp connection to ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.514797ms message: 'load-balancer-api-external: tcp connection to ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:38:02Z" - latency: 8.100175ms message: 'load-balancer-api-external: resolved host name ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:38:02Z" - latency: 3.856277ms message: 'load-balancer-api-external: tcp connection to ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:37:02Z" - latency: 8.599313ms message: 'load-balancer-api-external: resolved host name ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:37:02Z" - latency: 4.201792ms message: 'load-balancer-api-external: tcp connection to ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:36:02Z" - latency: 15.943162ms message: 'load-balancer-api-external: resolved host name ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:36:02Z" - latency: 4.537403ms message: 'load-balancer-api-external: tcp connection to ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:35:02Z" - latency: 8.407651ms message: 'load-balancer-api-external: resolved host name ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:35:02Z" - latency: 6.402617ms message: 'load-balancer-api-external: tcp connection to ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:34:02Z" - latency: 7.900759ms message: 'load-balancer-api-external: resolved host name ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:34:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:14:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-149-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-149.ec2.internal uid: 140c27c5-2493-4ad6-8de1-a581c6a941a8 resourceVersion: "24694" uid: b468992f-54f8-4097-9baf-a3e91e4540b1 spec: sourcePod: network-check-source-685456655f-mnn2h targetEndpoint: ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T20:20:02Z" message: 'load-balancer-api-internal: tcp connection to ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.894752ms message: 'load-balancer-api-internal: tcp connection to ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:38:02Z" - latency: 7.972158ms message: 'load-balancer-api-internal: resolved host name ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:38:02Z" - latency: 4.325003ms message: 'load-balancer-api-internal: tcp connection to ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:37:02Z" - latency: 8.537052ms message: 'load-balancer-api-internal: resolved host name ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:37:02Z" - latency: 4.012576ms message: 'load-balancer-api-internal: tcp connection to ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:36:02Z" - latency: 15.84755ms message: 'load-balancer-api-internal: resolved host name ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:36:02Z" - latency: 4.549765ms message: 'load-balancer-api-internal: tcp connection to ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:35:02Z" - latency: 8.282187ms message: 'load-balancer-api-internal: resolved host name ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:35:02Z" - latency: 6.397984ms message: 'load-balancer-api-internal: tcp connection to ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:34:02Z" - latency: 7.796001ms message: 'load-balancer-api-internal: resolved host name ad8b4d786bd174f0d81fc7977946bd65-6d4e79db73a135b1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T20:34:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:14:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-149-to-network-check-target-ip-10-0-132-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-149.ec2.internal uid: 140c27c5-2493-4ad6-8de1-a581c6a941a8 resourceVersion: "23269" uid: 7923379a-17dc-4e24-a5f7-449446582ee2 spec: sourcePod: network-check-source-685456655f-mnn2h targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:21:02Z" message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.03986ms message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:35:02Z" - latency: 2.143495ms message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:34:02Z" - latency: 2.176318ms message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:33:02Z" - latency: 2.427953ms message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:32:02Z" - latency: 2.197719ms message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:31:02Z" - latency: 2.116065ms message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:30:02Z" - latency: 2.596649ms message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:29:02Z" - latency: 2.189332ms message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:28:02Z" - latency: 2.29088ms message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:27:02Z" - latency: 2.090995ms message: 'network-check-target-ip-10-0-132-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:26:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:14:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-149-to-network-check-target-ip-10-0-143-149 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-149.ec2.internal uid: 140c27c5-2493-4ad6-8de1-a581c6a941a8 resourceVersion: "23267" uid: 43672421-dbdf-4693-adb9-6a193ac5f95e spec: sourcePod: network-check-source-685456655f-mnn2h targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:21:02Z" message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 914.198µs message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:35:02Z" - latency: 749.025µs message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:34:02Z" - latency: 1.192109ms message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:33:02Z" - latency: 1.671905ms message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:32:02Z" - latency: 839.343µs message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:31:02Z" - latency: 811.437µs message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:30:02Z" - latency: 1.779263ms message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:29:02Z" - latency: 959.911µs message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:28:02Z" - latency: 999.989µs message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:27:02Z" - latency: 878.339µs message: 'network-check-target-ip-10-0-143-149: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:26:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:14:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-149-to-network-check-target-ip-10-0-143-188 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-149.ec2.internal uid: 140c27c5-2493-4ad6-8de1-a581c6a941a8 resourceVersion: "23268" uid: 67f86e56-8bd6-409b-a0e5-0629f5bf7001 spec: sourcePod: network-check-source-685456655f-mnn2h targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T20:21:02Z" message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.026948ms message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:35:02Z" - latency: 2.049971ms message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:34:02Z" - latency: 2.2309ms message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:33:02Z" - latency: 2.021531ms message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:32:02Z" - latency: 2.259793ms message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:31:02Z" - latency: 2.396019ms message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:30:02Z" - latency: 2.108794ms message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:29:02Z" - latency: 2.202961ms message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:28:02Z" - latency: 2.187379ms message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:27:02Z" - latency: 1.826486ms message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:26:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:14:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-149-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-149.ec2.internal uid: 140c27c5-2493-4ad6-8de1-a581c6a941a8 resourceVersion: "24693" uid: ecb0c330-af32-408e-b3d9-805b3802075e spec: sourcePod: network-check-source-685456655f-mnn2h targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-09T20:20:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.154725ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:38:02Z" - latency: 1.719869ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:38:02Z" - latency: 769.918µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:37:02Z" - latency: 1.746768ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:37:02Z" - latency: 903.097µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:36:02Z" - latency: 2.287775ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:36:02Z" - latency: 811.73µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:35:02Z" - latency: 2.111765ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:35:02Z" - latency: 900.389µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T20:34:02Z" - latency: 1.748197ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T20:34:02Z" kind: List metadata: resourceVersion: ""