apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:03:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-57-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-57.ec2.internal uid: 01d64e65-0ef6-4c9b-b4c6-96d2aab7ec6a resourceVersion: "32117" uid: 22de5254-940b-4793-aca9-8a46d98c11c6 spec: sourcePod: network-check-source-7d88cb55d8-z565h targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-30T17:10:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.054444ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:45:28Z" - latency: 1.166859ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:44:28Z" - latency: 1.16221ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:43:28Z" - latency: 1.332582ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:42:28Z" - latency: 1.195022ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:41:28Z" - latency: 1.0182ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:40:28Z" - latency: 1.050242ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:39:28Z" - latency: 1.343172ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:38:28Z" - latency: 1.095729ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:37:28Z" - latency: 1.29255ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:36:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:03:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-57-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-57.ec2.internal uid: 01d64e65-0ef6-4c9b-b4c6-96d2aab7ec6a resourceVersion: "32116" uid: a8cdfc3e-af7f-46af-a178-3ebbb4418c0f spec: sourcePod: network-check-source-7d88cb55d8-z565h targetEndpoint: aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T17:09:28Z" message: 'load-balancer-api-external: tcp connection to aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.308031ms message: 'load-balancer-api-external: tcp connection to aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:45:28Z" - latency: 10.770521ms message: 'load-balancer-api-external: resolved host name aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:45:28Z" - latency: 6.199584ms message: 'load-balancer-api-external: tcp connection to aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:44:28Z" - latency: 7.499574ms message: 'load-balancer-api-external: resolved host name aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:44:28Z" - latency: 4.862811ms message: 'load-balancer-api-external: tcp connection to aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:43:28Z" - latency: 7.813034ms message: 'load-balancer-api-external: resolved host name aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:43:28Z" - latency: 6.46746ms message: 'load-balancer-api-external: tcp connection to aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:42:28Z" - latency: 7.477187ms message: 'load-balancer-api-external: resolved host name aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:42:28Z" - latency: 4.844703ms message: 'load-balancer-api-external: tcp connection to aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:41:28Z" - latency: 7.420255ms message: 'load-balancer-api-external: resolved host name aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:41:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:03:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-57-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-57.ec2.internal uid: 01d64e65-0ef6-4c9b-b4c6-96d2aab7ec6a resourceVersion: "32118" uid: b5d00e4a-096a-455e-81a7-93e8cb021ab1 spec: sourcePod: network-check-source-7d88cb55d8-z565h targetEndpoint: aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-30T17:09:28Z" message: 'load-balancer-api-internal: tcp connection to aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.273737ms message: 'load-balancer-api-internal: tcp connection to aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:45:28Z" - latency: 10.654588ms message: 'load-balancer-api-internal: resolved host name aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:45:28Z" - latency: 6.239644ms message: 'load-balancer-api-internal: tcp connection to aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:44:28Z" - latency: 7.434669ms message: 'load-balancer-api-internal: resolved host name aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:44:28Z" - latency: 4.73768ms message: 'load-balancer-api-internal: tcp connection to aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:43:28Z" - latency: 7.737987ms message: 'load-balancer-api-internal: resolved host name aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:43:28Z" - latency: 6.497755ms message: 'load-balancer-api-internal: tcp connection to aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:42:28Z" - latency: 7.43431ms message: 'load-balancer-api-internal: resolved host name aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:42:28Z" - latency: 4.866643ms message: 'load-balancer-api-internal: tcp connection to aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:41:28Z" - latency: 7.33109ms message: 'load-balancer-api-internal: resolved host name aa90e70a878514bd9b8e39f3fe7c5b3a-b342f382375a9dcb.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-30T17:41:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:03:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-57-to-network-check-target-ip-10-0-132-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-57.ec2.internal uid: 01d64e65-0ef6-4c9b-b4c6-96d2aab7ec6a resourceVersion: "32115" uid: 1b80c964-ffce-4644-b3a3-cdc3b3c846b5 spec: sourcePod: network-check-source-7d88cb55d8-z565h targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-30T17:10:28Z" message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.45671ms message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:45:28Z" - latency: 2.439707ms message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:44:28Z" - latency: 2.31356ms message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:43:28Z" - latency: 2.419478ms message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:42:28Z" - latency: 2.40807ms message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:41:28Z" - latency: 2.263159ms message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:40:28Z" - latency: 2.420764ms message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:39:28Z" - latency: 2.316152ms message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:38:28Z" - latency: 2.517707ms message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:37:28Z" - latency: 2.420248ms message: 'network-check-target-ip-10-0-132-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:36:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:03:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-57-to-network-check-target-ip-10-0-136-120 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-57.ec2.internal uid: 01d64e65-0ef6-4c9b-b4c6-96d2aab7ec6a resourceVersion: "32114" uid: 91251fb7-1748-46f9-a7e6-c311169ec470 spec: sourcePod: network-check-source-7d88cb55d8-z565h targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-30T17:10:28Z" message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.508915ms message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:45:28Z" - latency: 2.38789ms message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:44:28Z" - latency: 2.487676ms message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:43:28Z" - latency: 2.253972ms message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:42:28Z" - latency: 2.336065ms message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:41:28Z" - latency: 2.599611ms message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:40:28Z" - latency: 2.394481ms message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:39:28Z" - latency: 2.791173ms message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:38:28Z" - latency: 2.745001ms message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:37:28Z" - latency: 2.458041ms message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:36:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:03:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-57-to-network-check-target-ip-10-0-137-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-57.ec2.internal uid: 01d64e65-0ef6-4c9b-b4c6-96d2aab7ec6a resourceVersion: "32112" uid: 357bf482-38d0-4699-9fd2-cd1aaa96fcc5 spec: sourcePod: network-check-source-7d88cb55d8-z565h targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-30T17:10:28Z" message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.09147ms message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:45:28Z" - latency: 1.047037ms message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:44:28Z" - latency: 952.361µs message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:43:28Z" - latency: 1.293457ms message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:42:28Z" - latency: 925.875µs message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:41:28Z" - latency: 1.068855ms message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:40:28Z" - latency: 1.385493ms message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:39:28Z" - latency: 1.130291ms message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:38:28Z" - latency: 946.387µs message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:37:28Z" - latency: 1.094744ms message: 'network-check-target-ip-10-0-137-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:36:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-30T17:03:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-57-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-57.ec2.internal uid: 01d64e65-0ef6-4c9b-b4c6-96d2aab7ec6a resourceVersion: "32113" uid: 61aa4ad4-8ca2-4acc-bf75-94c3f7c5a0fa spec: sourcePod: network-check-source-7d88cb55d8-z565h targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-30T17:09:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 999.868µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:45:28Z" - latency: 2.262485ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T17:45:28Z" - latency: 968.159µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:44:28Z" - latency: 1.761798ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T17:44:28Z" - latency: 1.024261ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:43:28Z" - latency: 1.732602ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T17:43:28Z" - latency: 1.355428ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:42:28Z" - latency: 1.852731ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T17:42:28Z" - latency: 992.085µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-30T17:41:28Z" - latency: 1.74647ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-30T17:41:28Z" kind: List metadata: resourceVersion: ""