apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T02:37:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-136-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-136.ec2.internal uid: 18e50713-e63f-4623-b341-6997e1c6bf0e resourceVersion: "56728" uid: 451aceda-e844-4576-82d9-04825f189454 spec: sourcePod: network-check-source-989f8b8dc-qhcpn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T02:44:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.012792ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:19:28Z" - latency: 1.721146ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:18:28Z" - latency: 1.200957ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:17:28Z" - latency: 1.102483ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:16:28Z" - latency: 873.397µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:15:28Z" - latency: 921.375µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:14:28Z" - latency: 873.724µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:13:28Z" - latency: 1.671858ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:12:28Z" - latency: 1.134498ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:11:28Z" - latency: 951.574µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:10:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T02:37:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-136-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-136.ec2.internal uid: 18e50713-e63f-4623-b341-6997e1c6bf0e resourceVersion: "56729" uid: f20cf8a4-8fc7-43b0-bf52-df618fe8e552 spec: sourcePod: network-check-source-989f8b8dc-qhcpn targetEndpoint: ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T02:43:28Z" message: 'load-balancer-api-external: tcp connection to ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.862991ms message: 'load-balancer-api-external: tcp connection to ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:19:28Z" - latency: 9.385088ms message: 'load-balancer-api-external: resolved host name ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T03:19:28Z" - latency: 5.743663ms message: 'load-balancer-api-external: tcp connection to ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:18:28Z" - latency: 9.487627ms message: 'load-balancer-api-external: resolved host name ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T03:18:28Z" - latency: 4.865143ms message: 'load-balancer-api-external: tcp connection to ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:17:28Z" - latency: 8.621798ms message: 'load-balancer-api-external: resolved host name ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T03:17:28Z" - latency: 4.306358ms message: 'load-balancer-api-external: tcp connection to ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:16:28Z" - latency: 8.919289ms message: 'load-balancer-api-external: resolved host name ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T03:16:28Z" - latency: 4.299851ms message: 'load-balancer-api-external: tcp connection to ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:15:28Z" - latency: 8.210886ms message: 'load-balancer-api-external: resolved host name ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T03:15:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T02:37:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-136-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-136.ec2.internal uid: 18e50713-e63f-4623-b341-6997e1c6bf0e resourceVersion: "56730" uid: 74173a98-18bf-461f-8e4a-da19f75dda36 spec: sourcePod: network-check-source-989f8b8dc-qhcpn targetEndpoint: ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T02:43:28Z" message: 'load-balancer-api-internal: tcp connection to ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.804896ms message: 'load-balancer-api-internal: tcp connection to ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:19:28Z" - latency: 9.590431ms message: 'load-balancer-api-internal: resolved host name ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T03:19:28Z" - latency: 5.75046ms message: 'load-balancer-api-internal: tcp connection to ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:18:28Z" - latency: 9.613122ms message: 'load-balancer-api-internal: resolved host name ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T03:18:28Z" - latency: 4.906773ms message: 'load-balancer-api-internal: tcp connection to ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:17:28Z" - latency: 8.713559ms message: 'load-balancer-api-internal: resolved host name ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T03:17:28Z" - latency: 4.263619ms message: 'load-balancer-api-internal: tcp connection to ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:16:28Z" - latency: 8.986682ms message: 'load-balancer-api-internal: resolved host name ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T03:16:28Z" - latency: 4.284096ms message: 'load-balancer-api-internal: tcp connection to ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:15:28Z" - latency: 8.271475ms message: 'load-balancer-api-internal: resolved host name ad25e5125de4d439d9bdbe7175e9013a-770c13d14a8d1453.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T03:15:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T02:37:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-136-to-network-check-target-ip-10-0-129-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-136.ec2.internal uid: 18e50713-e63f-4623-b341-6997e1c6bf0e resourceVersion: "56725" uid: 092d1d59-9272-4e7d-a0ea-cbe47dbeff67 spec: sourcePod: network-check-source-989f8b8dc-qhcpn targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T02:44:28Z" message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.033922ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:19:28Z" - latency: 1.724575ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:18:28Z" - latency: 1.899559ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:17:28Z" - latency: 1.527209ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:16:28Z" - latency: 2.126395ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:15:28Z" - latency: 2.231415ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:14:28Z" - latency: 1.746665ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:13:28Z" - latency: 1.889569ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:12:28Z" - latency: 1.666515ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:11:28Z" - latency: 1.786705ms message: 'network-check-target-ip-10-0-129-236: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:10:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T02:37:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-136-to-network-check-target-ip-10-0-134-183 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-136.ec2.internal uid: 18e50713-e63f-4623-b341-6997e1c6bf0e resourceVersion: "56726" uid: 4a594ed9-3063-4472-8f26-6c681fd8c4a2 spec: sourcePod: network-check-source-989f8b8dc-qhcpn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T02:44:28Z" message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.559083ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:19:28Z" - latency: 2.442477ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:18:28Z" - latency: 2.370744ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:17:28Z" - latency: 2.206132ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:16:28Z" - latency: 2.471891ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:15:28Z" - latency: 2.611007ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:14:28Z" - latency: 2.251229ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:13:28Z" - latency: 2.263143ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:12:28Z" - latency: 2.332852ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:11:28Z" - latency: 2.291366ms message: 'network-check-target-ip-10-0-134-183: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:10:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T02:37:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-136-to-network-check-target-ip-10-0-138-136 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-136.ec2.internal uid: 18e50713-e63f-4623-b341-6997e1c6bf0e resourceVersion: "56724" uid: 4fc55b57-971e-46fa-bd88-e7b9ea331d2b spec: sourcePod: network-check-source-989f8b8dc-qhcpn targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T02:44:28Z" message: 'network-check-target-ip-10-0-138-136: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 966.572µs message: 'network-check-target-ip-10-0-138-136: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:19:28Z" - latency: 861.624µs message: 'network-check-target-ip-10-0-138-136: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:18:28Z" - latency: 1.545497ms message: 'network-check-target-ip-10-0-138-136: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:17:28Z" - latency: 803.733µs message: 'network-check-target-ip-10-0-138-136: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:16:28Z" - latency: 1.228197ms message: 'network-check-target-ip-10-0-138-136: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:15:28Z" - latency: 1.032149ms message: 'network-check-target-ip-10-0-138-136: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:14:28Z" - latency: 849.631µs message: 'network-check-target-ip-10-0-138-136: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:13:28Z" - latency: 1.44845ms message: 'network-check-target-ip-10-0-138-136: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:12:28Z" - latency: 1.264748ms message: 'network-check-target-ip-10-0-138-136: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:11:28Z" - latency: 987.626µs message: 'network-check-target-ip-10-0-138-136: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:10:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T02:37:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-136-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-136.ec2.internal uid: 18e50713-e63f-4623-b341-6997e1c6bf0e resourceVersion: "56727" uid: b1877ef6-8f5a-4424-a5fa-bb41b1fb07de spec: sourcePod: network-check-source-989f8b8dc-qhcpn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T02:43:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.163281ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:19:28Z" - latency: 2.532941ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T03:19:28Z" - latency: 1.077456ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:18:28Z" - latency: 2.260558ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T03:18:28Z" - latency: 1.273326ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:17:28Z" - latency: 1.866923ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T03:17:28Z" - latency: 884.009µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:16:28Z" - latency: 1.817952ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T03:16:28Z" - latency: 837.343µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T03:15:28Z" - latency: 1.894264ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T03:15:28Z" kind: List metadata: resourceVersion: ""