apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T08:51:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-230-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-230.ec2.internal uid: 94d7e689-548c-4444-a268-6e03c3d5e0c2 resourceVersion: "69553" uid: 2cecbbf4-e3b6-42d7-904e-17af4cf51e61 spec: sourcePod: network-check-source-7d88cb55d8-5tlqg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T08:58:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.194876ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:40:24Z" - latency: 954.804µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:39:24Z" - latency: 1.41295ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:38:24Z" - latency: 979.69µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:37:24Z" - latency: 994.827µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:36:24Z" - latency: 1.089236ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:35:24Z" - latency: 1.379268ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:34:24Z" - latency: 999.737µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:33:24Z" - latency: 943.524µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:32:24Z" - latency: 1.766482ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:31:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T08:51:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-230-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-230.ec2.internal uid: 94d7e689-548c-4444-a268-6e03c3d5e0c2 resourceVersion: "68203" uid: e9f2418a-2b0a-46ba-8486-9468e8aba026 spec: sourcePod: network-check-source-7d88cb55d8-5tlqg targetEndpoint: a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T08:57:24Z" message: 'load-balancer-api-external: tcp connection to a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.139424ms message: 'load-balancer-api-external: tcp connection to a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:39:24Z" - latency: 8.740973ms message: 'load-balancer-api-external: resolved host name a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T09:39:24Z" - latency: 5.243947ms message: 'load-balancer-api-external: tcp connection to a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:38:24Z" - latency: 9.30949ms message: 'load-balancer-api-external: resolved host name a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T09:38:24Z" - latency: 3.684632ms message: 'load-balancer-api-external: tcp connection to a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:37:24Z" - latency: 9.788806ms message: 'load-balancer-api-external: resolved host name a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T09:37:24Z" - latency: 4.901802ms message: 'load-balancer-api-external: tcp connection to a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:36:24Z" - latency: 8.617941ms message: 'load-balancer-api-external: resolved host name a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T09:36:24Z" - latency: 4.645093ms message: 'load-balancer-api-external: tcp connection to a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:35:24Z" - latency: 11.981253ms message: 'load-balancer-api-external: resolved host name a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T09:35:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T08:51:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-230-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-230.ec2.internal uid: 94d7e689-548c-4444-a268-6e03c3d5e0c2 resourceVersion: "68202" uid: 4576ba68-2904-4981-9b59-c2b3fe3b3b40 spec: sourcePod: network-check-source-7d88cb55d8-5tlqg targetEndpoint: a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T08:57:24Z" message: 'load-balancer-api-internal: tcp connection to a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.276748ms message: 'load-balancer-api-internal: tcp connection to a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:39:24Z" - latency: 8.775412ms message: 'load-balancer-api-internal: resolved host name a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T09:39:24Z" - latency: 5.219338ms message: 'load-balancer-api-internal: tcp connection to a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:38:24Z" - latency: 9.446911ms message: 'load-balancer-api-internal: resolved host name a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T09:38:24Z" - latency: 3.688303ms message: 'load-balancer-api-internal: tcp connection to a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:37:24Z" - latency: 9.823762ms message: 'load-balancer-api-internal: resolved host name a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T09:37:24Z" - latency: 4.868441ms message: 'load-balancer-api-internal: tcp connection to a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:36:24Z" - latency: 8.696427ms message: 'load-balancer-api-internal: resolved host name a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T09:36:24Z" - latency: 4.627457ms message: 'load-balancer-api-internal: tcp connection to a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:35:24Z" - latency: 12.014362ms message: 'load-balancer-api-internal: resolved host name a7dfe86e5560c47c48afc61d47eff53d-79bb40d159c06c11.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T09:35:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T08:51:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-230-to-network-check-target-ip-10-0-131-230 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-230.ec2.internal uid: 94d7e689-548c-4444-a268-6e03c3d5e0c2 resourceVersion: "69550" uid: 8bb4966c-4817-446a-9102-b2d620ce8963 spec: sourcePod: network-check-source-7d88cb55d8-5tlqg targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T08:58:24Z" message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.047825ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:40:24Z" - latency: 1.044441ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:39:24Z" - latency: 1.029742ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:38:24Z" - latency: 976.087µs message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:37:24Z" - latency: 1.349017ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:36:24Z" - latency: 995.461µs message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:35:24Z" - latency: 1.11946ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:34:24Z" - latency: 1.019102ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:33:24Z" - latency: 1.559243ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:32:24Z" - latency: 1.796473ms message: 'network-check-target-ip-10-0-131-230: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:31:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T08:51:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-230-to-network-check-target-ip-10-0-133-190 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-230.ec2.internal uid: 94d7e689-548c-4444-a268-6e03c3d5e0c2 resourceVersion: "69551" uid: 93041488-70dc-481c-957c-2887d0100973 spec: sourcePod: network-check-source-7d88cb55d8-5tlqg targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T08:58:24Z" message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.191395ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:40:24Z" - latency: 2.232139ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:39:24Z" - latency: 2.679213ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:38:24Z" - latency: 2.573819ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:37:24Z" - latency: 2.181942ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:36:24Z" - latency: 2.731843ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:35:24Z" - latency: 3.005398ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:34:24Z" - latency: 2.650765ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:33:24Z" - latency: 2.715424ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:32:24Z" - latency: 2.328413ms message: 'network-check-target-ip-10-0-133-190: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:31:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T08:51:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-230-to-network-check-target-ip-10-0-141-66 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-230.ec2.internal uid: 94d7e689-548c-4444-a268-6e03c3d5e0c2 resourceVersion: "69552" uid: f8737693-7ade-449f-8384-32bcebd13502 spec: sourcePod: network-check-source-7d88cb55d8-5tlqg targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-29T08:58:24Z" message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.362104ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:40:24Z" - latency: 2.184471ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:39:24Z" - latency: 2.271129ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:38:24Z" - latency: 2.309391ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:37:24Z" - latency: 2.18796ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:36:24Z" - latency: 2.29421ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:35:24Z" - latency: 2.442827ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:34:24Z" - latency: 2.20545ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:33:24Z" - latency: 2.362163ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:32:24Z" - latency: 2.773837ms message: 'network-check-target-ip-10-0-141-66: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:31:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T08:51:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-230-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-230.ec2.internal uid: 94d7e689-548c-4444-a268-6e03c3d5e0c2 resourceVersion: "68201" uid: 15e023a4-e6b7-4165-a23d-2844d5f36bd1 spec: sourcePod: network-check-source-7d88cb55d8-5tlqg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T08:57:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 980.625µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:39:24Z" - latency: 2.196062ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T09:39:24Z" - latency: 925.271µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:38:24Z" - latency: 1.953661ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T09:38:24Z" - latency: 1.180263ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:37:24Z" - latency: 1.793158ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T09:37:24Z" - latency: 1.233275ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:36:24Z" - latency: 1.610231ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T09:36:24Z" - latency: 1.230044ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T09:35:24Z" - latency: 1.795251ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T09:35:24Z" kind: List metadata: resourceVersion: ""