apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T05:29:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-143-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-143.us-west-2.compute.internal uid: 1f4081a8-a639-419f-b462-125241195703 resourceVersion: "30890" uid: a90532e6-af14-43ad-8cf2-1813930242ca spec: sourcePod: network-check-source-6f78d59f99-xk9lw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-04T05:36:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 834.959µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:43:02Z" - latency: 1.545144ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:42:02Z" - latency: 1.413439ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:41:02Z" - latency: 1.060601ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:40:02Z" - latency: 1.628639ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:39:02Z" - latency: 1.315894ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:38:02Z" - latency: 968.507µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:37:02Z" - latency: 987.294µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:36:02Z" - latency: 1.453428ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:35:02Z" - latency: 1.037716ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:34:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T05:29:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-143-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-143.us-west-2.compute.internal uid: 1f4081a8-a639-419f-b462-125241195703 resourceVersion: "38843" uid: 390bc07b-f8f0-48e0-b993-21219c5af5c0 spec: sourcePod: network-check-source-6f78d59f99-xk9lw targetEndpoint: a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T05:35:02Z" message: 'load-balancer-api-external: tcp connection to a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 60.512524ms message: 'load-balancer-api-external: tcp connection to a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:47:02Z" - latency: 6.550096ms message: 'load-balancer-api-external: resolved host name a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:47:02Z" - latency: 61.369559ms message: 'load-balancer-api-external: tcp connection to a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:46:02Z" - latency: 7.991128ms message: 'load-balancer-api-external: resolved host name a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:46:02Z" - latency: 62.597378ms message: 'load-balancer-api-external: tcp connection to a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:45:02Z" - latency: 13.072229ms message: 'load-balancer-api-external: resolved host name a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:45:02Z" - latency: 59.839711ms message: 'load-balancer-api-external: tcp connection to a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:44:02Z" - latency: 7.425443ms message: 'load-balancer-api-external: resolved host name a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:44:02Z" - latency: 61.387234ms message: 'load-balancer-api-external: tcp connection to a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:43:02Z" - latency: 6.710425ms message: 'load-balancer-api-external: resolved host name a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:43:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T05:29:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-143-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-143.us-west-2.compute.internal uid: 1f4081a8-a639-419f-b462-125241195703 resourceVersion: "38842" uid: f82fb38e-bd74-4332-8f0a-a28bbc9926d7 spec: sourcePod: network-check-source-6f78d59f99-xk9lw targetEndpoint: a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T05:35:02Z" message: 'load-balancer-api-internal: tcp connection to a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 59.425065ms message: 'load-balancer-api-internal: tcp connection to a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:47:02Z" - latency: 6.531471ms message: 'load-balancer-api-internal: resolved host name a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:47:02Z" - latency: 61.347918ms message: 'load-balancer-api-internal: tcp connection to a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:46:02Z" - latency: 8.288024ms message: 'load-balancer-api-internal: resolved host name a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:46:02Z" - latency: 65.930543ms message: 'load-balancer-api-internal: tcp connection to a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:45:02Z" - latency: 12.593722ms message: 'load-balancer-api-internal: resolved host name a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:45:02Z" - latency: 59.844442ms message: 'load-balancer-api-internal: tcp connection to a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:44:02Z" - latency: 7.442001ms message: 'load-balancer-api-internal: resolved host name a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:44:02Z" - latency: 61.392437ms message: 'load-balancer-api-internal: tcp connection to a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:43:02Z" - latency: 6.722247ms message: 'load-balancer-api-internal: resolved host name a6110e2483d664bf1a253f79dfb04657-a868372cdfab352f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T05:43:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T05:29:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-143-to-network-check-target-ip-10-0-130-185 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-143.us-west-2.compute.internal uid: 1f4081a8-a639-419f-b462-125241195703 resourceVersion: "30888" uid: 22c0f583-6177-40c8-914a-78a2c17b33df spec: sourcePod: network-check-source-6f78d59f99-xk9lw targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-04T05:36:02Z" message: 'network-check-target-ip-10-0-130-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.10258ms message: 'network-check-target-ip-10-0-130-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:43:02Z" - latency: 2.262118ms message: 'network-check-target-ip-10-0-130-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:42:02Z" - latency: 2.386885ms message: 'network-check-target-ip-10-0-130-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:41:02Z" - latency: 2.048716ms message: 'network-check-target-ip-10-0-130-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:40:02Z" - latency: 2.875624ms message: 'network-check-target-ip-10-0-130-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:39:02Z" - latency: 1.995477ms message: 'network-check-target-ip-10-0-130-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:38:02Z" - latency: 1.999833ms message: 'network-check-target-ip-10-0-130-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:37:02Z" - latency: 1.906119ms message: 'network-check-target-ip-10-0-130-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:36:02Z" - latency: 1.934191ms message: 'network-check-target-ip-10-0-130-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:35:02Z" - latency: 2.025631ms message: 'network-check-target-ip-10-0-130-185: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:34:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T05:29:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-143-to-network-check-target-ip-10-0-133-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-143.us-west-2.compute.internal uid: 1f4081a8-a639-419f-b462-125241195703 resourceVersion: "30885" uid: 0c55ab3b-f3aa-43e8-a64d-61100d415535 spec: sourcePod: network-check-source-6f78d59f99-xk9lw targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T05:36:02Z" message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 930.543µs message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:43:02Z" - latency: 1.449463ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:42:02Z" - latency: 1.59778ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:41:02Z" - latency: 1.536408ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:40:02Z" - latency: 883.487µs message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:39:02Z" - latency: 1.478676ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:38:02Z" - latency: 1.088943ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:37:02Z" - latency: 949.191µs message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:36:02Z" - latency: 1.075771ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:35:02Z" - latency: 1.019861ms message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:34:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T05:29:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-143-to-network-check-target-ip-10-0-139-34 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-143.us-west-2.compute.internal uid: 1f4081a8-a639-419f-b462-125241195703 resourceVersion: "30886" uid: f6e1204f-ee32-42e6-9918-7af89947eeb8 spec: sourcePod: network-check-source-6f78d59f99-xk9lw targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T05:36:02Z" message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.969815ms message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:43:02Z" - latency: 2.572497ms message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:42:02Z" - latency: 2.245407ms message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:41:02Z" - latency: 2.219718ms message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:40:02Z" - latency: 2.125467ms message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:39:02Z" - latency: 2.158563ms message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:38:02Z" - latency: 2.19813ms message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:37:02Z" - latency: 2.304439ms message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:36:02Z" - latency: 2.116215ms message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:35:02Z" - latency: 2.253291ms message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:34:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T05:29:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-143-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-143.us-west-2.compute.internal uid: 1f4081a8-a639-419f-b462-125241195703 resourceVersion: "38836" uid: 0d03e186-27f5-4f88-a7b9-f4758cc5943d spec: sourcePod: network-check-source-6f78d59f99-xk9lw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-04T05:35:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.004404ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:47:02Z" - latency: 1.94622ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T05:47:02Z" - latency: 1.017ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:46:02Z" - latency: 2.539646ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T05:46:02Z" - latency: 1.661288ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:45:02Z" - latency: 5.922746ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T05:45:02Z" - latency: 980.226µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:44:02Z" - latency: 1.999107ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T05:44:02Z" - latency: 828.577µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T05:43:02Z" - latency: 2.030966ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T05:43:02Z" kind: List metadata: resourceVersion: ""