apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T18:07:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-194-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-194.ec2.internal uid: ef9ff7c7-936e-4b6a-b1e6-29f04d99b88c resourceVersion: "45191" uid: b8899b87-4dfb-4788-9984-8cbae22cb6a5 spec: sourcePod: network-check-source-dbd9cf844-9rr6l targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-05T18:14:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.012519ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:35:29Z" - latency: 902.896µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:34:29Z" - latency: 907.037µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:33:29Z" - latency: 1.199743ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:32:29Z" - latency: 804.5µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:31:29Z" - latency: 974.468µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:30:29Z" - latency: 689.702µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:29:29Z" - latency: 741.038µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:28:29Z" - latency: 1.280029ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:27:29Z" - latency: 1.211531ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:26:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T18:07:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-194-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-194.ec2.internal uid: ef9ff7c7-936e-4b6a-b1e6-29f04d99b88c resourceVersion: "47176" uid: dd62bc13-d840-4967-bc63-0cd4e44abd8b spec: sourcePod: network-check-source-dbd9cf844-9rr6l targetEndpoint: a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T18:13:29Z" message: 'load-balancer-api-external: tcp connection to a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.02837ms message: 'load-balancer-api-external: tcp connection to a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:37:29Z" - latency: 6.611627ms message: 'load-balancer-api-external: resolved host name a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:37:29Z" - latency: 5.840124ms message: 'load-balancer-api-external: tcp connection to a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:36:29Z" - latency: 6.874332ms message: 'load-balancer-api-external: resolved host name a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:36:29Z" - latency: 5.651828ms message: 'load-balancer-api-external: tcp connection to a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:35:29Z" - latency: 6.497022ms message: 'load-balancer-api-external: resolved host name a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:35:29Z" - latency: 5.696462ms message: 'load-balancer-api-external: tcp connection to a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:34:29Z" - latency: 6.452307ms message: 'load-balancer-api-external: resolved host name a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:34:29Z" - latency: 5.050942ms message: 'load-balancer-api-external: tcp connection to a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:33:29Z" - latency: 6.344289ms message: 'load-balancer-api-external: resolved host name a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:33:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T18:07:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-194-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-194.ec2.internal uid: ef9ff7c7-936e-4b6a-b1e6-29f04d99b88c resourceVersion: "47177" uid: dd79bdeb-c6d3-461b-b201-620e46e4fca8 spec: sourcePod: network-check-source-dbd9cf844-9rr6l targetEndpoint: a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T18:13:29Z" message: 'load-balancer-api-internal: tcp connection to a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.008853ms message: 'load-balancer-api-internal: tcp connection to a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:37:29Z" - latency: 6.654776ms message: 'load-balancer-api-internal: resolved host name a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:37:29Z" - latency: 5.853785ms message: 'load-balancer-api-internal: tcp connection to a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:36:29Z" - latency: 6.813914ms message: 'load-balancer-api-internal: resolved host name a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:36:29Z" - latency: 5.658154ms message: 'load-balancer-api-internal: tcp connection to a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:35:29Z" - latency: 6.585519ms message: 'load-balancer-api-internal: resolved host name a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:35:29Z" - latency: 5.652649ms message: 'load-balancer-api-internal: tcp connection to a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:34:29Z" - latency: 6.481036ms message: 'load-balancer-api-internal: resolved host name a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:34:29Z" - latency: 6.273414ms message: 'load-balancer-api-internal: tcp connection to a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:33:29Z" - latency: 6.422209ms message: 'load-balancer-api-internal: resolved host name a30802dedb6d44459bc0669b1a2bd093-b5f641ef372ca28a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:33:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T18:07:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-194-to-network-check-target-ip-10-0-137-194 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-194.ec2.internal uid: ef9ff7c7-936e-4b6a-b1e6-29f04d99b88c resourceVersion: "45188" uid: f09b29f0-9e5a-47e8-9853-cdbe976bb53f spec: sourcePod: network-check-source-dbd9cf844-9rr6l targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T18:14:29Z" message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.067584ms message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:35:29Z" - latency: 789.039µs message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:34:29Z" - latency: 811.117µs message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:33:29Z" - latency: 1.441978ms message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:32:29Z" - latency: 1.050696ms message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:31:29Z" - latency: 847.592µs message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:30:29Z" - latency: 1.370565ms message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:29:29Z" - latency: 774.294µs message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:28:29Z" - latency: 900.412µs message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:27:29Z" - latency: 817.611µs message: 'network-check-target-ip-10-0-137-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:26:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T18:07:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-194-to-network-check-target-ip-10-0-142-78 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-194.ec2.internal uid: ef9ff7c7-936e-4b6a-b1e6-29f04d99b88c resourceVersion: "45189" uid: 02ced04e-3ec3-499d-bd64-dfd40394cc2d spec: sourcePod: network-check-source-dbd9cf844-9rr6l targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-05T18:14:29Z" message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.050136ms message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:35:29Z" - latency: 1.898678ms message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:34:29Z" - latency: 1.923096ms message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:33:29Z" - latency: 1.978794ms message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:32:29Z" - latency: 1.768113ms message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:31:29Z" - latency: 1.660948ms message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:30:29Z" - latency: 2.105152ms message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:29:29Z" - latency: 1.899858ms message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:28:29Z" - latency: 1.970343ms message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:27:29Z" - latency: 1.821391ms message: 'network-check-target-ip-10-0-142-78: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:26:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T18:07:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-194-to-network-check-target-ip-10-0-143-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-194.ec2.internal uid: ef9ff7c7-936e-4b6a-b1e6-29f04d99b88c resourceVersion: "45190" uid: 3ed75e34-84cd-4445-aa88-88b44c7b6174 spec: sourcePod: network-check-source-dbd9cf844-9rr6l targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T18:14:29Z" message: 'network-check-target-ip-10-0-143-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.040497ms message: 'network-check-target-ip-10-0-143-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:35:29Z" - latency: 1.611239ms message: 'network-check-target-ip-10-0-143-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:34:29Z" - latency: 1.883434ms message: 'network-check-target-ip-10-0-143-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:33:29Z" - latency: 1.76113ms message: 'network-check-target-ip-10-0-143-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:32:29Z" - latency: 1.632183ms message: 'network-check-target-ip-10-0-143-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:31:29Z" - latency: 1.596714ms message: 'network-check-target-ip-10-0-143-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:30:29Z" - latency: 1.857643ms message: 'network-check-target-ip-10-0-143-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:29:29Z" - latency: 1.85121ms message: 'network-check-target-ip-10-0-143-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:28:29Z" - latency: 1.681952ms message: 'network-check-target-ip-10-0-143-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:27:29Z" - latency: 1.697966ms message: 'network-check-target-ip-10-0-143-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:26:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T18:07:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-194-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-194.ec2.internal uid: ef9ff7c7-936e-4b6a-b1e6-29f04d99b88c resourceVersion: "47175" uid: fe4c3d5d-5d24-4a92-ab08-4b8fb0d36446 spec: sourcePod: network-check-source-dbd9cf844-9rr6l targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-05T18:13:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 816.473µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:37:29Z" - latency: 2.061084ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T18:37:29Z" - latency: 869.604µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:36:29Z" - latency: 1.723402ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T18:36:29Z" - latency: 919.084µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:35:29Z" - latency: 2.107584ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T18:35:29Z" - latency: 958.793µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:34:29Z" - latency: 1.644129ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T18:34:29Z" - latency: 727.771µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:33:29Z" - latency: 1.61916ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T18:33:29Z" kind: List metadata: resourceVersion: ""