apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-31-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-31.ec2.internal uid: cdf9fd85-8449-42f4-bc53-0a974293be0f resourceVersion: "78330" uid: 836a3a0c-c83f-4c2e-9545-70b17f643911 spec: sourcePod: network-check-source-869dcfcdcd-p8b85 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-16T17:46:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 974.847µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:56:32Z" - latency: 955.089µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:55:32Z" - latency: 1.115257ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:54:32Z" - latency: 1.153433ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:53:32Z" - latency: 1.108211ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:52:32Z" - latency: 1.497006ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:51:32Z" - latency: 1.23994ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:50:32Z" - latency: 1.055179ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:49:32Z" - latency: 1.128153ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:48:32Z" - latency: 1.165067ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:47:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-31-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-31.ec2.internal uid: cdf9fd85-8449-42f4-bc53-0a974293be0f resourceVersion: "78996" uid: 7992fedc-9c3d-4e45-9acd-1831f12fefe2 spec: sourcePod: network-check-source-869dcfcdcd-p8b85 targetEndpoint: a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T17:45:32Z" message: 'load-balancer-api-external: tcp connection to a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.418741ms message: 'load-balancer-api-external: tcp connection to a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:57:32Z" - latency: 7.05736ms message: 'load-balancer-api-external: resolved host name a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:57:32Z" - latency: 4.831836ms message: 'load-balancer-api-external: tcp connection to a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:56:32Z" - latency: 7.824718ms message: 'load-balancer-api-external: resolved host name a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:56:32Z" - latency: 4.731207ms message: 'load-balancer-api-external: tcp connection to a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:55:32Z" - latency: 7.288869ms message: 'load-balancer-api-external: resolved host name a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:55:32Z" - latency: 5.072242ms message: 'load-balancer-api-external: tcp connection to a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:54:32Z" - latency: 6.793857ms message: 'load-balancer-api-external: resolved host name a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:54:32Z" - latency: 4.857503ms message: 'load-balancer-api-external: tcp connection to a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:53:32Z" - latency: 6.888463ms message: 'load-balancer-api-external: resolved host name a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:53:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-31-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-31.ec2.internal uid: cdf9fd85-8449-42f4-bc53-0a974293be0f resourceVersion: "78995" uid: cb5eabb4-7f38-4915-8cd3-f07c2e590416 spec: sourcePod: network-check-source-869dcfcdcd-p8b85 targetEndpoint: a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-16T17:45:32Z" message: 'load-balancer-api-internal: tcp connection to a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.432053ms message: 'load-balancer-api-internal: tcp connection to a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:57:32Z" - latency: 7.008654ms message: 'load-balancer-api-internal: resolved host name a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:57:32Z" - latency: 4.839079ms message: 'load-balancer-api-internal: tcp connection to a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:56:32Z" - latency: 7.876803ms message: 'load-balancer-api-internal: resolved host name a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:56:32Z" - latency: 4.403395ms message: 'load-balancer-api-internal: tcp connection to a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:55:32Z" - latency: 7.200782ms message: 'load-balancer-api-internal: resolved host name a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:55:32Z" - latency: 5.063935ms message: 'load-balancer-api-internal: tcp connection to a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:54:32Z" - latency: 6.703168ms message: 'load-balancer-api-internal: resolved host name a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:54:32Z" - latency: 5.062407ms message: 'load-balancer-api-internal: tcp connection to a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:53:32Z" - latency: 6.80891ms message: 'load-balancer-api-internal: resolved host name a59be8ef1618e4ac8b5f728e41b05ca4-17ea8ece44ba2f3a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T18:53:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-31-to-network-check-target-ip-10-0-128-180 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-31.ec2.internal uid: cdf9fd85-8449-42f4-bc53-0a974293be0f resourceVersion: "78328" uid: 0ed011c4-08a9-4f0c-83fb-a64cb5da24f5 spec: sourcePod: network-check-source-869dcfcdcd-p8b85 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:46:32Z" message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.225119ms message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:56:32Z" - latency: 2.223725ms message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:55:32Z" - latency: 2.216191ms message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:54:32Z" - latency: 1.950414ms message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:53:32Z" - latency: 2.030808ms message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:52:32Z" - latency: 2.20091ms message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:51:32Z" - latency: 2.36179ms message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:50:32Z" - latency: 1.818103ms message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:49:32Z" - latency: 2.084863ms message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:48:32Z" - latency: 2.371887ms message: 'network-check-target-ip-10-0-128-180: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:47:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-31-to-network-check-target-ip-10-0-132-31 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-31.ec2.internal uid: cdf9fd85-8449-42f4-bc53-0a974293be0f resourceVersion: "78327" uid: 4a68c578-5d0c-4ec2-b39f-9f6755d004c4 spec: sourcePod: network-check-source-869dcfcdcd-p8b85 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:46:32Z" message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.247464ms message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:56:32Z" - latency: 1.483147ms message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:55:32Z" - latency: 1.178787ms message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:54:32Z" - latency: 1.630172ms message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:53:32Z" - latency: 1.106806ms message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:52:32Z" - latency: 1.203366ms message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:51:32Z" - latency: 993.965µs message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:50:32Z" - latency: 936.685µs message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:49:32Z" - latency: 911.074µs message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:48:32Z" - latency: 1.670839ms message: 'network-check-target-ip-10-0-132-31: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:47:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-31-to-network-check-target-ip-10-0-142-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-31.ec2.internal uid: cdf9fd85-8449-42f4-bc53-0a974293be0f resourceVersion: "78329" uid: ed470d6b-a596-4d22-b39b-531a57616029 spec: sourcePod: network-check-source-869dcfcdcd-p8b85 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-16T17:46:32Z" message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.339274ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:56:32Z" - latency: 2.373578ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:55:32Z" - latency: 2.282407ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:54:32Z" - latency: 2.39262ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:53:32Z" - latency: 2.028478ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:52:32Z" - latency: 2.43053ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:51:32Z" - latency: 2.541811ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:50:32Z" - latency: 2.400872ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:49:32Z" - latency: 1.954874ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:48:32Z" - latency: 2.308085ms message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:47:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-16T17:39:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-31-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-31.ec2.internal uid: cdf9fd85-8449-42f4-bc53-0a974293be0f resourceVersion: "78994" uid: cb6bb0e6-0f2f-4d83-8baf-de6799a100fc spec: sourcePod: network-check-source-869dcfcdcd-p8b85 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-16T17:45:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 899.599µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:57:32Z" - latency: 2.062383ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:57:32Z" - latency: 1.161089ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:56:32Z" - latency: 2.518345ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:56:32Z" - latency: 1.13173ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:55:32Z" - latency: 2.171313ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:55:32Z" - latency: 929.502µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:54:32Z" - latency: 2.021018ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:54:32Z" - latency: 1.029719ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T18:53:32Z" - latency: 1.888244ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T18:53:32Z" kind: List metadata: resourceVersion: ""