apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T23:17:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-77-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-77.ec2.internal uid: ce3eb0b5-5fec-4d6f-a4c1-9d106a243c19 resourceVersion: "47157" uid: b102e3eb-7537-475c-aea0-f8d35ce49b1d spec: sourcePod: network-check-source-989f8b8dc-bdm5q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T23:25:00Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.18999ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:46:00Z" - latency: 1.274094ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:45:00Z" - latency: 817.006µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:44:00Z" - latency: 887.205µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:43:00Z" - latency: 763.553µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:42:00Z" - latency: 1.070476ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:41:00Z" - latency: 1.253904ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:40:00Z" - latency: 882.262µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:39:00Z" - latency: 965.758µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:38:00Z" - latency: 1.134821ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:37:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T23:17:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-77-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-77.ec2.internal uid: ce3eb0b5-5fec-4d6f-a4c1-9d106a243c19 resourceVersion: "49721" uid: eda8643b-15ef-41ca-92ec-fa4abd4c7c48 spec: sourcePod: network-check-source-989f8b8dc-bdm5q targetEndpoint: a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T23:24:00Z" message: 'load-balancer-api-external: tcp connection to a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.624767ms message: 'load-balancer-api-external: tcp connection to a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:48:00Z" - latency: 8.816189ms message: 'load-balancer-api-external: resolved host name a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:48:00Z" - latency: 3.764795ms message: 'load-balancer-api-external: tcp connection to a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:47:00Z" - latency: 7.20327ms message: 'load-balancer-api-external: resolved host name a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:47:00Z" - latency: 4.126017ms message: 'load-balancer-api-external: tcp connection to a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:46:00Z" - latency: 9.908011ms message: 'load-balancer-api-external: resolved host name a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:46:00Z" - latency: 4.545985ms message: 'load-balancer-api-external: tcp connection to a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:45:00Z" - latency: 8.542224ms message: 'load-balancer-api-external: resolved host name a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:45:00Z" - latency: 4.886641ms message: 'load-balancer-api-external: tcp connection to a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:44:00Z" - latency: 8.173057ms message: 'load-balancer-api-external: resolved host name a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:44:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T23:17:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-77-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-77.ec2.internal uid: ce3eb0b5-5fec-4d6f-a4c1-9d106a243c19 resourceVersion: "49722" uid: 4ccd943b-3849-40d9-8c74-6acdff7a4ddd spec: sourcePod: network-check-source-989f8b8dc-bdm5q targetEndpoint: a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T23:24:00Z" message: 'load-balancer-api-internal: tcp connection to a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.605771ms message: 'load-balancer-api-internal: tcp connection to a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:48:00Z" - latency: 9.246361ms message: 'load-balancer-api-internal: resolved host name a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:48:00Z" - latency: 3.731112ms message: 'load-balancer-api-internal: tcp connection to a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:47:00Z" - latency: 7.137289ms message: 'load-balancer-api-internal: resolved host name a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:47:00Z" - latency: 4.101038ms message: 'load-balancer-api-internal: tcp connection to a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:46:00Z" - latency: 9.932048ms message: 'load-balancer-api-internal: resolved host name a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:46:00Z" - latency: 4.544228ms message: 'load-balancer-api-internal: tcp connection to a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:45:00Z" - latency: 8.440702ms message: 'load-balancer-api-internal: resolved host name a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:45:00Z" - latency: 4.915853ms message: 'load-balancer-api-internal: tcp connection to a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:44:00Z" - latency: 8.100418ms message: 'load-balancer-api-internal: resolved host name a8b148b35ca7348d29d87976e2ade078-62c7c49a00497ff4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T23:44:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T23:17:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-77-to-network-check-target-ip-10-0-134-140 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-77.ec2.internal uid: ce3eb0b5-5fec-4d6f-a4c1-9d106a243c19 resourceVersion: "47155" uid: dd0a2fb3-c1f3-4546-a7cc-ec8b3b612faf spec: sourcePod: network-check-source-989f8b8dc-bdm5q targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T23:25:00Z" message: 'network-check-target-ip-10-0-134-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.187559ms message: 'network-check-target-ip-10-0-134-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:46:00Z" - latency: 2.26938ms message: 'network-check-target-ip-10-0-134-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:45:00Z" - latency: 1.839594ms message: 'network-check-target-ip-10-0-134-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:44:00Z" - latency: 2.19212ms message: 'network-check-target-ip-10-0-134-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:43:00Z" - latency: 2.060518ms message: 'network-check-target-ip-10-0-134-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:42:00Z" - latency: 1.746306ms message: 'network-check-target-ip-10-0-134-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:41:00Z" - latency: 2.243431ms message: 'network-check-target-ip-10-0-134-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:40:00Z" - latency: 1.766577ms message: 'network-check-target-ip-10-0-134-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:39:00Z" - latency: 1.898182ms message: 'network-check-target-ip-10-0-134-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:38:00Z" - latency: 2.368342ms message: 'network-check-target-ip-10-0-134-140: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:37:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T23:17:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-77-to-network-check-target-ip-10-0-137-77 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-77.ec2.internal uid: ce3eb0b5-5fec-4d6f-a4c1-9d106a243c19 resourceVersion: "47154" uid: 71fb4294-a78f-46cb-8af1-5e8115033a70 spec: sourcePod: network-check-source-989f8b8dc-bdm5q targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T23:25:00Z" message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.001881ms message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:46:00Z" - latency: 1.265652ms message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:45:00Z" - latency: 1.348457ms message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:44:00Z" - latency: 1.029188ms message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:43:00Z" - latency: 1.052413ms message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:42:00Z" - latency: 1.17365ms message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:41:00Z" - latency: 897.861µs message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:40:00Z" - latency: 960.404µs message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:39:00Z" - latency: 1.276224ms message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:38:00Z" - latency: 1.512157ms message: 'network-check-target-ip-10-0-137-77: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:37:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T23:17:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-77-to-network-check-target-ip-10-0-143-195 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-77.ec2.internal uid: ce3eb0b5-5fec-4d6f-a4c1-9d106a243c19 resourceVersion: "47156" uid: af25fd75-edbe-4ab3-8a7a-7468fc2ffaf2 spec: sourcePod: network-check-source-989f8b8dc-bdm5q targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T23:25:00Z" message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.760586ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:46:00Z" - latency: 1.993606ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:45:00Z" - latency: 1.879536ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:44:00Z" - latency: 1.973304ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:43:00Z" - latency: 1.883982ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:42:00Z" - latency: 2.037859ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:41:00Z" - latency: 2.115015ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:40:00Z" - latency: 1.949481ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:39:00Z" - latency: 1.729548ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:38:00Z" - latency: 2.012029ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:37:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T23:17:59Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-77-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-77.ec2.internal uid: ce3eb0b5-5fec-4d6f-a4c1-9d106a243c19 resourceVersion: "49720" uid: bb5ee879-7be1-4f41-876f-ea7285360c77 spec: sourcePod: network-check-source-989f8b8dc-bdm5q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T23:24:00Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 942.947µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:48:00Z" - latency: 3.544277ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T23:48:00Z" - latency: 1.005377ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:47:00Z" - latency: 1.850927ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T23:47:00Z" - latency: 876.686µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:46:00Z" - latency: 1.986197ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T23:46:00Z" - latency: 1.067192ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:45:00Z" - latency: 2.000682ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T23:45:00Z" - latency: 876.949µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T23:44:00Z" - latency: 1.633964ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T23:44:00Z" kind: List metadata: resourceVersion: ""