apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:38:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-70-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-70.ec2.internal uid: 6d6ef44c-6953-4edb-9d80-7dab618c4560 resourceVersion: "24374" uid: 6f1b6114-8e31-4c91-a5d1-e8f002fae14f spec: sourcePod: network-check-source-dbd9cf844-jprlz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-05T15:45:41Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.399903ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:45:41Z" - latency: 1.05752ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:44:41Z" - latency: 967.36µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:43:41Z" - latency: 909.364µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:42:41Z" - latency: 1.234952ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:41:41Z" - latency: 1.126013ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:40:41Z" - latency: 1.343161ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:39:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:38:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-70-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-70.ec2.internal uid: 6d6ef44c-6953-4edb-9d80-7dab618c4560 resourceVersion: "28505" uid: 743c056a-cdf8-4baf-b27a-4ac377162f17 spec: sourcePod: network-check-source-dbd9cf844-jprlz targetEndpoint: aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T15:44:41Z" message: 'load-balancer-api-external: tcp connection to aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.005847ms message: 'load-balancer-api-external: tcp connection to aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:50:41Z" - latency: 6.283184ms message: 'load-balancer-api-external: resolved host name aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:50:41Z" - latency: 4.076312ms message: 'load-balancer-api-external: tcp connection to aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:49:41Z" - latency: 14.645093ms message: 'load-balancer-api-external: resolved host name aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:49:41Z" - latency: 5.322261ms message: 'load-balancer-api-external: tcp connection to aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:48:41Z" - latency: 6.166118ms message: 'load-balancer-api-external: resolved host name aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:48:41Z" - latency: 4.463353ms message: 'load-balancer-api-external: tcp connection to aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:47:41Z" - latency: 10.867399ms message: 'load-balancer-api-external: resolved host name aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:47:41Z" - latency: 5.674775ms message: 'load-balancer-api-external: tcp connection to aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:46:41Z" - latency: 6.892675ms message: 'load-balancer-api-external: resolved host name aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:46:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:38:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-70-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-70.ec2.internal uid: 6d6ef44c-6953-4edb-9d80-7dab618c4560 resourceVersion: "28503" uid: a6086034-3e2b-43fb-a7f3-a34d6c457119 spec: sourcePod: network-check-source-dbd9cf844-jprlz targetEndpoint: aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T15:44:41Z" message: 'load-balancer-api-internal: tcp connection to aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.067367ms message: 'load-balancer-api-internal: tcp connection to aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:50:41Z" - latency: 6.214893ms message: 'load-balancer-api-internal: resolved host name aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:50:41Z" - latency: 3.940562ms message: 'load-balancer-api-internal: tcp connection to aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:49:41Z" - latency: 14.816374ms message: 'load-balancer-api-internal: resolved host name aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:49:41Z" - latency: 4.965143ms message: 'load-balancer-api-internal: tcp connection to aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:48:41Z" - latency: 6.132757ms message: 'load-balancer-api-internal: resolved host name aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:48:41Z" - latency: 4.433531ms message: 'load-balancer-api-internal: tcp connection to aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:47:41Z" - latency: 10.954319ms message: 'load-balancer-api-internal: resolved host name aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:47:41Z" - latency: 4.86904ms message: 'load-balancer-api-internal: tcp connection to aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:46:41Z" - latency: 6.797879ms message: 'load-balancer-api-internal: resolved host name aba553e64fe3c44e381bea7a7ec9e843-a0e77ed4f978e3fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:46:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:38:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-70-to-network-check-target-ip-10-0-136-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-70.ec2.internal uid: 6d6ef44c-6953-4edb-9d80-7dab618c4560 resourceVersion: "24373" uid: c40a4f37-1a07-4bb2-967d-5549373ff89e spec: sourcePod: network-check-source-dbd9cf844-jprlz targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T15:45:41Z" message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.312938ms message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:45:41Z" - latency: 2.223445ms message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:44:41Z" - latency: 2.059826ms message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:43:41Z" - latency: 2.429939ms message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:42:41Z" - latency: 2.418959ms message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:41:41Z" - latency: 2.417635ms message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:40:41Z" - latency: 2.530282ms message: 'network-check-target-ip-10-0-136-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:39:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:38:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-70-to-network-check-target-ip-10-0-140-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-70.ec2.internal uid: 6d6ef44c-6953-4edb-9d80-7dab618c4560 resourceVersion: "24372" uid: a3305b26-6f8f-4d2b-8bc1-936004f46304 spec: sourcePod: network-check-source-dbd9cf844-jprlz targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-05T15:45:41Z" message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.739697ms message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:45:41Z" - latency: 2.412496ms message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:44:41Z" - latency: 2.677399ms message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:43:41Z" - latency: 2.47249ms message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:42:41Z" - latency: 2.405542ms message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:41:41Z" - latency: 2.800789ms message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:40:41Z" - latency: 2.691469ms message: 'network-check-target-ip-10-0-140-178: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:39:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:38:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-70-to-network-check-target-ip-10-0-143-70 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-70.ec2.internal uid: 6d6ef44c-6953-4edb-9d80-7dab618c4560 resourceVersion: "24371" uid: 0239f06f-7081-4759-8e04-9fa4689e92c3 spec: sourcePod: network-check-source-dbd9cf844-jprlz targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T15:45:41Z" message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.446766ms message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:45:41Z" - latency: 1.171316ms message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:44:41Z" - latency: 959.571µs message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:43:41Z" - latency: 854.316µs message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:42:41Z" - latency: 1.112844ms message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:41:41Z" - latency: 1.67757ms message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:40:41Z" - latency: 1.49449ms message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:39:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:38:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-70-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-70.ec2.internal uid: 6d6ef44c-6953-4edb-9d80-7dab618c4560 resourceVersion: "28502" uid: 51e03646-b45c-44ae-bf56-03804f68d316 spec: sourcePod: network-check-source-dbd9cf844-jprlz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-05T15:44:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 880.065µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:50:41Z" - latency: 1.728496ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T15:50:41Z" - latency: 789.832µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:49:41Z" - latency: 1.697071ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T15:49:41Z" - latency: 915.572µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:48:41Z" - latency: 1.740487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T15:48:41Z" - latency: 899.847µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:47:41Z" - latency: 1.801946ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T15:47:41Z" - latency: 1.186135ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:46:41Z" - latency: 1.868052ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T15:46:41Z" kind: List metadata: resourceVersion: ""