apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T10:10:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-1-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-1.ec2.internal uid: 44ae5c1f-0606-4b00-8400-18f3eecb1c55 resourceVersion: "45608" uid: 41d4ea12-30d5-4dc0-9119-b49cffadbaa4 spec: sourcePod: network-check-source-dbd9cf844-ltr5f targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T10:17:10Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 923.677µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:38:10Z" - latency: 868.983µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:37:10Z" - latency: 1.270613ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:36:10Z" - latency: 1.124808ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:35:10Z" - latency: 788.992µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:34:10Z" - latency: 1.313535ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:33:10Z" - latency: 911.985µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:32:10Z" - latency: 872.868µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:31:10Z" - latency: 1.415329ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:30:10Z" - latency: 1.05916ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:29:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T10:10:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-1-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-1.ec2.internal uid: 44ae5c1f-0606-4b00-8400-18f3eecb1c55 resourceVersion: "47642" uid: 876db79a-faf4-4868-973a-504161f75eef spec: sourcePod: network-check-source-dbd9cf844-ltr5f targetEndpoint: a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T10:16:10Z" message: 'load-balancer-api-external: tcp connection to a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.600355ms message: 'load-balancer-api-external: tcp connection to a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:40:10Z" - latency: 8.788227ms message: 'load-balancer-api-external: resolved host name a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:40:10Z" - latency: 4.557647ms message: 'load-balancer-api-external: tcp connection to a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:39:10Z" - latency: 8.916381ms message: 'load-balancer-api-external: resolved host name a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:39:10Z" - latency: 6.006034ms message: 'load-balancer-api-external: tcp connection to a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:38:10Z" - latency: 8.558639ms message: 'load-balancer-api-external: resolved host name a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:38:10Z" - latency: 4.0232ms message: 'load-balancer-api-external: tcp connection to a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:37:10Z" - latency: 8.639909ms message: 'load-balancer-api-external: resolved host name a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:37:10Z" - latency: 3.865441ms message: 'load-balancer-api-external: tcp connection to a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:36:10Z" - latency: 9.327067ms message: 'load-balancer-api-external: resolved host name a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:36:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T10:10:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-1-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-1.ec2.internal uid: 44ae5c1f-0606-4b00-8400-18f3eecb1c55 resourceVersion: "47643" uid: 0a716195-085d-466f-8608-5df9588d5bda spec: sourcePod: network-check-source-dbd9cf844-ltr5f targetEndpoint: a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T10:16:10Z" message: 'load-balancer-api-internal: tcp connection to a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.458121ms message: 'load-balancer-api-internal: tcp connection to a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:40:10Z" - latency: 8.730277ms message: 'load-balancer-api-internal: resolved host name a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:40:10Z" - latency: 4.276279ms message: 'load-balancer-api-internal: tcp connection to a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:39:10Z" - latency: 8.927859ms message: 'load-balancer-api-internal: resolved host name a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:39:10Z" - latency: 6.074201ms message: 'load-balancer-api-internal: tcp connection to a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:38:10Z" - latency: 8.471004ms message: 'load-balancer-api-internal: resolved host name a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:38:10Z" - latency: 3.650409ms message: 'load-balancer-api-internal: tcp connection to a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:37:10Z" - latency: 8.667181ms message: 'load-balancer-api-internal: resolved host name a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:37:10Z" - latency: 4.957649ms message: 'load-balancer-api-internal: tcp connection to a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:36:10Z" - latency: 9.065079ms message: 'load-balancer-api-internal: resolved host name a7983a7d27a2d45fc87b9792bed2871f-e70a1020a3c16217.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T10:36:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T10:10:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-1-to-network-check-target-ip-10-0-137-128 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-1.ec2.internal uid: 44ae5c1f-0606-4b00-8400-18f3eecb1c55 resourceVersion: "45606" uid: 09c0f95b-ca1d-4a63-ab71-f950c1f63bdb spec: sourcePod: network-check-source-dbd9cf844-ltr5f targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T10:17:10Z" message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.023767ms message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:38:10Z" - latency: 2.285027ms message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:37:10Z" - latency: 2.139698ms message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:36:10Z" - latency: 2.308001ms message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:35:10Z" - latency: 1.989107ms message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:34:10Z" - latency: 1.978048ms message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:33:10Z" - latency: 2.661485ms message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:32:10Z" - latency: 2.042498ms message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:31:10Z" - latency: 2.165854ms message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:30:10Z" - latency: 2.255832ms message: 'network-check-target-ip-10-0-137-128: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:29:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T10:10:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-1-to-network-check-target-ip-10-0-137-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-1.ec2.internal uid: 44ae5c1f-0606-4b00-8400-18f3eecb1c55 resourceVersion: "45607" uid: 2fed32d9-d4bd-4f65-83e9-76307a362556 spec: sourcePod: network-check-source-dbd9cf844-ltr5f targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T10:17:10Z" message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.045881ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:38:10Z" - latency: 2.298286ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:37:10Z" - latency: 2.164029ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:36:10Z" - latency: 2.41948ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:35:10Z" - latency: 2.111957ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:34:10Z" - latency: 1.981101ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:33:10Z" - latency: 2.223407ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:32:10Z" - latency: 2.23056ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:31:10Z" - latency: 2.278657ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:30:10Z" - latency: 2.592647ms message: 'network-check-target-ip-10-0-137-68: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:29:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T10:10:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-1-to-network-check-target-ip-10-0-141-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-1.ec2.internal uid: 44ae5c1f-0606-4b00-8400-18f3eecb1c55 resourceVersion: "45605" uid: bc057ec5-4986-49f8-afeb-6c71ce674dba spec: sourcePod: network-check-source-dbd9cf844-ltr5f targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T10:17:10Z" message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 985.084µs message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:38:10Z" - latency: 784.742µs message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:37:10Z" - latency: 740.982µs message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:36:10Z" - latency: 773.066µs message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:35:10Z" - latency: 1.213999ms message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:34:10Z" - latency: 1.595708ms message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:33:10Z" - latency: 880.301µs message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:32:10Z" - latency: 808.445µs message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:31:10Z" - latency: 1.533829ms message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:30:10Z" - latency: 1.050982ms message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:29:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T10:10:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-1-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-1.ec2.internal uid: 44ae5c1f-0606-4b00-8400-18f3eecb1c55 resourceVersion: "47640" uid: a9a5ec57-f53a-4fe7-8d2a-abeee1ad7966 spec: sourcePod: network-check-source-dbd9cf844-ltr5f targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T10:16:10Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.140611ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:40:10Z" - latency: 2.000244ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T10:40:10Z" - latency: 786.581µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:39:10Z" - latency: 1.822178ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T10:39:10Z" - latency: 1.100865ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:38:10Z" - latency: 1.789386ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T10:38:10Z" - latency: 1.269344ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:37:10Z" - latency: 1.636541ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T10:37:10Z" - latency: 880.6µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T10:36:10Z" - latency: 2.473859ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T10:36:10Z" kind: List metadata: resourceVersion: ""