apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T21:16:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-149-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-149.ec2.internal uid: 7467041b-6f1c-4f37-808e-7f55e12d00d8 resourceVersion: "44417" uid: b0d6dfe7-803a-4d13-ada5-7cfca2d439fa spec: sourcePod: network-check-source-8894fc9bd-9nwmh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-20T21:23:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.045607ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:44:27Z" - latency: 1.313559ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:43:27Z" - latency: 986.934µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:42:27Z" - latency: 991.803µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:41:27Z" - latency: 1.179188ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:40:27Z" - latency: 1.130436ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:39:27Z" - latency: 943.879µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:38:27Z" - latency: 792.713µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:37:27Z" - latency: 1.273243ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:36:27Z" - latency: 981.35µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:35:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T21:16:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-149-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-149.ec2.internal uid: 7467041b-6f1c-4f37-808e-7f55e12d00d8 resourceVersion: "46829" uid: 44000199-a342-4131-b317-41d0ab1d10fa spec: sourcePod: network-check-source-8894fc9bd-9nwmh targetEndpoint: a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T21:22:27Z" message: 'load-balancer-api-external: tcp connection to a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.156719ms message: 'load-balancer-api-external: tcp connection to a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:46:27Z" - latency: 7.010752ms message: 'load-balancer-api-external: resolved host name a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T21:46:27Z" - latency: 3.193165ms message: 'load-balancer-api-external: tcp connection to a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:45:27Z" - latency: 6.755613ms message: 'load-balancer-api-external: resolved host name a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T21:45:27Z" - latency: 3.829783ms message: 'load-balancer-api-external: tcp connection to a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:44:27Z" - latency: 6.942035ms message: 'load-balancer-api-external: resolved host name a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T21:44:27Z" - latency: 5.315517ms message: 'load-balancer-api-external: tcp connection to a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:43:27Z" - latency: 6.077396ms message: 'load-balancer-api-external: resolved host name a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T21:43:27Z" - latency: 3.816352ms message: 'load-balancer-api-external: tcp connection to a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:42:27Z" - latency: 7.378871ms message: 'load-balancer-api-external: resolved host name a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T21:42:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T21:16:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-149-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-149.ec2.internal uid: 7467041b-6f1c-4f37-808e-7f55e12d00d8 resourceVersion: "46830" uid: 0ab03394-5a80-4f7c-9815-0d7999d95221 spec: sourcePod: network-check-source-8894fc9bd-9nwmh targetEndpoint: a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T21:22:27Z" message: 'load-balancer-api-internal: tcp connection to a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.992761ms message: 'load-balancer-api-internal: tcp connection to a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:46:27Z" - latency: 7.070975ms message: 'load-balancer-api-internal: resolved host name a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T21:46:27Z" - latency: 14.11628ms message: 'load-balancer-api-internal: tcp connection to a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:45:27Z" - latency: 6.65765ms message: 'load-balancer-api-internal: resolved host name a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T21:45:27Z" - latency: 3.919777ms message: 'load-balancer-api-internal: tcp connection to a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:44:27Z" - latency: 6.900529ms message: 'load-balancer-api-internal: resolved host name a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T21:44:27Z" - latency: 5.292187ms message: 'load-balancer-api-internal: tcp connection to a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:43:27Z" - latency: 6.139569ms message: 'load-balancer-api-internal: resolved host name a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T21:43:27Z" - latency: 4.178765ms message: 'load-balancer-api-internal: tcp connection to a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:42:27Z" - latency: 7.346442ms message: 'load-balancer-api-internal: resolved host name a2e284b2ae89c4b8d8f22195b8c11dba-ac556babc39089ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T21:42:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T21:16:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-149-to-network-check-target-ip-10-0-129-149 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-149.ec2.internal uid: 7467041b-6f1c-4f37-808e-7f55e12d00d8 resourceVersion: "44414" uid: 55d722e2-a5b8-477b-b57e-7c75a1a72053 spec: sourcePod: network-check-source-8894fc9bd-9nwmh targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-20T21:23:27Z" message: 'network-check-target-ip-10-0-129-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.029359ms message: 'network-check-target-ip-10-0-129-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:44:27Z" - latency: 1.109024ms message: 'network-check-target-ip-10-0-129-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:43:27Z" - latency: 917.254µs message: 'network-check-target-ip-10-0-129-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:42:27Z" - latency: 829.341µs message: 'network-check-target-ip-10-0-129-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:41:27Z" - latency: 1.208143ms message: 'network-check-target-ip-10-0-129-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:40:27Z" - latency: 818.946µs message: 'network-check-target-ip-10-0-129-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:39:27Z" - latency: 835.31µs message: 'network-check-target-ip-10-0-129-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:38:27Z" - latency: 797.417µs message: 'network-check-target-ip-10-0-129-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:37:27Z" - latency: 1.082327ms message: 'network-check-target-ip-10-0-129-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:36:27Z" - latency: 864.569µs message: 'network-check-target-ip-10-0-129-149: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:35:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T21:16:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-149-to-network-check-target-ip-10-0-129-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-149.ec2.internal uid: 7467041b-6f1c-4f37-808e-7f55e12d00d8 resourceVersion: "44416" uid: dc83b72e-bb5f-4d62-bdfd-d6433b34b8ac spec: sourcePod: network-check-source-8894fc9bd-9nwmh targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-20T21:23:27Z" message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.204204ms message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:44:27Z" - latency: 1.910384ms message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:43:27Z" - latency: 1.777326ms message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:42:27Z" - latency: 1.977332ms message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:41:27Z" - latency: 2.020311ms message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:40:27Z" - latency: 2.10291ms message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:39:27Z" - latency: 1.8964ms message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:38:27Z" - latency: 2.368065ms message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:37:27Z" - latency: 2.284129ms message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:36:27Z" - latency: 2.045836ms message: 'network-check-target-ip-10-0-129-57: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:35:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T21:16:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-149-to-network-check-target-ip-10-0-132-45 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-149.ec2.internal uid: 7467041b-6f1c-4f37-808e-7f55e12d00d8 resourceVersion: "44415" uid: b784e1d4-7383-4b84-b955-dff85bab2b2e spec: sourcePod: network-check-source-8894fc9bd-9nwmh targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-20T21:23:27Z" message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.948761ms message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:44:27Z" - latency: 1.734228ms message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:43:27Z" - latency: 1.773501ms message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:42:27Z" - latency: 1.879703ms message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:41:27Z" - latency: 1.789954ms message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:40:27Z" - latency: 1.716972ms message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:39:27Z" - latency: 1.600466ms message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:38:27Z" - latency: 1.596715ms message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:37:27Z" - latency: 1.832901ms message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:36:27Z" - latency: 1.697845ms message: 'network-check-target-ip-10-0-132-45: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:35:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T21:16:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-149-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-149.ec2.internal uid: 7467041b-6f1c-4f37-808e-7f55e12d00d8 resourceVersion: "46828" uid: 6884eb80-250a-4060-8241-fb13a4b10c55 spec: sourcePod: network-check-source-8894fc9bd-9nwmh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-20T21:22:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 731.65µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:46:27Z" - latency: 1.924304ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T21:46:27Z" - latency: 810.686µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:45:27Z" - latency: 1.749924ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T21:45:27Z" - latency: 792.224µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:44:27Z" - latency: 2.074585ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T21:44:27Z" - latency: 781.885µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:43:27Z" - latency: 1.687939ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T21:43:27Z" - latency: 733.518µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T21:42:27Z" - latency: 1.698414ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T21:42:27Z" kind: List metadata: resourceVersion: ""