apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:36:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-209-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-209.us-west-1.compute.internal uid: 51b9baed-a92b-4b6f-9c45-82ee580997e8 resourceVersion: "105556" uid: 68cc9910-fbc3-4816-b59d-ee98e8fbfcfe spec: sourcePod: network-check-source-6f78d59f99-hm2jc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-04T02:43:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.191661ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:39:33Z" - latency: 1.152189ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:38:33Z" - latency: 952.552µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:37:33Z" - latency: 1.655775ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:36:33Z" - latency: 1.333115ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:35:33Z" - latency: 3.836148ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:34:33Z" - latency: 3.539129ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:33:33Z" - latency: 1.948977ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:32:33Z" - latency: 922.176µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:31:33Z" - latency: 1.027875ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:30:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:36:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-209-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-209.us-west-1.compute.internal uid: 51b9baed-a92b-4b6f-9c45-82ee580997e8 resourceVersion: "102445" uid: 8131e2a4-afbb-4ee4-9ca4-825ed430be30 spec: sourcePod: network-check-source-6f78d59f99-hm2jc targetEndpoint: a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T02:42:33Z" message: 'load-balancer-api-external: tcp connection to a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.389725ms message: 'load-balancer-api-external: tcp connection to a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:36:33Z" - latency: 6.98237ms message: 'load-balancer-api-external: resolved host name a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:36:33Z" - latency: 52.397184ms message: 'load-balancer-api-external: tcp connection to a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:35:33Z" - latency: 7.365297ms message: 'load-balancer-api-external: resolved host name a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:35:33Z" - latency: 65.327848ms message: 'load-balancer-api-external: tcp connection to a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:34:33Z" - latency: 46.948729ms message: 'load-balancer-api-external: resolved host name a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:34:33Z" - latency: 54.894257ms message: 'load-balancer-api-external: tcp connection to a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:33:33Z" - latency: 13.013099ms message: 'load-balancer-api-external: resolved host name a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:33:33Z" - latency: 53.789767ms message: 'load-balancer-api-external: tcp connection to a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:32:33Z" - latency: 7.730356ms message: 'load-balancer-api-external: resolved host name a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:32:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:36:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-209-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-209.us-west-1.compute.internal uid: 51b9baed-a92b-4b6f-9c45-82ee580997e8 resourceVersion: "102446" uid: 6494a9f4-963e-431c-9fda-3096229e4a38 spec: sourcePod: network-check-source-6f78d59f99-hm2jc targetEndpoint: a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T02:42:33Z" message: 'load-balancer-api-internal: tcp connection to a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.359451ms message: 'load-balancer-api-internal: tcp connection to a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:36:33Z" - latency: 7.026606ms message: 'load-balancer-api-internal: resolved host name a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:36:33Z" - latency: 52.426151ms message: 'load-balancer-api-internal: tcp connection to a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:35:33Z" - latency: 7.179581ms message: 'load-balancer-api-internal: resolved host name a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:35:33Z" - latency: 65.997688ms message: 'load-balancer-api-internal: tcp connection to a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:34:33Z" - latency: 46.45763ms message: 'load-balancer-api-internal: resolved host name a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:34:33Z" - latency: 55.510682ms message: 'load-balancer-api-internal: tcp connection to a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:33:33Z" - latency: 12.560019ms message: 'load-balancer-api-internal: resolved host name a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:33:33Z" - latency: 53.720461ms message: 'load-balancer-api-internal: tcp connection to a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:32:33Z" - latency: 7.786029ms message: 'load-balancer-api-internal: resolved host name a7878fea1d4a142dfa615cdc355a2760-4128f5fe3c6c09e5.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:32:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:36:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-209-to-network-check-target-ip-10-0-128-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-209.us-west-1.compute.internal uid: 51b9baed-a92b-4b6f-9c45-82ee580997e8 resourceVersion: "105551" uid: 868e2a3e-8cfe-4c52-af83-aa49768ebbb9 spec: sourcePod: network-check-source-6f78d59f99-hm2jc targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-04T02:43:33Z" message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.563668ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:39:33Z" - latency: 2.494383ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:38:33Z" - latency: 2.796298ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:37:33Z" - latency: 2.476168ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:36:33Z" - latency: 2.37181ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:35:33Z" - latency: 19.011122ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:34:33Z" - latency: 5.109082ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:33:33Z" - latency: 2.444415ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:32:33Z" - latency: 2.353655ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:31:33Z" - latency: 2.090182ms message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:30:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:36:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-209-to-network-check-target-ip-10-0-133-209 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-209.us-west-1.compute.internal uid: 51b9baed-a92b-4b6f-9c45-82ee580997e8 resourceVersion: "105550" uid: f06c1d17-8f7b-4529-a5b1-daacc1bccbc5 spec: sourcePod: network-check-source-6f78d59f99-hm2jc targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T02:43:33Z" message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.737521ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:39:33Z" - latency: 1.494613ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:38:33Z" - latency: 855.624µs message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:37:33Z" - latency: 1.201695ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:36:33Z" - latency: 1.071359ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:35:33Z" - latency: 4.094416ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:34:33Z" - latency: 3.292776ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:33:33Z" - latency: 1.055103ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:32:33Z" - latency: 1.282226ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:31:33Z" - latency: 1.179437ms message: 'network-check-target-ip-10-0-133-209: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:30:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:36:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-209-to-network-check-target-ip-10-0-134-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-209.us-west-1.compute.internal uid: 51b9baed-a92b-4b6f-9c45-82ee580997e8 resourceVersion: "105553" uid: 0f8c6e06-0e90-4b76-ba6a-2e8d09b7962d spec: sourcePod: network-check-source-6f78d59f99-hm2jc targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-04T02:43:33Z" message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.704293ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:39:33Z" - latency: 2.600339ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:38:33Z" - latency: 2.459812ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:37:33Z" - latency: 2.533241ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:36:33Z" - latency: 2.2292ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:35:33Z" - latency: 23.672539ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:34:33Z" - latency: 4.298676ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:33:33Z" - latency: 2.722907ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:32:33Z" - latency: 2.936479ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:31:33Z" - latency: 2.39363ms message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:30:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T02:36:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-209-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-209.us-west-1.compute.internal uid: 51b9baed-a92b-4b6f-9c45-82ee580997e8 resourceVersion: "102442" uid: ae2a7cb9-efca-4275-9759-949ed16688f4 spec: sourcePod: network-check-source-6f78d59f99-hm2jc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-04T02:42:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 844.328µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:36:33Z" - latency: 2.007361ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T03:36:33Z" - latency: 1.195733ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:35:33Z" - latency: 2.264808ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T03:35:33Z" - latency: 9.64664ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:34:33Z" - latency: 14.232717ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T03:34:33Z" - latency: 1.09305ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:33:33Z" - latency: 5.978186ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T03:33:33Z" - latency: 1.120679ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:32:33Z" - latency: 2.068585ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T03:32:33Z" kind: List metadata: resourceVersion: ""