apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:33:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-73-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-73.ec2.internal uid: 2e9ef42c-6c7b-4eb3-b554-ce31280e3b20 resourceVersion: "18340" uid: a202cdf6-77b3-47cd-81e9-1aa994996214 spec: sourcePod: network-check-source-8894fc9bd-nncrg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T22:40:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 928.505µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:47:15Z" - latency: 1.016528ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:46:15Z" - latency: 946.855µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:45:15Z" - latency: 1.025464ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:44:15Z" - latency: 941.851µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:43:15Z" - latency: 898.288µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:42:15Z" - latency: 685.641µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:41:15Z" - latency: 722.723µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:40:15Z" - latency: 960.004µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:39:15Z" - latency: 1.014945ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:38:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:33:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-73-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-73.ec2.internal uid: 2e9ef42c-6c7b-4eb3-b554-ce31280e3b20 resourceVersion: "17351" uid: d17b7b72-360c-44e3-ab58-6b77017c16a1 spec: sourcePod: network-check-source-8894fc9bd-nncrg targetEndpoint: a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T22:39:15Z" message: 'load-balancer-api-external: tcp connection to a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.875698ms message: 'load-balancer-api-external: tcp connection to a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:45:15Z" - latency: 8.062657ms message: 'load-balancer-api-external: resolved host name a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:45:15Z" - latency: 5.031241ms message: 'load-balancer-api-external: tcp connection to a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:44:15Z" - latency: 8.100874ms message: 'load-balancer-api-external: resolved host name a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:44:15Z" - latency: 3.687416ms message: 'load-balancer-api-external: tcp connection to a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:43:15Z" - latency: 7.562021ms message: 'load-balancer-api-external: resolved host name a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:43:15Z" - latency: 9.724219ms message: 'load-balancer-api-external: tcp connection to a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:42:15Z" - latency: 8.542818ms message: 'load-balancer-api-external: resolved host name a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:42:15Z" - latency: 4.632776ms message: 'load-balancer-api-external: tcp connection to a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:41:15Z" - latency: 7.795292ms message: 'load-balancer-api-external: resolved host name a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:41:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:33:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-73-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-73.ec2.internal uid: 2e9ef42c-6c7b-4eb3-b554-ce31280e3b20 resourceVersion: "17352" uid: 8a07083f-5cbb-4f5a-979e-f6f4dfca6502 spec: sourcePod: network-check-source-8894fc9bd-nncrg targetEndpoint: a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T22:39:15Z" message: 'load-balancer-api-internal: tcp connection to a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.234616ms message: 'load-balancer-api-internal: tcp connection to a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:45:15Z" - latency: 8.009041ms message: 'load-balancer-api-internal: resolved host name a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:45:15Z" - latency: 5.060724ms message: 'load-balancer-api-internal: tcp connection to a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:44:15Z" - latency: 8.037757ms message: 'load-balancer-api-internal: resolved host name a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:44:15Z" - latency: 3.714137ms message: 'load-balancer-api-internal: tcp connection to a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:43:15Z" - latency: 7.515107ms message: 'load-balancer-api-internal: resolved host name a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:43:15Z" - latency: 5.67995ms message: 'load-balancer-api-internal: tcp connection to a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:42:15Z" - latency: 8.565798ms message: 'load-balancer-api-internal: resolved host name a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:42:15Z" - latency: 4.628015ms message: 'load-balancer-api-internal: tcp connection to a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:41:15Z" - latency: 7.827076ms message: 'load-balancer-api-internal: resolved host name a39eb4355074845919ffb95f84f8964c-9f3944925b02658a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T22:41:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:33:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-73-to-network-check-target-ip-10-0-133-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-73.ec2.internal uid: 2e9ef42c-6c7b-4eb3-b554-ce31280e3b20 resourceVersion: "18337" uid: 5ccf3cd5-a20c-4aff-9182-e891916cbf40 spec: sourcePod: network-check-source-8894fc9bd-nncrg targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T22:40:15Z" message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 811.916µs message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:47:15Z" - latency: 958.9µs message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:46:15Z" - latency: 934.498µs message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:45:15Z" - latency: 716.575µs message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:44:15Z" - latency: 715.606µs message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:43:15Z" - latency: 802.49µs message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:42:15Z" - latency: 726.181µs message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:41:15Z" - latency: 1.051466ms message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:40:15Z" - latency: 1.158742ms message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:39:15Z" - latency: 1.543749ms message: 'network-check-target-ip-10-0-133-73: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:38:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:33:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-73-to-network-check-target-ip-10-0-135-222 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-73.ec2.internal uid: 2e9ef42c-6c7b-4eb3-b554-ce31280e3b20 resourceVersion: "18338" uid: 3ee0b366-d535-4e4d-b2e4-b93aad70dd4a spec: sourcePod: network-check-source-8894fc9bd-nncrg targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-24T22:40:15Z" message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.13372ms message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:47:15Z" - latency: 2.588599ms message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:46:15Z" - latency: 2.201829ms message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:45:15Z" - latency: 1.962542ms message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:44:15Z" - latency: 2.10109ms message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:43:15Z" - latency: 2.192762ms message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:42:15Z" - latency: 1.707287ms message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:41:15Z" - latency: 2.127171ms message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:40:15Z" - latency: 2.113793ms message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:39:15Z" - latency: 2.190762ms message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:38:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:33:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-73-to-network-check-target-ip-10-0-137-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-73.ec2.internal uid: 2e9ef42c-6c7b-4eb3-b554-ce31280e3b20 resourceVersion: "18339" uid: 436ad40f-5576-419d-b992-2e939c282b79 spec: sourcePod: network-check-source-8894fc9bd-nncrg targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T22:40:15Z" message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.665889ms message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:47:15Z" - latency: 1.892034ms message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:46:15Z" - latency: 1.590503ms message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:45:15Z" - latency: 1.577718ms message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:44:15Z" - latency: 1.890214ms message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:43:15Z" - latency: 1.700927ms message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:42:15Z" - latency: 1.413133ms message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:41:15Z" - latency: 1.681769ms message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:40:15Z" - latency: 1.761034ms message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:39:15Z" - latency: 1.926442ms message: 'network-check-target-ip-10-0-137-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:38:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:33:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-73-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-73.ec2.internal uid: 2e9ef42c-6c7b-4eb3-b554-ce31280e3b20 resourceVersion: "17350" uid: 1e768924-e8b1-4ad9-9229-64727d591f41 spec: sourcePod: network-check-source-8894fc9bd-nncrg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T22:39:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 897.957µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:45:15Z" - latency: 1.999011ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:45:15Z" - latency: 837.25µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:44:15Z" - latency: 1.662814ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:44:15Z" - latency: 687.116µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:43:15Z" - latency: 1.841926ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:43:15Z" - latency: 874.752µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:42:15Z" - latency: 1.692256ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:42:15Z" - latency: 824.875µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T22:41:15Z" - latency: 1.738094ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T22:41:15Z" kind: List metadata: resourceVersion: ""