apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T08:05:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-117-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-117.ec2.internal uid: 4c27706f-7d79-4112-9cf4-48c1aeb56785 resourceVersion: "32235" uid: b658c967-7d77-4041-9585-89e7b604f862 spec: sourcePod: network-check-source-dbd9cf844-9n9r8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T08:12:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.095927ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:19:42Z" - latency: 1.601797ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:18:42Z" - latency: 1.257653ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:17:42Z" - latency: 983.585µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:16:42Z" - latency: 1.213861ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:15:42Z" - latency: 1.138357ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:14:42Z" - latency: 1.378641ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:13:42Z" - latency: 1.211573ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:12:42Z" - latency: 956.1µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:11:42Z" - latency: 1.112292ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:10:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T08:05:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-117-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-117.ec2.internal uid: 4c27706f-7d79-4112-9cf4-48c1aeb56785 resourceVersion: "35851" uid: 3545077f-c1b3-4c01-8c1f-4c01f3c5c562 spec: sourcePod: network-check-source-dbd9cf844-9n9r8 targetEndpoint: acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T08:11:42Z" message: 'load-balancer-api-external: tcp connection to acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.328244ms message: 'load-balancer-api-external: tcp connection to acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:23:42Z" - latency: 7.361352ms message: 'load-balancer-api-external: resolved host name acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T08:23:42Z" - latency: 4.86448ms message: 'load-balancer-api-external: tcp connection to acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:22:42Z" - latency: 6.927493ms message: 'load-balancer-api-external: resolved host name acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T08:22:42Z" - latency: 4.284329ms message: 'load-balancer-api-external: tcp connection to acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:21:42Z" - latency: 6.647604ms message: 'load-balancer-api-external: resolved host name acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T08:21:42Z" - latency: 4.930397ms message: 'load-balancer-api-external: tcp connection to acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:20:42Z" - latency: 7.474645ms message: 'load-balancer-api-external: resolved host name acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T08:20:42Z" - latency: 9.486263ms message: 'load-balancer-api-external: tcp connection to acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:19:42Z" - latency: 6.365161ms message: 'load-balancer-api-external: resolved host name acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T08:19:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T08:05:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-117-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-117.ec2.internal uid: 4c27706f-7d79-4112-9cf4-48c1aeb56785 resourceVersion: "35852" uid: 59789c16-2f9d-44c1-81e0-cb792460c840 spec: sourcePod: network-check-source-dbd9cf844-9n9r8 targetEndpoint: acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T08:11:42Z" message: 'load-balancer-api-internal: tcp connection to acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.284089ms message: 'load-balancer-api-internal: tcp connection to acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:23:42Z" - latency: 7.335363ms message: 'load-balancer-api-internal: resolved host name acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T08:23:42Z" - latency: 4.895786ms message: 'load-balancer-api-internal: tcp connection to acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:22:42Z" - latency: 6.834104ms message: 'load-balancer-api-internal: resolved host name acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T08:22:42Z" - latency: 4.289941ms message: 'load-balancer-api-internal: tcp connection to acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:21:42Z" - latency: 6.703755ms message: 'load-balancer-api-internal: resolved host name acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T08:21:42Z" - latency: 4.974081ms message: 'load-balancer-api-internal: tcp connection to acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:20:42Z" - latency: 7.492999ms message: 'load-balancer-api-internal: resolved host name acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T08:20:42Z" - latency: 9.427932ms message: 'load-balancer-api-internal: tcp connection to acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:19:42Z" - latency: 6.35565ms message: 'load-balancer-api-internal: resolved host name acf47ed937c8e419e8044c42f391fa6f-ecce97ae9c8a3390.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T08:19:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T08:05:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-117-to-network-check-target-ip-10-0-134-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-117.ec2.internal uid: 4c27706f-7d79-4112-9cf4-48c1aeb56785 resourceVersion: "32233" uid: 87be90ea-fa77-4fbb-a864-ffa9805f4e0a spec: sourcePod: network-check-source-dbd9cf844-9n9r8 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T08:12:42Z" message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 926.326µs message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:19:42Z" - latency: 928.986µs message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:18:42Z" - latency: 860.838µs message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:17:42Z" - latency: 875.938µs message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:16:42Z" - latency: 861.68µs message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:15:42Z" - latency: 938.572µs message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:14:42Z" - latency: 1.599839ms message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:13:42Z" - latency: 963.454µs message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:12:42Z" - latency: 1.086001ms message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:11:42Z" - latency: 892.162µs message: 'network-check-target-ip-10-0-134-117: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:10:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T08:05:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-117-to-network-check-target-ip-10-0-139-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-117.ec2.internal uid: 4c27706f-7d79-4112-9cf4-48c1aeb56785 resourceVersion: "32236" uid: 57f32e92-3809-46f7-a101-6ff4fd75811b spec: sourcePod: network-check-source-dbd9cf844-9n9r8 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T08:12:42Z" message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.216817ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:19:42Z" - latency: 2.084753ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:18:42Z" - latency: 1.958184ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:17:42Z" - latency: 2.375433ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:16:42Z" - latency: 2.11976ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:15:42Z" - latency: 2.330644ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:14:42Z" - latency: 2.298597ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:13:42Z" - latency: 2.058384ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:12:42Z" - latency: 1.747143ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:11:42Z" - latency: 1.862721ms message: 'network-check-target-ip-10-0-139-124: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:10:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T08:05:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-117-to-network-check-target-ip-10-0-141-98 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-117.ec2.internal uid: 4c27706f-7d79-4112-9cf4-48c1aeb56785 resourceVersion: "32234" uid: adc07b03-3b79-429e-8b81-cffe9f3b13c1 spec: sourcePod: network-check-source-dbd9cf844-9n9r8 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T08:12:42Z" message: 'network-check-target-ip-10-0-141-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.706907ms message: 'network-check-target-ip-10-0-141-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:19:42Z" - latency: 2.300922ms message: 'network-check-target-ip-10-0-141-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:18:42Z" - latency: 1.854884ms message: 'network-check-target-ip-10-0-141-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:17:42Z" - latency: 1.88143ms message: 'network-check-target-ip-10-0-141-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:16:42Z" - latency: 1.614039ms message: 'network-check-target-ip-10-0-141-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:15:42Z" - latency: 1.892252ms message: 'network-check-target-ip-10-0-141-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:14:42Z" - latency: 1.967284ms message: 'network-check-target-ip-10-0-141-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:13:42Z" - latency: 2.036868ms message: 'network-check-target-ip-10-0-141-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:12:42Z" - latency: 2.053753ms message: 'network-check-target-ip-10-0-141-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:11:42Z" - latency: 1.969478ms message: 'network-check-target-ip-10-0-141-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:10:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T08:05:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-117-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-117.ec2.internal uid: 4c27706f-7d79-4112-9cf4-48c1aeb56785 resourceVersion: "35849" uid: 35bceb8d-608e-462b-b286-4c4ea7ac4887 spec: sourcePod: network-check-source-dbd9cf844-9n9r8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T08:11:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 922.004µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:23:42Z" - latency: 1.678418ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T08:23:42Z" - latency: 755.053µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:22:42Z" - latency: 2.116443ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T08:22:42Z" - latency: 1.088999ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:21:42Z" - latency: 1.713193ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T08:21:42Z" - latency: 819.145µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:20:42Z" - latency: 2.357853ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T08:20:42Z" - latency: 887.217µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T08:19:42Z" - latency: 1.65855ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T08:19:42Z" kind: List metadata: resourceVersion: ""