apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T14:18:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-175-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-175.ec2.internal uid: 8d5d656e-3fc0-45ce-b5a7-d17ab72c270f resourceVersion: "54687" uid: 020871b7-e299-4a19-90e8-f1c14a1a0035 spec: sourcePod: network-check-source-6f8b768455-m5knk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-11T14:25:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.171647ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:46:25Z" - latency: 900.366µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:45:25Z" - latency: 1.196297ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:44:25Z" - latency: 1.199127ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:43:25Z" - latency: 1.031553ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:42:25Z" - latency: 1.400587ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:41:25Z" - latency: 966.123µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:40:25Z" - latency: 1.098678ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:39:25Z" - latency: 1.014513ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:38:25Z" - latency: 985.846µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:37:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T14:18:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-175-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-175.ec2.internal uid: 8d5d656e-3fc0-45ce-b5a7-d17ab72c270f resourceVersion: "56148" uid: dced9fb5-289f-4fb4-8b7a-ee79d34b45fe spec: sourcePod: network-check-source-6f8b768455-m5knk targetEndpoint: a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T14:24:25Z" message: 'load-balancer-api-external: tcp connection to a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.575289ms message: 'load-balancer-api-external: tcp connection to a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:48:25Z" - latency: 7.010859ms message: 'load-balancer-api-external: resolved host name a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:48:25Z" - latency: 3.629324ms message: 'load-balancer-api-external: tcp connection to a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:47:25Z" - latency: 6.512206ms message: 'load-balancer-api-external: resolved host name a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:47:25Z" - latency: 4.039202ms message: 'load-balancer-api-external: tcp connection to a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:46:25Z" - latency: 8.300334ms message: 'load-balancer-api-external: resolved host name a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:46:25Z" - latency: 5.891671ms message: 'load-balancer-api-external: tcp connection to a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:45:25Z" - latency: 7.20175ms message: 'load-balancer-api-external: resolved host name a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:45:25Z" - latency: 5.956114ms message: 'load-balancer-api-external: tcp connection to a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:44:25Z" - latency: 6.77245ms message: 'load-balancer-api-external: resolved host name a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:44:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T14:18:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-175-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-175.ec2.internal uid: 8d5d656e-3fc0-45ce-b5a7-d17ab72c270f resourceVersion: "56147" uid: a6d6323b-ce53-4216-bd5a-87cb1251ce30 spec: sourcePod: network-check-source-6f8b768455-m5knk targetEndpoint: a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T14:24:25Z" message: 'load-balancer-api-internal: tcp connection to a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.56987ms message: 'load-balancer-api-internal: tcp connection to a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:48:25Z" - latency: 7.091439ms message: 'load-balancer-api-internal: resolved host name a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:48:25Z" - latency: 4.93305ms message: 'load-balancer-api-internal: tcp connection to a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:47:25Z" - latency: 6.534716ms message: 'load-balancer-api-internal: resolved host name a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:47:25Z" - latency: 3.939578ms message: 'load-balancer-api-internal: tcp connection to a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:46:25Z" - latency: 8.206987ms message: 'load-balancer-api-internal: resolved host name a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:46:25Z" - latency: 5.56772ms message: 'load-balancer-api-internal: tcp connection to a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:45:25Z" - latency: 7.233398ms message: 'load-balancer-api-internal: resolved host name a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:45:25Z" - latency: 5.944752ms message: 'load-balancer-api-internal: tcp connection to a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:44:25Z" - latency: 6.695932ms message: 'load-balancer-api-internal: resolved host name a74780d535e704ef492fc89756eb8f8f-3975046ef94aeb73.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T14:44:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T14:18:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-175-to-network-check-target-ip-10-0-131-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-175.ec2.internal uid: 8d5d656e-3fc0-45ce-b5a7-d17ab72c270f resourceVersion: "54685" uid: 4325da04-6567-4fff-b523-3d54a0cba701 spec: sourcePod: network-check-source-6f8b768455-m5knk targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-11T14:25:25Z" message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.852312ms message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:46:25Z" - latency: 2.328708ms message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:45:25Z" - latency: 2.341572ms message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:44:25Z" - latency: 2.488268ms message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:43:25Z" - latency: 2.157013ms message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:42:25Z" - latency: 2.535798ms message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:41:25Z" - latency: 2.64768ms message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:40:25Z" - latency: 2.491927ms message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:39:25Z" - latency: 2.112552ms message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:38:25Z" - latency: 2.096594ms message: 'network-check-target-ip-10-0-131-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:37:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T14:18:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-175-to-network-check-target-ip-10-0-133-175 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-175.ec2.internal uid: 8d5d656e-3fc0-45ce-b5a7-d17ab72c270f resourceVersion: "54684" uid: ba0f48ed-2db0-4b79-8b77-d67398112bf0 spec: sourcePod: network-check-source-6f8b768455-m5knk targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-11T14:25:25Z" message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.390808ms message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:46:25Z" - latency: 916.891µs message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:45:25Z" - latency: 1.210022ms message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:44:25Z" - latency: 1.194903ms message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:43:25Z" - latency: 1.02092ms message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:42:25Z" - latency: 1.265703ms message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:41:25Z" - latency: 1.045689ms message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:40:25Z" - latency: 1.09187ms message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:39:25Z" - latency: 1.066461ms message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:38:25Z" - latency: 1.638006ms message: 'network-check-target-ip-10-0-133-175: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:37:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T14:18:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-175-to-network-check-target-ip-10-0-134-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-175.ec2.internal uid: 8d5d656e-3fc0-45ce-b5a7-d17ab72c270f resourceVersion: "54686" uid: 723aaeb2-acb0-4445-b3fa-93307b9f8a70 spec: sourcePod: network-check-source-6f8b768455-m5knk targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-11T14:25:25Z" message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.34003ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:46:25Z" - latency: 2.399421ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:45:25Z" - latency: 2.201496ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:44:25Z" - latency: 2.365243ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:43:25Z" - latency: 1.948576ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:42:25Z" - latency: 2.206745ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:41:25Z" - latency: 2.016324ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:40:25Z" - latency: 2.401501ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:39:25Z" - latency: 2.086558ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:38:25Z" - latency: 2.512185ms message: 'network-check-target-ip-10-0-134-221: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:37:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T14:18:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-175-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-175.ec2.internal uid: 8d5d656e-3fc0-45ce-b5a7-d17ab72c270f resourceVersion: "56146" uid: ef96972e-b16e-48ae-b987-6ed9574f6d29 spec: sourcePod: network-check-source-6f8b768455-m5knk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-11T14:24:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.09149ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:48:25Z" - latency: 2.07615ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T14:48:25Z" - latency: 1.195271ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:47:25Z" - latency: 2.026679ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T14:47:25Z" - latency: 1.540485ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:46:25Z" - latency: 2.430274ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T14:46:25Z" - latency: 1.37934ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:45:25Z" - latency: 1.878753ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T14:45:25Z" - latency: 1.213952ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T14:44:25Z" - latency: 1.77606ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T14:44:25Z" kind: List metadata: resourceVersion: ""