apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:04:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-170-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-170.ec2.internal uid: 504c1842-cecf-4f41-8504-7ebf33c321a7 resourceVersion: "68263" uid: 4feba1a4-a454-46ba-9c34-b00f2f7c858c spec: sourcePod: network-check-source-6f8b768455-82xgp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-16T12:11:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.266759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:39:56Z" - latency: 1.333129ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:38:56Z" - latency: 1.10787ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:37:56Z" - latency: 798.161µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:36:56Z" - latency: 1.134112ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:35:56Z" - latency: 1.165108ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:34:56Z" - latency: 1.623212ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:33:56Z" - latency: 1.360623ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:32:56Z" - latency: 1.101208ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:31:56Z" - latency: 926.265µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:30:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:04:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-170-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-170.ec2.internal uid: 504c1842-cecf-4f41-8504-7ebf33c321a7 resourceVersion: "69143" uid: ee5da49c-9488-4641-8b2d-17a7e95e0e8d spec: sourcePod: network-check-source-6f8b768455-82xgp targetEndpoint: a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T12:10:56Z" message: 'load-balancer-api-external: tcp connection to a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.895418ms message: 'load-balancer-api-external: tcp connection to a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:40:56Z" - latency: 8.3975ms message: 'load-balancer-api-external: resolved host name a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:40:56Z" - latency: 5.494969ms message: 'load-balancer-api-external: tcp connection to a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:39:56Z" - latency: 9.079061ms message: 'load-balancer-api-external: resolved host name a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:39:56Z" - latency: 4.554886ms message: 'load-balancer-api-external: tcp connection to a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:38:56Z" - latency: 8.994277ms message: 'load-balancer-api-external: resolved host name a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:38:56Z" - latency: 4.499161ms message: 'load-balancer-api-external: tcp connection to a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:37:56Z" - latency: 7.723277ms message: 'load-balancer-api-external: resolved host name a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:37:56Z" - latency: 4.347654ms message: 'load-balancer-api-external: tcp connection to a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:36:56Z" - latency: 7.952271ms message: 'load-balancer-api-external: resolved host name a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:36:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:04:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-170-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-170.ec2.internal uid: 504c1842-cecf-4f41-8504-7ebf33c321a7 resourceVersion: "69142" uid: 3c91d7f2-494d-42cb-8d3f-d965e2d9c68b spec: sourcePod: network-check-source-6f8b768455-82xgp targetEndpoint: a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T12:10:56Z" message: 'load-balancer-api-internal: tcp connection to a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.23636ms message: 'load-balancer-api-internal: tcp connection to a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:40:56Z" - latency: 8.324725ms message: 'load-balancer-api-internal: resolved host name a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:40:56Z" - latency: 5.463951ms message: 'load-balancer-api-internal: tcp connection to a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:39:56Z" - latency: 9.108483ms message: 'load-balancer-api-internal: resolved host name a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:39:56Z" - latency: 4.676999ms message: 'load-balancer-api-internal: tcp connection to a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:38:56Z" - latency: 8.950289ms message: 'load-balancer-api-internal: resolved host name a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:38:56Z" - latency: 4.379405ms message: 'load-balancer-api-internal: tcp connection to a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:37:56Z" - latency: 7.686909ms message: 'load-balancer-api-internal: resolved host name a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:37:56Z" - latency: 4.333388ms message: 'load-balancer-api-internal: tcp connection to a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:36:56Z" - latency: 7.921852ms message: 'load-balancer-api-internal: resolved host name a21115dc7f5404d49bb66f6fb6e2551b-3f7ff8688757ee5a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:36:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:04:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-170-to-network-check-target-ip-10-0-133-38 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-170.ec2.internal uid: 504c1842-cecf-4f41-8504-7ebf33c321a7 resourceVersion: "68262" uid: 69b6aa7e-bf00-4bac-baf0-cd6c59199785 spec: sourcePod: network-check-source-6f8b768455-82xgp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-16T12:11:56Z" message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.229429ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:39:56Z" - latency: 2.299024ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:38:56Z" - latency: 2.264366ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:37:56Z" - latency: 2.167362ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:36:56Z" - latency: 1.888487ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:35:56Z" - latency: 2.488811ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:34:56Z" - latency: 2.315699ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:33:56Z" - latency: 2.612748ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:32:56Z" - latency: 2.492412ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:31:56Z" - latency: 2.306101ms message: 'network-check-target-ip-10-0-133-38: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:30:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:04:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-170-to-network-check-target-ip-10-0-136-170 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-170.ec2.internal uid: 504c1842-cecf-4f41-8504-7ebf33c321a7 resourceVersion: "68260" uid: 18223945-70a9-42b5-acd4-35659a1a47ff spec: sourcePod: network-check-source-6f8b768455-82xgp targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-16T12:11:56Z" message: 'network-check-target-ip-10-0-136-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.026657ms message: 'network-check-target-ip-10-0-136-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:39:56Z" - latency: 856.922µs message: 'network-check-target-ip-10-0-136-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:38:56Z" - latency: 882.311µs message: 'network-check-target-ip-10-0-136-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:37:56Z" - latency: 1.259054ms message: 'network-check-target-ip-10-0-136-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:36:56Z" - latency: 815.31µs message: 'network-check-target-ip-10-0-136-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:35:56Z" - latency: 1.000074ms message: 'network-check-target-ip-10-0-136-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:34:56Z" - latency: 978.237µs message: 'network-check-target-ip-10-0-136-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:33:56Z" - latency: 1.110223ms message: 'network-check-target-ip-10-0-136-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:32:56Z" - latency: 1.557699ms message: 'network-check-target-ip-10-0-136-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:31:56Z" - latency: 1.034989ms message: 'network-check-target-ip-10-0-136-170: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:30:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:04:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-170-to-network-check-target-ip-10-0-137-240 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-170.ec2.internal uid: 504c1842-cecf-4f41-8504-7ebf33c321a7 resourceVersion: "68261" uid: 2a849eb6-1bad-499a-8f19-d17bd62445ea spec: sourcePod: network-check-source-6f8b768455-82xgp targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-16T12:11:56Z" message: 'network-check-target-ip-10-0-137-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.929553ms message: 'network-check-target-ip-10-0-137-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:39:56Z" - latency: 2.473877ms message: 'network-check-target-ip-10-0-137-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:38:56Z" - latency: 1.776ms message: 'network-check-target-ip-10-0-137-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:37:56Z" - latency: 1.588816ms message: 'network-check-target-ip-10-0-137-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:36:56Z" - latency: 1.60645ms message: 'network-check-target-ip-10-0-137-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:35:56Z" - latency: 2.143668ms message: 'network-check-target-ip-10-0-137-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:34:56Z" - latency: 2.248979ms message: 'network-check-target-ip-10-0-137-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:33:56Z" - latency: 2.388033ms message: 'network-check-target-ip-10-0-137-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:32:56Z" - latency: 1.668831ms message: 'network-check-target-ip-10-0-137-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:31:56Z" - latency: 2.111396ms message: 'network-check-target-ip-10-0-137-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:30:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:04:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-170-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-170.ec2.internal uid: 504c1842-cecf-4f41-8504-7ebf33c321a7 resourceVersion: "69141" uid: 47deaed4-a767-4901-9a6e-19f6986e596e spec: sourcePod: network-check-source-6f8b768455-82xgp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-16T12:10:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 886.998µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:40:56Z" - latency: 1.803634ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T12:40:56Z" - latency: 820.237µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:39:56Z" - latency: 1.786437ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T12:39:56Z" - latency: 1.066585ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:38:56Z" - latency: 2.344891ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T12:38:56Z" - latency: 874.751µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:37:56Z" - latency: 1.610144ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T12:37:56Z" - latency: 795.354µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:36:56Z" - latency: 1.781318ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T12:36:56Z" kind: List metadata: resourceVersion: ""