apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T17:06:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-185-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-185.ec2.internal uid: c3eecbc1-291b-4a1d-8c83-6032392e322a resourceVersion: "64136" uid: 99cc7310-6cb2-41c8-bb0f-e3fe4d0cfda8 spec: sourcePod: network-check-source-7d88cb55d8-qt284 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T17:13:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 946.141µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:48:17Z" - latency: 933.389µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:47:17Z" - latency: 1.230183ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:46:17Z" - latency: 1.127889ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:45:17Z" - latency: 1.061906ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:44:17Z" - latency: 1.215635ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:43:17Z" - latency: 863.906µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:42:17Z" - latency: 800.913µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:41:17Z" - latency: 1.427563ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:40:17Z" - latency: 946.179µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:39:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T17:06:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-185-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-185.ec2.internal uid: c3eecbc1-291b-4a1d-8c83-6032392e322a resourceVersion: "64137" uid: 73d20c30-9cac-4742-a685-504faa17de01 spec: sourcePod: network-check-source-7d88cb55d8-qt284 targetEndpoint: a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T17:12:17Z" message: 'load-balancer-api-external: tcp connection to a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.667071ms message: 'load-balancer-api-external: tcp connection to a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:48:17Z" - latency: 8.948965ms message: 'load-balancer-api-external: resolved host name a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:48:17Z" - latency: 4.950075ms message: 'load-balancer-api-external: tcp connection to a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:47:17Z" - latency: 8.466317ms message: 'load-balancer-api-external: resolved host name a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:47:17Z" - latency: 4.859676ms message: 'load-balancer-api-external: tcp connection to a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:46:17Z" - latency: 9.075786ms message: 'load-balancer-api-external: resolved host name a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:46:17Z" - latency: 5.598353ms message: 'load-balancer-api-external: tcp connection to a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:45:17Z" - latency: 8.060966ms message: 'load-balancer-api-external: resolved host name a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:45:17Z" - latency: 4.580357ms message: 'load-balancer-api-external: tcp connection to a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:44:17Z" - latency: 7.65456ms message: 'load-balancer-api-external: resolved host name a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:44:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T17:06:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-185-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-185.ec2.internal uid: c3eecbc1-291b-4a1d-8c83-6032392e322a resourceVersion: "64138" uid: 08e4b16a-4efe-462c-9b3a-6b12d15a9bf1 spec: sourcePod: network-check-source-7d88cb55d8-qt284 targetEndpoint: a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T17:12:17Z" message: 'load-balancer-api-internal: tcp connection to a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.291874ms message: 'load-balancer-api-internal: tcp connection to a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:48:17Z" - latency: 9.021378ms message: 'load-balancer-api-internal: resolved host name a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:48:17Z" - latency: 4.923929ms message: 'load-balancer-api-internal: tcp connection to a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:47:17Z" - latency: 8.574662ms message: 'load-balancer-api-internal: resolved host name a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:47:17Z" - latency: 3.914467ms message: 'load-balancer-api-internal: tcp connection to a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:46:17Z" - latency: 9.11243ms message: 'load-balancer-api-internal: resolved host name a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:46:17Z" - latency: 4.771781ms message: 'load-balancer-api-internal: tcp connection to a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:45:17Z" - latency: 8.095172ms message: 'load-balancer-api-internal: resolved host name a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:45:17Z" - latency: 5.241895ms message: 'load-balancer-api-internal: tcp connection to a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:44:17Z" - latency: 7.817494ms message: 'load-balancer-api-internal: resolved host name a707fa914e31c40a1955b9b738c80592-e5ba48f810f7a436.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T17:44:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T17:06:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-185-to-network-check-target-ip-10-0-134-152 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-185.ec2.internal uid: c3eecbc1-291b-4a1d-8c83-6032392e322a resourceVersion: "64134" uid: fac70c1b-18ba-432d-800f-3ebb8a7e8149 spec: sourcePod: network-check-source-7d88cb55d8-qt284 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T17:13:17Z" message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.220388ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:48:17Z" - latency: 2.244225ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:47:17Z" - latency: 2.347647ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:46:17Z" - latency: 2.02098ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:45:17Z" - latency: 2.144437ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:44:17Z" - latency: 2.166554ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:43:17Z" - latency: 2.260771ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:42:17Z" - latency: 2.114797ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:41:17Z" - latency: 2.237478ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:40:17Z" - latency: 1.85222ms message: 'network-check-target-ip-10-0-134-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:39:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T17:06:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-185-to-network-check-target-ip-10-0-137-137 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-185.ec2.internal uid: c3eecbc1-291b-4a1d-8c83-6032392e322a resourceVersion: "64133" uid: d4d7b0ad-626a-459f-ab00-6e29ad569de1 spec: sourcePod: network-check-source-7d88cb55d8-qt284 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T17:13:17Z" message: 'network-check-target-ip-10-0-137-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.98711ms message: 'network-check-target-ip-10-0-137-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:48:17Z" - latency: 1.855963ms message: 'network-check-target-ip-10-0-137-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:47:17Z" - latency: 1.498947ms message: 'network-check-target-ip-10-0-137-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:46:17Z" - latency: 1.964059ms message: 'network-check-target-ip-10-0-137-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:45:17Z" - latency: 1.654773ms message: 'network-check-target-ip-10-0-137-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:44:17Z" - latency: 1.963894ms message: 'network-check-target-ip-10-0-137-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:43:17Z" - latency: 1.919726ms message: 'network-check-target-ip-10-0-137-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:42:17Z" - latency: 1.866928ms message: 'network-check-target-ip-10-0-137-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:41:17Z" - latency: 2.084612ms message: 'network-check-target-ip-10-0-137-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:40:17Z" - latency: 1.77816ms message: 'network-check-target-ip-10-0-137-137: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:39:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T17:06:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-185-to-network-check-target-ip-10-0-138-185 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-185.ec2.internal uid: c3eecbc1-291b-4a1d-8c83-6032392e322a resourceVersion: "64132" uid: 48ab240a-3810-478f-8749-154b8e5af3ef spec: sourcePod: network-check-source-7d88cb55d8-qt284 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T17:13:17Z" message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 959.822µs message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:48:17Z" - latency: 977.682µs message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:47:17Z" - latency: 1.418672ms message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:46:17Z" - latency: 1.36036ms message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:45:17Z" - latency: 988.413µs message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:44:17Z" - latency: 1.328409ms message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:43:17Z" - latency: 956.47µs message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:42:17Z" - latency: 930.393µs message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:41:17Z" - latency: 1.594427ms message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:40:17Z" - latency: 1.240621ms message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:39:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T17:06:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-185-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-185.ec2.internal uid: c3eecbc1-291b-4a1d-8c83-6032392e322a resourceVersion: "64135" uid: b18cc517-843e-4e01-b4d4-42c24e45ad88 spec: sourcePod: network-check-source-7d88cb55d8-qt284 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T17:12:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.136892ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:48:17Z" - latency: 1.837202ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T17:48:17Z" - latency: 769.14µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:47:17Z" - latency: 2.142351ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T17:47:17Z" - latency: 839.503µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:46:17Z" - latency: 2.268447ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T17:46:17Z" - latency: 838.109µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:45:17Z" - latency: 1.691436ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T17:45:17Z" - latency: 772.13µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T17:44:17Z" - latency: 1.841904ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T17:44:17Z" kind: List metadata: resourceVersion: ""