apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:37:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-205-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-205.ec2.internal uid: c2988e3f-ff8d-484f-bfca-f6c1d1322415 resourceVersion: "70609" uid: 9e89c049-310f-4638-8d56-ed6f7cbb7ebc spec: sourcePod: network-check-source-7d88cb55d8-hspwk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T20:44:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.273821ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:26:37Z" - latency: 1.419711ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:25:37Z" - latency: 1.715037ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:24:37Z" - latency: 1.271799ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:23:37Z" - latency: 851.311µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:22:37Z" - latency: 925.983µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:21:37Z" - latency: 1.084506ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:20:37Z" - latency: 965.178µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:19:37Z" - latency: 1.679004ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:18:37Z" - latency: 1.163216ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:17:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:37:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-205-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-205.ec2.internal uid: c2988e3f-ff8d-484f-bfca-f6c1d1322415 resourceVersion: "69783" uid: cc746c09-4d15-40f3-a488-820cf296c782 spec: sourcePod: network-check-source-7d88cb55d8-hspwk targetEndpoint: abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T20:43:37Z" message: 'load-balancer-api-external: tcp connection to abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.788672ms message: 'load-balancer-api-external: tcp connection to abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:25:37Z" - latency: 7.684676ms message: 'load-balancer-api-external: resolved host name abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:25:37Z" - latency: 4.95339ms message: 'load-balancer-api-external: tcp connection to abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:24:37Z" - latency: 7.794255ms message: 'load-balancer-api-external: resolved host name abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:24:37Z" - latency: 4.460782ms message: 'load-balancer-api-external: tcp connection to abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:23:37Z" - latency: 7.372897ms message: 'load-balancer-api-external: resolved host name abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:23:37Z" - latency: 4.029957ms message: 'load-balancer-api-external: tcp connection to abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:22:37Z" - latency: 9.565541ms message: 'load-balancer-api-external: resolved host name abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:22:37Z" - latency: 4.465362ms message: 'load-balancer-api-external: tcp connection to abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:21:37Z" - latency: 10.082452ms message: 'load-balancer-api-external: resolved host name abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:21:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:37:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-205-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-205.ec2.internal uid: c2988e3f-ff8d-484f-bfca-f6c1d1322415 resourceVersion: "69784" uid: 66854c44-9b48-40d0-8652-0448c7a1f977 spec: sourcePod: network-check-source-7d88cb55d8-hspwk targetEndpoint: abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T20:43:37Z" message: 'load-balancer-api-internal: tcp connection to abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.807377ms message: 'load-balancer-api-internal: tcp connection to abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:25:37Z" - latency: 7.617492ms message: 'load-balancer-api-internal: resolved host name abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:25:37Z" - latency: 5.003447ms message: 'load-balancer-api-internal: tcp connection to abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:24:37Z" - latency: 7.680545ms message: 'load-balancer-api-internal: resolved host name abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:24:37Z" - latency: 4.508904ms message: 'load-balancer-api-internal: tcp connection to abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:23:37Z" - latency: 7.398222ms message: 'load-balancer-api-internal: resolved host name abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:23:37Z" - latency: 4.020671ms message: 'load-balancer-api-internal: tcp connection to abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:22:37Z" - latency: 9.49013ms message: 'load-balancer-api-internal: resolved host name abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:22:37Z" - latency: 4.933024ms message: 'load-balancer-api-internal: tcp connection to abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:21:37Z" - latency: 10.065171ms message: 'load-balancer-api-internal: resolved host name abfd37b6fbc2d4e8091c7e25058b939b-649bf434765c6a16.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T21:21:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:37:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-205-to-network-check-target-ip-10-0-140-195 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-205.ec2.internal uid: c2988e3f-ff8d-484f-bfca-f6c1d1322415 resourceVersion: "70607" uid: fb4db623-4344-488e-a155-31c14809a874 spec: sourcePod: network-check-source-7d88cb55d8-hspwk targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T20:44:37Z" message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.922013ms message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:26:37Z" - latency: 1.905805ms message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:25:37Z" - latency: 2.071709ms message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:24:37Z" - latency: 1.968898ms message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:23:37Z" - latency: 2.26015ms message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:22:37Z" - latency: 2.255632ms message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:21:37Z" - latency: 2.410892ms message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:20:37Z" - latency: 2.293026ms message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:19:37Z" - latency: 2.543688ms message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:18:37Z" - latency: 2.353846ms message: 'network-check-target-ip-10-0-140-195: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:17:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:37:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-205-to-network-check-target-ip-10-0-142-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-205.ec2.internal uid: c2988e3f-ff8d-484f-bfca-f6c1d1322415 resourceVersion: "70608" uid: 0abbd762-a338-48fc-a6e7-aebdc8cfba00 spec: sourcePod: network-check-source-7d88cb55d8-hspwk targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T20:44:37Z" message: 'network-check-target-ip-10-0-142-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.458855ms message: 'network-check-target-ip-10-0-142-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:26:37Z" - latency: 2.393538ms message: 'network-check-target-ip-10-0-142-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:25:37Z" - latency: 2.638647ms message: 'network-check-target-ip-10-0-142-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:24:37Z" - latency: 2.524001ms message: 'network-check-target-ip-10-0-142-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:23:37Z" - latency: 2.294571ms message: 'network-check-target-ip-10-0-142-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:22:37Z" - latency: 2.29876ms message: 'network-check-target-ip-10-0-142-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:21:37Z" - latency: 2.355883ms message: 'network-check-target-ip-10-0-142-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:20:37Z" - latency: 2.343772ms message: 'network-check-target-ip-10-0-142-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:19:37Z" - latency: 2.347931ms message: 'network-check-target-ip-10-0-142-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:18:37Z" - latency: 2.159438ms message: 'network-check-target-ip-10-0-142-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:17:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:37:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-205-to-network-check-target-ip-10-0-143-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-205.ec2.internal uid: c2988e3f-ff8d-484f-bfca-f6c1d1322415 resourceVersion: "70606" uid: 98018258-f9df-4942-b1bb-cf6b36dd198b spec: sourcePod: network-check-source-7d88cb55d8-hspwk targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T20:44:37Z" message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 888.482µs message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:26:37Z" - latency: 1.045586ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:25:37Z" - latency: 1.526584ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:24:37Z" - latency: 1.592319ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:23:37Z" - latency: 1.587245ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:22:37Z" - latency: 1.129573ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:21:37Z" - latency: 1.694131ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:20:37Z" - latency: 1.459497ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:19:37Z" - latency: 1.755249ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:18:37Z" - latency: 1.094606ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:17:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T20:37:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-205-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-205.ec2.internal uid: c2988e3f-ff8d-484f-bfca-f6c1d1322415 resourceVersion: "69782" uid: ffe1e975-4f77-4037-a29c-078d10aa483c spec: sourcePod: network-check-source-7d88cb55d8-hspwk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T20:43:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 974.897µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:25:37Z" - latency: 1.764018ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:25:37Z" - latency: 985.657µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:24:37Z" - latency: 2.669198ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:24:37Z" - latency: 1.16468ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:23:37Z" - latency: 1.956512ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:23:37Z" - latency: 900.67µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:22:37Z" - latency: 2.274244ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:22:37Z" - latency: 830.056µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T21:21:37Z" - latency: 2.550113ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T21:21:37Z" kind: List metadata: resourceVersion: ""