apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-29-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-29.ec2.internal uid: 537c5146-05bb-4589-bdc0-b196e9790f6e resourceVersion: "46195" uid: a4fa7053-f11f-44b4-87f5-64735fbd1154 spec: sourcePod: network-check-source-8894fc9bd-wpxbk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T18:46:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 807.85µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:03:33Z" - latency: 1.273267ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:02:33Z" - latency: 1.207557ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:01:33Z" - latency: 1.008804ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:00:33Z" - latency: 1.077743ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:59:33Z" - latency: 1.141481ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:58:33Z" - latency: 778.594µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:57:33Z" - latency: 808.207µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:56:33Z" - latency: 871.46µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:55:33Z" - latency: 911.735µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:54:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-29-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-29.ec2.internal uid: 537c5146-05bb-4589-bdc0-b196e9790f6e resourceVersion: "46197" uid: fcd87bd8-a828-4c19-95e3-ccc4dbd729bc spec: sourcePod: network-check-source-8894fc9bd-wpxbk targetEndpoint: aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:45:33Z" message: 'load-balancer-api-external: tcp connection to aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.544893ms message: 'load-balancer-api-external: tcp connection to aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:03:33Z" - latency: 8.057395ms message: 'load-balancer-api-external: resolved host name aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:03:33Z" - latency: 4.063006ms message: 'load-balancer-api-external: tcp connection to aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:02:33Z" - latency: 7.738869ms message: 'load-balancer-api-external: resolved host name aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:02:33Z" - latency: 4.82559ms message: 'load-balancer-api-external: tcp connection to aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:01:33Z" - latency: 8.094913ms message: 'load-balancer-api-external: resolved host name aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:01:33Z" - latency: 5.012466ms message: 'load-balancer-api-external: tcp connection to aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:00:33Z" - latency: 8.440723ms message: 'load-balancer-api-external: resolved host name aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:00:33Z" - latency: 5.555792ms message: 'load-balancer-api-external: tcp connection to aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:59:33Z" - latency: 7.912349ms message: 'load-balancer-api-external: resolved host name aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:59:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-29-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-29.ec2.internal uid: 537c5146-05bb-4589-bdc0-b196e9790f6e resourceVersion: "46196" uid: 44dbfd09-77c3-4f94-b0f4-38f901413024 spec: sourcePod: network-check-source-8894fc9bd-wpxbk targetEndpoint: aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:45:33Z" message: 'load-balancer-api-internal: tcp connection to aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.540425ms message: 'load-balancer-api-internal: tcp connection to aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:03:33Z" - latency: 7.947105ms message: 'load-balancer-api-internal: resolved host name aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:03:33Z" - latency: 4.045597ms message: 'load-balancer-api-internal: tcp connection to aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:02:33Z" - latency: 7.708625ms message: 'load-balancer-api-internal: resolved host name aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:02:33Z" - latency: 4.711192ms message: 'load-balancer-api-internal: tcp connection to aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:01:33Z" - latency: 8.046295ms message: 'load-balancer-api-internal: resolved host name aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:01:33Z" - latency: 5.069598ms message: 'load-balancer-api-internal: tcp connection to aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:00:33Z" - latency: 8.390928ms message: 'load-balancer-api-internal: resolved host name aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T20:00:33Z" - latency: 5.264094ms message: 'load-balancer-api-internal: tcp connection to aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:59:33Z" - latency: 7.876896ms message: 'load-balancer-api-internal: resolved host name aebf26d8ee2954e578ef6bbd7695e2cd-334bbbd7cb1bcca2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:59:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-29-to-network-check-target-ip-10-0-129-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-29.ec2.internal uid: 537c5146-05bb-4589-bdc0-b196e9790f6e resourceVersion: "46193" uid: 07ac140e-521e-464b-bf54-b351ebcfe9b4 spec: sourcePod: network-check-source-8894fc9bd-wpxbk targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:46:33Z" message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.101092ms message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:03:33Z" - latency: 2.563841ms message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:02:33Z" - latency: 1.90225ms message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:01:33Z" - latency: 2.049026ms message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:00:33Z" - latency: 2.392008ms message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:59:33Z" - latency: 2.184486ms message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:58:33Z" - latency: 2.177386ms message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:57:33Z" - latency: 2.294754ms message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:56:33Z" - latency: 2.173233ms message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:55:33Z" - latency: 2.168331ms message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:54:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-29-to-network-check-target-ip-10-0-132-204 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-29.ec2.internal uid: 537c5146-05bb-4589-bdc0-b196e9790f6e resourceVersion: "46192" uid: e0ed74cc-5738-4d57-9b09-5f75440a337c spec: sourcePod: network-check-source-8894fc9bd-wpxbk targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:46:33Z" message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.232929ms message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:03:33Z" - latency: 2.218946ms message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:02:33Z" - latency: 1.993557ms message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:01:33Z" - latency: 1.857679ms message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:00:33Z" - latency: 2.05636ms message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:59:33Z" - latency: 2.078217ms message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:58:33Z" - latency: 1.698208ms message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:57:33Z" - latency: 2.04418ms message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:56:33Z" - latency: 2.000485ms message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:55:33Z" - latency: 1.840079ms message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:54:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-29-to-network-check-target-ip-10-0-133-29 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-29.ec2.internal uid: 537c5146-05bb-4589-bdc0-b196e9790f6e resourceVersion: "46191" uid: c6d58166-cd33-442a-809f-8676640a6908 spec: sourcePod: network-check-source-8894fc9bd-wpxbk targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:46:33Z" message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 928.435µs message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:03:33Z" - latency: 1.486594ms message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:02:33Z" - latency: 786.993µs message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:01:33Z" - latency: 693.211µs message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:00:33Z" - latency: 845.803µs message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:59:33Z" - latency: 957.595µs message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:58:33Z" - latency: 796µs message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:57:33Z" - latency: 761.72µs message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:56:33Z" - latency: 1.228394ms message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:55:33Z" - latency: 853.244µs message: 'network-check-target-ip-10-0-133-29: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:54:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-29-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-29.ec2.internal uid: 537c5146-05bb-4589-bdc0-b196e9790f6e resourceVersion: "46194" uid: 03873798-33a7-4b7c-976d-1e3abb070f33 spec: sourcePod: network-check-source-8894fc9bd-wpxbk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T18:45:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 846.746µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:03:33Z" - latency: 1.64356ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:03:33Z" - latency: 770.707µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:02:33Z" - latency: 1.545701ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:02:33Z" - latency: 838.15µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:01:33Z" - latency: 1.894741ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:01:33Z" - latency: 719.893µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T20:00:33Z" - latency: 1.805398ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T20:00:33Z" - latency: 1.19126ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:59:33Z" - latency: 1.508163ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:59:33Z" kind: List metadata: resourceVersion: ""