apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T20:52:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-248-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-248.ec2.internal uid: 4c764bc4-d993-46bc-8482-82b90fda2d63 resourceVersion: "60478" uid: 024aa78a-99e1-4580-ba96-3d5b62483527 spec: sourcePod: network-check-source-869dcfcdcd-qwfct targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T20:59:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.284981ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:34:02Z" - latency: 869.07µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:33:02Z" - latency: 1.05665ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:32:02Z" - latency: 1.167164ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:31:02Z" - latency: 1.297256ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:30:02Z" - latency: 1.152614ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:29:02Z" - latency: 987.048µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:28:02Z" - latency: 1.252087ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:27:02Z" - latency: 945.066µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:26:02Z" - latency: 1.089977ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:25:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T20:52:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-248-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-248.ec2.internal uid: 4c764bc4-d993-46bc-8482-82b90fda2d63 resourceVersion: "60480" uid: af70e70a-83ee-47a3-b99b-a569369d2464 spec: sourcePod: network-check-source-869dcfcdcd-qwfct targetEndpoint: a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T20:58:02Z" message: 'load-balancer-api-external: tcp connection to a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.104053ms message: 'load-balancer-api-external: tcp connection to a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:34:02Z" - latency: 6.67109ms message: 'load-balancer-api-external: resolved host name a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:34:02Z" - latency: 4.75811ms message: 'load-balancer-api-external: tcp connection to a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:33:02Z" - latency: 7.469889ms message: 'load-balancer-api-external: resolved host name a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:33:02Z" - latency: 4.670334ms message: 'load-balancer-api-external: tcp connection to a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:32:02Z" - latency: 7.400641ms message: 'load-balancer-api-external: resolved host name a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:32:02Z" - latency: 5.212069ms message: 'load-balancer-api-external: tcp connection to a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:31:02Z" - latency: 7.614439ms message: 'load-balancer-api-external: resolved host name a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:31:02Z" - latency: 4.318593ms message: 'load-balancer-api-external: tcp connection to a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:30:02Z" - latency: 6.948111ms message: 'load-balancer-api-external: resolved host name a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:30:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T20:52:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-248-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-248.ec2.internal uid: 4c764bc4-d993-46bc-8482-82b90fda2d63 resourceVersion: "60479" uid: 3427d978-c7c9-4694-bf0d-9d3f5a89da34 spec: sourcePod: network-check-source-869dcfcdcd-qwfct targetEndpoint: a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T20:58:02Z" message: 'load-balancer-api-internal: tcp connection to a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.122382ms message: 'load-balancer-api-internal: tcp connection to a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:34:02Z" - latency: 6.723924ms message: 'load-balancer-api-internal: resolved host name a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:34:02Z" - latency: 4.762162ms message: 'load-balancer-api-internal: tcp connection to a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:33:02Z" - latency: 7.536782ms message: 'load-balancer-api-internal: resolved host name a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:33:02Z" - latency: 4.66357ms message: 'load-balancer-api-internal: tcp connection to a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:32:02Z" - latency: 7.484007ms message: 'load-balancer-api-internal: resolved host name a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:32:02Z" - latency: 5.205718ms message: 'load-balancer-api-internal: tcp connection to a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:31:02Z" - latency: 7.680339ms message: 'load-balancer-api-internal: resolved host name a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:31:02Z" - latency: 5.676102ms message: 'load-balancer-api-internal: tcp connection to a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:30:02Z" - latency: 7.004417ms message: 'load-balancer-api-internal: resolved host name a5abea38f92334642b0aaff8b85b41dc-1d928c0d7db5e619.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T21:30:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T20:52:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-248-to-network-check-target-ip-10-0-137-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-248.ec2.internal uid: 4c764bc4-d993-46bc-8482-82b90fda2d63 resourceVersion: "60475" uid: 72ed90be-b786-4bc8-826a-993b1647ca65 spec: sourcePod: network-check-source-869dcfcdcd-qwfct targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-15T20:59:02Z" message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.129313ms message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:34:02Z" - latency: 1.840914ms message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:33:02Z" - latency: 2.196901ms message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:32:02Z" - latency: 2.166169ms message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:31:02Z" - latency: 1.689616ms message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:30:02Z" - latency: 2.177361ms message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:29:02Z" - latency: 1.88916ms message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:28:02Z" - latency: 2.200347ms message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:27:02Z" - latency: 2.040282ms message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:26:02Z" - latency: 2.069511ms message: 'network-check-target-ip-10-0-137-234: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:25:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T20:52:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-248-to-network-check-target-ip-10-0-138-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-248.ec2.internal uid: 4c764bc4-d993-46bc-8482-82b90fda2d63 resourceVersion: "60474" uid: 189b5602-5701-47d0-9986-c641b72ef3a2 spec: sourcePod: network-check-source-869dcfcdcd-qwfct targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T20:59:02Z" message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 966.98µs message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:34:02Z" - latency: 1.001224ms message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:33:02Z" - latency: 1.312135ms message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:32:02Z" - latency: 991.665µs message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:31:02Z" - latency: 1.111426ms message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:30:02Z" - latency: 1.001939ms message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:29:02Z" - latency: 940.811µs message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:28:02Z" - latency: 880.322µs message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:27:02Z" - latency: 1.089443ms message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:26:02Z" - latency: 942.591µs message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:25:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T20:52:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-248-to-network-check-target-ip-10-0-140-96 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-248.ec2.internal uid: 4c764bc4-d993-46bc-8482-82b90fda2d63 resourceVersion: "60476" uid: 76f24b14-77ed-4c61-b970-d16459a94430 spec: sourcePod: network-check-source-869dcfcdcd-qwfct targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T20:59:02Z" message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.267826ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:34:02Z" - latency: 2.187292ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:33:02Z" - latency: 2.193133ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:32:02Z" - latency: 2.107862ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:31:02Z" - latency: 2.102197ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:30:02Z" - latency: 2.138753ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:29:02Z" - latency: 2.015456ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:28:02Z" - latency: 2.210493ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:27:02Z" - latency: 2.146365ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:26:02Z" - latency: 2.266054ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:25:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T20:52:01Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-248-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-248.ec2.internal uid: 4c764bc4-d993-46bc-8482-82b90fda2d63 resourceVersion: "60477" uid: 09f18b94-8f0f-463b-80cd-e980c5d505b3 spec: sourcePod: network-check-source-869dcfcdcd-qwfct targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T20:58:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 852.903µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:34:02Z" - latency: 1.741938ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:34:02Z" - latency: 787.512µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:33:02Z" - latency: 2.209736ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:33:02Z" - latency: 924.859µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:32:02Z" - latency: 1.811834ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:32:02Z" - latency: 1.053748ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:31:02Z" - latency: 1.746582ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:31:02Z" - latency: 1.188034ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T21:30:02Z" - latency: 1.999829ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T21:30:02Z" kind: List metadata: resourceVersion: ""