apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:08:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-38-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-38.ec2.internal uid: 67d8ae82-34a8-4097-b06f-c52841670718 resourceVersion: "50755" uid: d7bcb199-b639-4da8-9217-6b527046ddd0 spec: sourcePod: network-check-source-dbd9cf844-ss484 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T15:15:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.117965ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:43:35Z" - latency: 928.106µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:42:35Z" - latency: 999.439µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:41:35Z" - latency: 969.722µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:40:35Z" - latency: 913.504µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:39:35Z" - latency: 1.038825ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:38:35Z" - latency: 1.051674ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:37:35Z" - latency: 1.007327ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:36:35Z" - latency: 1.125567ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:35:35Z" - latency: 781.387µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:34:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:08:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-38-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-38.ec2.internal uid: 67d8ae82-34a8-4097-b06f-c52841670718 resourceVersion: "45305" uid: 7b8fcafe-bed8-4753-bf44-8d6d4070ae9d spec: sourcePod: network-check-source-dbd9cf844-ss484 targetEndpoint: a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T15:14:35Z" message: 'load-balancer-api-external: tcp connection to a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.351627ms message: 'load-balancer-api-external: tcp connection to a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:38:35Z" - latency: 7.175809ms message: 'load-balancer-api-external: resolved host name a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:38:35Z" - latency: 4.894861ms message: 'load-balancer-api-external: tcp connection to a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:37:35Z" - latency: 7.608192ms message: 'load-balancer-api-external: resolved host name a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:37:35Z" - latency: 3.736575ms message: 'load-balancer-api-external: tcp connection to a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:36:35Z" - latency: 7.746095ms message: 'load-balancer-api-external: resolved host name a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:36:35Z" - latency: 4.652762ms message: 'load-balancer-api-external: tcp connection to a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:35:35Z" - latency: 11.40479ms message: 'load-balancer-api-external: resolved host name a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:35:35Z" - latency: 6.389176ms message: 'load-balancer-api-external: tcp connection to a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:34:35Z" - latency: 7.435515ms message: 'load-balancer-api-external: resolved host name a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:34:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:08:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-38-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-38.ec2.internal uid: 67d8ae82-34a8-4097-b06f-c52841670718 resourceVersion: "45304" uid: 84f16b18-b674-471c-b8e4-a7570a0fc5bf spec: sourcePod: network-check-source-dbd9cf844-ss484 targetEndpoint: a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T15:14:35Z" message: 'load-balancer-api-internal: tcp connection to a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.728124ms message: 'load-balancer-api-internal: tcp connection to a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:38:35Z" - latency: 7.125013ms message: 'load-balancer-api-internal: resolved host name a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:38:35Z" - latency: 4.544149ms message: 'load-balancer-api-internal: tcp connection to a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:37:35Z" - latency: 7.617431ms message: 'load-balancer-api-internal: resolved host name a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:37:35Z" - latency: 4.407638ms message: 'load-balancer-api-internal: tcp connection to a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:36:35Z" - latency: 7.711606ms message: 'load-balancer-api-internal: resolved host name a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:36:35Z" - latency: 4.027398ms message: 'load-balancer-api-internal: tcp connection to a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:35:35Z" - latency: 11.357124ms message: 'load-balancer-api-internal: resolved host name a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:35:35Z" - latency: 6.384371ms message: 'load-balancer-api-internal: tcp connection to a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:34:35Z" - latency: 7.396103ms message: 'load-balancer-api-internal: resolved host name a6b1b6be824504fb9bb447f83070e3fb-d019dd22fa17d8cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:34:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:08:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-38-to-network-check-target-ip-10-0-136-38 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-38.ec2.internal uid: 67d8ae82-34a8-4097-b06f-c52841670718 resourceVersion: "50752" uid: 9f3eeba1-900f-4fb1-846f-306a77e74897 spec: sourcePod: network-check-source-dbd9cf844-ss484 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:15:35Z" message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 980.72µs message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:43:35Z" - latency: 841.969µs message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:42:35Z" - latency: 960.958µs message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:41:35Z" - latency: 750.78µs message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:40:35Z" - latency: 1.051387ms message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:39:35Z" - latency: 1.353381ms message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:38:35Z" - latency: 822.833µs message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:37:35Z" - latency: 909.698µs message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:36:35Z" - latency: 871.373µs message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:35:35Z" - latency: 1.058302ms message: 'network-check-target-ip-10-0-136-38: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:34:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:08:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-38-to-network-check-target-ip-10-0-138-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-38.ec2.internal uid: 67d8ae82-34a8-4097-b06f-c52841670718 resourceVersion: "50754" uid: 43b44513-fdf3-4283-bbfa-8e6b634e8255 spec: sourcePod: network-check-source-dbd9cf844-ss484 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:15:35Z" message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.427505ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:43:35Z" - latency: 3.092612ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:42:35Z" - latency: 2.085969ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:41:35Z" - latency: 2.347807ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:40:35Z" - latency: 2.306034ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:39:35Z" - latency: 2.326411ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:38:35Z" - latency: 2.245747ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:37:35Z" - latency: 2.325463ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:36:35Z" - latency: 2.54305ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:35:35Z" - latency: 2.230074ms message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:34:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:08:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-38-to-network-check-target-ip-10-0-142-137 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-38.ec2.internal uid: 67d8ae82-34a8-4097-b06f-c52841670718 resourceVersion: "50753" uid: 67711be8-a5cd-4b37-b1cc-2fb6543fe04b spec: sourcePod: network-check-source-dbd9cf844-ss484 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:15:35Z" message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.399465ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:43:35Z" - latency: 2.153191ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:42:35Z" - latency: 2.309806ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:41:35Z" - latency: 2.226541ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:40:35Z" - latency: 2.283462ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:39:35Z" - latency: 2.687957ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:38:35Z" - latency: 2.211796ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:37:35Z" - latency: 2.21478ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:36:35Z" - latency: 2.479341ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:35:35Z" - latency: 2.678859ms message: 'network-check-target-ip-10-0-142-137: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:34:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T15:08:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-38-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-38.ec2.internal uid: 67d8ae82-34a8-4097-b06f-c52841670718 resourceVersion: "45303" uid: b3516cf2-1eb2-4f85-a61c-51ee6a870a75 spec: sourcePod: network-check-source-dbd9cf844-ss484 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T15:14:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 935.873µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:38:35Z" - latency: 1.715008ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:38:35Z" - latency: 839.288µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:37:35Z" - latency: 1.670154ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:37:35Z" - latency: 796.557µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:36:35Z" - latency: 1.921558ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:36:35Z" - latency: 900.428µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:35:35Z" - latency: 1.724033ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:35:35Z" - latency: 1.056776ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:34:35Z" - latency: 1.725042ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:34:35Z" kind: List metadata: resourceVersion: ""