apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:23:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-242-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-242.ec2.internal uid: 87d6454a-fa2c-40fc-a8e7-0b0f6d36eaec resourceVersion: "48973" uid: 369159f2-a1af-48e9-8806-435e8787838e spec: sourcePod: network-check-source-989f8b8dc-l78ml targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T19:30:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.008231ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:58:59Z" - latency: 1.147244ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:57:59Z" - latency: 817.197µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:56:59Z" - latency: 1.372195ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:55:59Z" - latency: 965.289µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:54:59Z" - latency: 1.006634ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:53:59Z" - latency: 1.217056ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:52:59Z" - latency: 1.09343ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:51:59Z" - latency: 1.061406ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:50:59Z" - latency: 1.041456ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:49:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:23:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-242-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-242.ec2.internal uid: 87d6454a-fa2c-40fc-a8e7-0b0f6d36eaec resourceVersion: "45853" uid: 1ecf143d-ce6b-48ec-8505-e42bedd30385 spec: sourcePod: network-check-source-989f8b8dc-l78ml targetEndpoint: aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T19:29:59Z" message: 'load-balancer-api-external: tcp connection to aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.959268ms message: 'load-balancer-api-external: tcp connection to aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:53:59Z" - latency: 8.412029ms message: 'load-balancer-api-external: resolved host name aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:53:59Z" - latency: 4.66945ms message: 'load-balancer-api-external: tcp connection to aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:52:59Z" - latency: 7.051575ms message: 'load-balancer-api-external: resolved host name aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:52:59Z" - latency: 6.542734ms message: 'load-balancer-api-external: tcp connection to aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:51:59Z" - latency: 7.335068ms message: 'load-balancer-api-external: resolved host name aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:51:59Z" - latency: 4.461352ms message: 'load-balancer-api-external: tcp connection to aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:50:59Z" - latency: 7.32716ms message: 'load-balancer-api-external: resolved host name aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:50:59Z" - latency: 4.531991ms message: 'load-balancer-api-external: tcp connection to aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:49:59Z" - latency: 7.255062ms message: 'load-balancer-api-external: resolved host name aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:49:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:23:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-242-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-242.ec2.internal uid: 87d6454a-fa2c-40fc-a8e7-0b0f6d36eaec resourceVersion: "45852" uid: 25e66514-4bb7-4799-979f-8ec31e902836 spec: sourcePod: network-check-source-989f8b8dc-l78ml targetEndpoint: aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T19:29:59Z" message: 'load-balancer-api-internal: tcp connection to aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.628504ms message: 'load-balancer-api-internal: tcp connection to aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:53:59Z" - latency: 8.364559ms message: 'load-balancer-api-internal: resolved host name aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:53:59Z" - latency: 4.527669ms message: 'load-balancer-api-internal: tcp connection to aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:52:59Z" - latency: 7.11008ms message: 'load-balancer-api-internal: resolved host name aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:52:59Z" - latency: 5.969864ms message: 'load-balancer-api-internal: tcp connection to aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:51:59Z" - latency: 7.368949ms message: 'load-balancer-api-internal: resolved host name aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:51:59Z" - latency: 4.422178ms message: 'load-balancer-api-internal: tcp connection to aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:50:59Z" - latency: 7.290574ms message: 'load-balancer-api-internal: resolved host name aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:50:59Z" - latency: 5.851751ms message: 'load-balancer-api-internal: tcp connection to aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:49:59Z" - latency: 7.219273ms message: 'load-balancer-api-internal: resolved host name aa3fb6cc0e53b47a39f4ebe88e1dddaa-81b6ebb866844294.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:49:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:23:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-242-to-network-check-target-ip-10-0-130-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-242.ec2.internal uid: 87d6454a-fa2c-40fc-a8e7-0b0f6d36eaec resourceVersion: "48969" uid: 1088c817-e7e1-45c1-ba66-6c27967c0b15 spec: sourcePod: network-check-source-989f8b8dc-l78ml targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T19:30:59Z" message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 868.917µs message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:58:59Z" - latency: 1.24776ms message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:57:59Z" - latency: 1.349662ms message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:56:59Z" - latency: 1.11841ms message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:55:59Z" - latency: 837.292µs message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:54:59Z" - latency: 840.697µs message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:53:59Z" - latency: 994.92µs message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:52:59Z" - latency: 897.85µs message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:51:59Z" - latency: 896.983µs message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:50:59Z" - latency: 849.335µs message: 'network-check-target-ip-10-0-130-242: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:49:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:23:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-242-to-network-check-target-ip-10-0-135-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-242.ec2.internal uid: 87d6454a-fa2c-40fc-a8e7-0b0f6d36eaec resourceVersion: "48971" uid: 454c7cd8-53f3-4b71-b40f-a0a9cd28e027 spec: sourcePod: network-check-source-989f8b8dc-l78ml targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T19:30:59Z" message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.178424ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:58:59Z" - latency: 2.283485ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:57:59Z" - latency: 2.102117ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:56:59Z" - latency: 2.354097ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:55:59Z" - latency: 2.164177ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:54:59Z" - latency: 2.223936ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:53:59Z" - latency: 2.201567ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:52:59Z" - latency: 2.063619ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:51:59Z" - latency: 2.187594ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:50:59Z" - latency: 2.332752ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:49:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:23:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-242-to-network-check-target-ip-10-0-137-135 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-242.ec2.internal uid: 87d6454a-fa2c-40fc-a8e7-0b0f6d36eaec resourceVersion: "48970" uid: 5d6aa105-a62b-487f-8431-931f48a6c34c spec: sourcePod: network-check-source-989f8b8dc-l78ml targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T19:30:59Z" message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.927761ms message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:58:59Z" - latency: 1.891812ms message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:57:59Z" - latency: 1.807155ms message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:56:59Z" - latency: 1.844886ms message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:55:59Z" - latency: 1.654805ms message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:54:59Z" - latency: 1.987466ms message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:53:59Z" - latency: 1.811194ms message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:52:59Z" - latency: 1.779976ms message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:51:59Z" - latency: 1.972341ms message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:50:59Z" - latency: 1.510091ms message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:49:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T19:23:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-242-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-242.ec2.internal uid: 87d6454a-fa2c-40fc-a8e7-0b0f6d36eaec resourceVersion: "45851" uid: 601e236c-0a76-46a2-af90-2d7af7db3f63 spec: sourcePod: network-check-source-989f8b8dc-l78ml targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T19:29:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 777.523µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:53:59Z" - latency: 2.313842ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:53:59Z" - latency: 859.529µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:52:59Z" - latency: 1.849658ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:52:59Z" - latency: 895.215µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:51:59Z" - latency: 2.32976ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:51:59Z" - latency: 815.001µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:50:59Z" - latency: 1.99207ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:50:59Z" - latency: 957.978µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:49:59Z" - latency: 2.02505ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:49:59Z" kind: List metadata: resourceVersion: ""