apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T02:49:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-74-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-74.us-west-1.compute.internal uid: 0a339dca-77ab-4397-93e0-ab9c5da64edc resourceVersion: "124627" uid: 415d85ce-c9a3-4cc3-8fda-8d20e694809d spec: sourcePod: network-check-source-6f78d59f99-z89m4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T02:56:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.200107ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:06:15Z" - latency: 998.147µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:05:15Z" - latency: 882.141µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:04:15Z" - latency: 977.234µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:03:15Z" - latency: 924.449µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:02:15Z" - latency: 1.478327ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:01:15Z" - latency: 1.638187ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:00:15Z" - latency: 1.042997ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T03:59:15Z" - latency: 1.035824ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T03:58:15Z" - latency: 1.358311ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T03:57:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T02:49:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-74-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-74.us-west-1.compute.internal uid: 0a339dca-77ab-4397-93e0-ab9c5da64edc resourceVersion: "125838" uid: 39753a2a-c1d0-448d-a305-a43866c7754f spec: sourcePod: network-check-source-6f78d59f99-z89m4 targetEndpoint: af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T02:55:15Z" message: 'load-balancer-api-external: tcp connection to af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.364285ms message: 'load-balancer-api-external: tcp connection to af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:07:15Z" - latency: 6.525662ms message: 'load-balancer-api-external: resolved host name af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T04:07:15Z" - latency: 53.739697ms message: 'load-balancer-api-external: tcp connection to af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:06:15Z" - latency: 6.650759ms message: 'load-balancer-api-external: resolved host name af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T04:06:15Z" - latency: 52.733802ms message: 'load-balancer-api-external: tcp connection to af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:05:15Z" - latency: 6.971695ms message: 'load-balancer-api-external: resolved host name af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T04:05:15Z" - latency: 52.554034ms message: 'load-balancer-api-external: tcp connection to af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:04:15Z" - latency: 10.511604ms message: 'load-balancer-api-external: resolved host name af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T04:04:15Z" - latency: 54.81931ms message: 'load-balancer-api-external: tcp connection to af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:03:15Z" - latency: 6.531856ms message: 'load-balancer-api-external: resolved host name af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T04:03:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T02:49:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-74-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-74.us-west-1.compute.internal uid: 0a339dca-77ab-4397-93e0-ab9c5da64edc resourceVersion: "125837" uid: a7d9b92a-1883-452c-a7e5-cd81b9d3100c spec: sourcePod: network-check-source-6f78d59f99-z89m4 targetEndpoint: af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T02:55:15Z" message: 'load-balancer-api-internal: tcp connection to af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 52.481032ms message: 'load-balancer-api-internal: tcp connection to af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:07:15Z" - latency: 6.502711ms message: 'load-balancer-api-internal: resolved host name af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T04:07:15Z" - latency: 53.78657ms message: 'load-balancer-api-internal: tcp connection to af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:06:15Z" - latency: 6.689366ms message: 'load-balancer-api-internal: resolved host name af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T04:06:15Z" - latency: 52.17265ms message: 'load-balancer-api-internal: tcp connection to af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:05:15Z" - latency: 7.036262ms message: 'load-balancer-api-internal: resolved host name af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T04:05:15Z" - latency: 52.565222ms message: 'load-balancer-api-internal: tcp connection to af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:04:15Z" - latency: 10.491331ms message: 'load-balancer-api-internal: resolved host name af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T04:04:15Z" - latency: 54.790493ms message: 'load-balancer-api-internal: tcp connection to af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:03:15Z" - latency: 6.584248ms message: 'load-balancer-api-internal: resolved host name af3a1c6fd9c4d43e7823e9d8be5f460a-a3480c90fef6e68b.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T04:03:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T02:49:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-74-to-network-check-target-ip-10-0-131-112 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-74.us-west-1.compute.internal uid: 0a339dca-77ab-4397-93e0-ab9c5da64edc resourceVersion: "124625" uid: 3eb132a2-d271-4743-9974-ba5358424e84 spec: sourcePod: network-check-source-6f78d59f99-z89m4 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T02:56:15Z" message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.452455ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:06:15Z" - latency: 2.171425ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:05:15Z" - latency: 1.989083ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:04:15Z" - latency: 2.027169ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:03:15Z" - latency: 2.368703ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:02:15Z" - latency: 2.009933ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:01:15Z" - latency: 3.071058ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:00:15Z" - latency: 1.933411ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T03:59:15Z" - latency: 2.083354ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T03:58:15Z" - latency: 1.971562ms message: 'network-check-target-ip-10-0-131-112: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T03:57:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T02:49:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-74-to-network-check-target-ip-10-0-133-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-74.us-west-1.compute.internal uid: 0a339dca-77ab-4397-93e0-ab9c5da64edc resourceVersion: "124626" uid: a7c9cd5c-9e42-409e-a606-a568e2bb2fc5 spec: sourcePod: network-check-source-6f78d59f99-z89m4 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T02:56:15Z" message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.671323ms message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:06:15Z" - latency: 2.248015ms message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:05:15Z" - latency: 2.804583ms message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:04:15Z" - latency: 2.479375ms message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:03:15Z" - latency: 2.423671ms message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:02:15Z" - latency: 2.762335ms message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:01:15Z" - latency: 2.801937ms message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:00:15Z" - latency: 2.562321ms message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T03:59:15Z" - latency: 2.882213ms message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T03:58:15Z" - latency: 3.054666ms message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T03:57:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T02:49:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-74-to-network-check-target-ip-10-0-137-74 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-74.us-west-1.compute.internal uid: 0a339dca-77ab-4397-93e0-ab9c5da64edc resourceVersion: "124624" uid: 73b0facd-6334-4773-858c-1c66bc8e7dc4 spec: sourcePod: network-check-source-6f78d59f99-z89m4 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T02:56:15Z" message: 'network-check-target-ip-10-0-137-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.033023ms message: 'network-check-target-ip-10-0-137-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:06:15Z" - latency: 1.074162ms message: 'network-check-target-ip-10-0-137-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:05:15Z" - latency: 1.083272ms message: 'network-check-target-ip-10-0-137-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:04:15Z" - latency: 1.105972ms message: 'network-check-target-ip-10-0-137-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:03:15Z" - latency: 1.36372ms message: 'network-check-target-ip-10-0-137-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:02:15Z" - latency: 1.22536ms message: 'network-check-target-ip-10-0-137-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:01:15Z" - latency: 1.930347ms message: 'network-check-target-ip-10-0-137-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:00:15Z" - latency: 1.387981ms message: 'network-check-target-ip-10-0-137-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T03:59:15Z" - latency: 1.085886ms message: 'network-check-target-ip-10-0-137-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T03:58:15Z" - latency: 961.864µs message: 'network-check-target-ip-10-0-137-74: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T03:57:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T02:49:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-74-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-74.us-west-1.compute.internal uid: 0a339dca-77ab-4397-93e0-ab9c5da64edc resourceVersion: "125835" uid: af015e5d-a5bf-4748-a93c-c13d7729b38f spec: sourcePod: network-check-source-6f78d59f99-z89m4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T02:55:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.358376ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:07:15Z" - latency: 1.752135ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T04:07:15Z" - latency: 901.749µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:06:15Z" - latency: 1.984992ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T04:06:15Z" - latency: 1.135749ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:05:15Z" - latency: 2.030797ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T04:05:15Z" - latency: 1.028685ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:04:15Z" - latency: 1.741598ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T04:04:15Z" - latency: 1.299272ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T04:03:15Z" - latency: 1.848003ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T04:03:15Z" kind: List metadata: resourceVersion: ""