apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-180-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-180.ec2.internal uid: cd05bedf-1a57-4155-9c6c-0b2fda7a3b4d resourceVersion: "54406" uid: a9f4d49a-27fd-415e-93ed-1a2cf619244c spec: sourcePod: network-check-source-989f8b8dc-d7xvk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T11:26:20Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.543894ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:54:20Z" - latency: 766.706µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:53:20Z" - latency: 1.086468ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:52:20Z" - latency: 982.753µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:51:20Z" - latency: 1.179043ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:50:20Z" - latency: 1.115047ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:49:20Z" - latency: 1.002227ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:48:20Z" - latency: 1.127469ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:47:20Z" - latency: 1.003649ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:46:20Z" - latency: 1.070035ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:45:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-180-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-180.ec2.internal uid: cd05bedf-1a57-4155-9c6c-0b2fda7a3b4d resourceVersion: "55387" uid: 962fc2d1-d127-4634-bf53-7d572780bf13 spec: sourcePod: network-check-source-989f8b8dc-d7xvk targetEndpoint: ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T11:25:20Z" message: 'load-balancer-api-external: tcp connection to ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.531245ms message: 'load-balancer-api-external: tcp connection to ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:55:20Z" - latency: 7.901052ms message: 'load-balancer-api-external: resolved host name ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:55:20Z" - latency: 5.027859ms message: 'load-balancer-api-external: tcp connection to ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:54:20Z" - latency: 9.875132ms message: 'load-balancer-api-external: resolved host name ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:54:20Z" - latency: 3.533358ms message: 'load-balancer-api-external: tcp connection to ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:53:20Z" - latency: 8.018748ms message: 'load-balancer-api-external: resolved host name ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:53:20Z" - latency: 3.561721ms message: 'load-balancer-api-external: tcp connection to ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:52:20Z" - latency: 8.740381ms message: 'load-balancer-api-external: resolved host name ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:52:20Z" - latency: 6.063846ms message: 'load-balancer-api-external: tcp connection to ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:51:20Z" - latency: 7.017306ms message: 'load-balancer-api-external: resolved host name ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:51:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-180-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-180.ec2.internal uid: cd05bedf-1a57-4155-9c6c-0b2fda7a3b4d resourceVersion: "55386" uid: 337e403c-a40e-4059-b263-9bbc88182997 spec: sourcePod: network-check-source-989f8b8dc-d7xvk targetEndpoint: ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T11:25:20Z" message: 'load-balancer-api-internal: tcp connection to ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.516595ms message: 'load-balancer-api-internal: tcp connection to ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:55:20Z" - latency: 7.863335ms message: 'load-balancer-api-internal: resolved host name ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:55:20Z" - latency: 4.331887ms message: 'load-balancer-api-internal: tcp connection to ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:54:20Z" - latency: 9.816198ms message: 'load-balancer-api-internal: resolved host name ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:54:20Z" - latency: 3.391969ms message: 'load-balancer-api-internal: tcp connection to ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:53:20Z" - latency: 7.922794ms message: 'load-balancer-api-internal: resolved host name ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:53:20Z" - latency: 4.168439ms message: 'load-balancer-api-internal: tcp connection to ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:52:20Z" - latency: 8.700178ms message: 'load-balancer-api-internal: resolved host name ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:52:20Z" - latency: 6.307049ms message: 'load-balancer-api-internal: tcp connection to ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:51:20Z" - latency: 6.964376ms message: 'load-balancer-api-internal: resolved host name ac28f6f1ed79b4b1195ef25eccf0b180-159fa045d8e2ea88.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T11:51:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-180-to-network-check-target-ip-10-0-133-180 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-180.ec2.internal uid: cd05bedf-1a57-4155-9c6c-0b2fda7a3b4d resourceVersion: "54403" uid: ced0f45b-3c79-47a3-ba37-f63bb72c0ee3 spec: sourcePod: network-check-source-989f8b8dc-d7xvk targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-07T11:26:20Z" message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.198974ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:54:20Z" - latency: 1.057528ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:53:20Z" - latency: 895.679µs message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:52:20Z" - latency: 895.986µs message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:51:20Z" - latency: 1.682469ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:50:20Z" - latency: 868.149µs message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:49:20Z" - latency: 1.246997ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:48:20Z" - latency: 790.037µs message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:47:20Z" - latency: 1.301522ms message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:46:20Z" - latency: 764.49µs message: 'network-check-target-ip-10-0-133-180: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:45:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-180-to-network-check-target-ip-10-0-135-166 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-180.ec2.internal uid: cd05bedf-1a57-4155-9c6c-0b2fda7a3b4d resourceVersion: "54405" uid: 8bc83b2e-d685-4ced-8c52-6bb71ec2e65c spec: sourcePod: network-check-source-989f8b8dc-d7xvk targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T11:26:20Z" message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.918142ms message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:54:20Z" - latency: 2.240851ms message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:53:20Z" - latency: 2.238644ms message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:52:20Z" - latency: 2.292025ms message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:51:20Z" - latency: 2.466017ms message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:50:20Z" - latency: 2.358967ms message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:49:20Z" - latency: 2.506767ms message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:48:20Z" - latency: 2.300902ms message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:47:20Z" - latency: 2.229526ms message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:46:20Z" - latency: 2.518377ms message: 'network-check-target-ip-10-0-135-166: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:45:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-180-to-network-check-target-ip-10-0-142-112 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-180.ec2.internal uid: cd05bedf-1a57-4155-9c6c-0b2fda7a3b4d resourceVersion: "54404" uid: 3c33948c-6dc0-4745-a159-3b60be40ae24 spec: sourcePod: network-check-source-989f8b8dc-d7xvk targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T11:26:20Z" message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.393231ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:54:20Z" - latency: 1.764889ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:53:20Z" - latency: 1.876577ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:52:20Z" - latency: 1.938929ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:51:20Z" - latency: 2.014698ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:50:20Z" - latency: 1.877992ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:49:20Z" - latency: 1.919158ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:48:20Z" - latency: 1.880252ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:47:20Z" - latency: 1.88758ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:46:20Z" - latency: 1.888851ms message: 'network-check-target-ip-10-0-142-112: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:45:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T11:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-180-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-180.ec2.internal uid: cd05bedf-1a57-4155-9c6c-0b2fda7a3b4d resourceVersion: "55384" uid: e34f7945-3a46-4b5b-930a-2b0f8ea801b8 spec: sourcePod: network-check-source-989f8b8dc-d7xvk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T11:25:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 812.921µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:55:20Z" - latency: 1.758055ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T11:55:20Z" - latency: 1.290581ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:54:20Z" - latency: 1.996042ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T11:54:20Z" - latency: 899.721µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:53:20Z" - latency: 1.66975ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T11:53:20Z" - latency: 1.27345ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:52:20Z" - latency: 1.70238ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T11:52:20Z" - latency: 949.523µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T11:51:20Z" - latency: 1.841391ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T11:51:20Z" kind: List metadata: resourceVersion: ""