apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:26:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-165-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-165.ec2.internal uid: a6ee1353-4088-47f5-b865-55ad94826aa0 resourceVersion: "37557" uid: 86a69d5c-3744-45dc-a310-a528db946134 spec: sourcePod: network-check-source-7b678d77c7-v9g5q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T16:33:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.562938ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:54:53Z" - latency: 905.059µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:53:53Z" - latency: 1.018759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:52:53Z" - latency: 943.93µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:51:53Z" - latency: 1.049522ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:50:53Z" - latency: 981.706µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:49:53Z" - latency: 1.086571ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:48:53Z" - latency: 1.038929ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:47:53Z" - latency: 1.334716ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:46:53Z" - latency: 1.308662ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:45:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:26:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-165-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-165.ec2.internal uid: a6ee1353-4088-47f5-b865-55ad94826aa0 resourceVersion: "34281" uid: c5458c71-c5d9-4917-93f9-961167412c52 spec: sourcePod: network-check-source-7b678d77c7-v9g5q targetEndpoint: ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T16:32:53Z" message: 'load-balancer-api-external: tcp connection to ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.244743ms message: 'load-balancer-api-external: tcp connection to ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:50:53Z" - latency: 6.605915ms message: 'load-balancer-api-external: resolved host name ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:50:53Z" - latency: 5.543888ms message: 'load-balancer-api-external: tcp connection to ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:49:53Z" - latency: 6.661181ms message: 'load-balancer-api-external: resolved host name ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:49:53Z" - latency: 5.680825ms message: 'load-balancer-api-external: tcp connection to ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:48:53Z" - latency: 6.846302ms message: 'load-balancer-api-external: resolved host name ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:48:53Z" - latency: 3.549825ms message: 'load-balancer-api-external: tcp connection to ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:47:53Z" - latency: 7.53969ms message: 'load-balancer-api-external: resolved host name ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:47:53Z" - latency: 5.255909ms message: 'load-balancer-api-external: tcp connection to ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:46:53Z" - latency: 6.460281ms message: 'load-balancer-api-external: resolved host name ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:46:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:26:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-165-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-165.ec2.internal uid: a6ee1353-4088-47f5-b865-55ad94826aa0 resourceVersion: "34280" uid: feaee5cb-2831-4dfe-bcb1-a23c1cf8e778 spec: sourcePod: network-check-source-7b678d77c7-v9g5q targetEndpoint: ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T16:32:53Z" message: 'load-balancer-api-internal: tcp connection to ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.261595ms message: 'load-balancer-api-internal: tcp connection to ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:50:53Z" - latency: 6.694531ms message: 'load-balancer-api-internal: resolved host name ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:50:53Z" - latency: 5.448509ms message: 'load-balancer-api-internal: tcp connection to ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:49:53Z" - latency: 6.745656ms message: 'load-balancer-api-internal: resolved host name ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:49:53Z" - latency: 5.672246ms message: 'load-balancer-api-internal: tcp connection to ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:48:53Z" - latency: 6.91939ms message: 'load-balancer-api-internal: resolved host name ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:48:53Z" - latency: 3.520916ms message: 'load-balancer-api-internal: tcp connection to ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:47:53Z" - latency: 7.621466ms message: 'load-balancer-api-internal: resolved host name ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:47:53Z" - latency: 4.34732ms message: 'load-balancer-api-internal: tcp connection to ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:46:53Z" - latency: 6.548854ms message: 'load-balancer-api-internal: resolved host name ab1d0627a8b2e41bf8ff564a13faba14-5bcadcaa4b5b3a2c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T16:46:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:26:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-165-to-network-check-target-ip-10-0-130-165 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-165.ec2.internal uid: a6ee1353-4088-47f5-b865-55ad94826aa0 resourceVersion: "37554" uid: fe172191-835d-47ff-bea7-1b41247a5813 spec: sourcePod: network-check-source-7b678d77c7-v9g5q targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:33:53Z" message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 762.834µs message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:54:53Z" - latency: 859.622µs message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:53:53Z" - latency: 1.003413ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:52:53Z" - latency: 792.94µs message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:51:53Z" - latency: 729.015µs message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:50:53Z" - latency: 1.059198ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:49:53Z" - latency: 1.165146ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:48:53Z" - latency: 1.167704ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:47:53Z" - latency: 865.176µs message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:46:53Z" - latency: 1.424806ms message: 'network-check-target-ip-10-0-130-165: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:45:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:26:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-165-to-network-check-target-ip-10-0-132-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-165.ec2.internal uid: a6ee1353-4088-47f5-b865-55ad94826aa0 resourceVersion: "37555" uid: d8ff8e6d-ae3b-4df0-b74d-326d6c05c080 spec: sourcePod: network-check-source-7b678d77c7-v9g5q targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:33:53Z" message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.134895ms message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:54:53Z" - latency: 2.380853ms message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:53:53Z" - latency: 1.919832ms message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:52:53Z" - latency: 2.178666ms message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:51:53Z" - latency: 2.376478ms message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:50:53Z" - latency: 2.262961ms message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:49:53Z" - latency: 2.570336ms message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:48:53Z" - latency: 2.093617ms message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:47:53Z" - latency: 2.478801ms message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:46:53Z" - latency: 2.595039ms message: 'network-check-target-ip-10-0-132-246: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:45:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:26:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-165-to-network-check-target-ip-10-0-138-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-165.ec2.internal uid: a6ee1353-4088-47f5-b865-55ad94826aa0 resourceVersion: "37556" uid: 16741f4a-8007-4c6c-866b-8bee531943c3 spec: sourcePod: network-check-source-7b678d77c7-v9g5q targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:33:53Z" message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.901307ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:54:53Z" - latency: 2.408046ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:53:53Z" - latency: 2.396645ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:52:53Z" - latency: 2.291161ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:51:53Z" - latency: 2.372506ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:50:53Z" - latency: 2.254767ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:49:53Z" - latency: 2.896542ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:48:53Z" - latency: 2.467261ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:47:53Z" - latency: 2.404476ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:46:53Z" - latency: 2.586399ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:45:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:26:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-165-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-165.ec2.internal uid: a6ee1353-4088-47f5-b865-55ad94826aa0 resourceVersion: "34278" uid: c81dfde3-5531-47d8-a44e-591f40e6ab30 spec: sourcePod: network-check-source-7b678d77c7-v9g5q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T16:32:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 926.067µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:50:53Z" - latency: 2.424409ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T16:50:53Z" - latency: 868.425µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:49:53Z" - latency: 1.718198ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T16:49:53Z" - latency: 809.232µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:48:53Z" - latency: 1.967286ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T16:48:53Z" - latency: 960.489µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:47:53Z" - latency: 2.19555ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T16:47:53Z" - latency: 1.020889ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T16:46:53Z" - latency: 1.725031ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T16:46:53Z" kind: List metadata: resourceVersion: ""