apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T14:55:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-11-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-11.ec2.internal uid: 233708e8-2eb0-46d8-8227-e19c93b3813d resourceVersion: "51347" uid: b166756c-517f-4c74-9388-eeac84f462b5 spec: sourcePod: network-check-source-dbd9cf844-zs7fx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T15:02:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.172158ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:30:55Z" - latency: 806.099µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:29:55Z" - latency: 1.019051ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:28:55Z" - latency: 953.982µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:27:55Z" - latency: 1.412642ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:26:55Z" - latency: 1.047301ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:25:55Z" - latency: 962.122µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:24:55Z" - latency: 1.139706ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:23:55Z" - latency: 1.018124ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:22:55Z" - latency: 1.307683ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:21:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T14:55:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-11-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-11.ec2.internal uid: 233708e8-2eb0-46d8-8227-e19c93b3813d resourceVersion: "45773" uid: 256ae110-0d6a-4742-8e16-0a8a72e52aa3 spec: sourcePod: network-check-source-dbd9cf844-zs7fx targetEndpoint: a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T15:01:55Z" message: 'load-balancer-api-external: tcp connection to a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.763597ms message: 'load-balancer-api-external: tcp connection to a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:25:55Z" - latency: 6.448106ms message: 'load-balancer-api-external: resolved host name a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:25:55Z" - latency: 6.109138ms message: 'load-balancer-api-external: tcp connection to a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:24:55Z" - latency: 7.183622ms message: 'load-balancer-api-external: resolved host name a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:24:55Z" - latency: 4.692086ms message: 'load-balancer-api-external: tcp connection to a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:23:55Z" - latency: 7.32273ms message: 'load-balancer-api-external: resolved host name a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:23:55Z" - latency: 5.520921ms message: 'load-balancer-api-external: tcp connection to a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:22:55Z" - latency: 6.49511ms message: 'load-balancer-api-external: resolved host name a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:22:55Z" - latency: 6.486694ms message: 'load-balancer-api-external: tcp connection to a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:21:55Z" - latency: 6.588312ms message: 'load-balancer-api-external: resolved host name a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:21:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T14:55:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-11-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-11.ec2.internal uid: 233708e8-2eb0-46d8-8227-e19c93b3813d resourceVersion: "45772" uid: fde0ce03-dd29-4c8b-98f3-a12b8d79c946 spec: sourcePod: network-check-source-dbd9cf844-zs7fx targetEndpoint: a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T15:01:55Z" message: 'load-balancer-api-internal: tcp connection to a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.755774ms message: 'load-balancer-api-internal: tcp connection to a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:25:55Z" - latency: 6.549441ms message: 'load-balancer-api-internal: resolved host name a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:25:55Z" - latency: 6.340155ms message: 'load-balancer-api-internal: tcp connection to a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:24:55Z" - latency: 7.241681ms message: 'load-balancer-api-internal: resolved host name a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:24:55Z" - latency: 4.688888ms message: 'load-balancer-api-internal: tcp connection to a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:23:55Z" - latency: 7.420977ms message: 'load-balancer-api-internal: resolved host name a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:23:55Z" - latency: 5.524779ms message: 'load-balancer-api-internal: tcp connection to a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:22:55Z" - latency: 6.547579ms message: 'load-balancer-api-internal: resolved host name a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:22:55Z" - latency: 6.555328ms message: 'load-balancer-api-internal: tcp connection to a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:21:55Z" - latency: 6.671631ms message: 'load-balancer-api-internal: resolved host name a8f7e25009cf749f8a2bc6cbc65c5b26-383370b0c594cca5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T15:21:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T14:55:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-11-to-network-check-target-ip-10-0-135-91 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-11.ec2.internal uid: 233708e8-2eb0-46d8-8227-e19c93b3813d resourceVersion: "51345" uid: e1e4c613-a32f-4e28-ae62-08655e924d7d spec: sourcePod: network-check-source-dbd9cf844-zs7fx targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:02:55Z" message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.369802ms message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:30:55Z" - latency: 1.798022ms message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:29:55Z" - latency: 2.416462ms message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:28:55Z" - latency: 2.458532ms message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:27:55Z" - latency: 2.371039ms message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:26:55Z" - latency: 2.312042ms message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:25:55Z" - latency: 2.079505ms message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:24:55Z" - latency: 2.289507ms message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:23:55Z" - latency: 2.486426ms message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:22:55Z" - latency: 2.187424ms message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:21:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T14:55:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-11-to-network-check-target-ip-10-0-139-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-11.ec2.internal uid: 233708e8-2eb0-46d8-8227-e19c93b3813d resourceVersion: "51343" uid: cdf62984-0fb6-4901-bf2c-161766b0c245 spec: sourcePod: network-check-source-dbd9cf844-zs7fx targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:02:55Z" message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 930.607µs message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:30:55Z" - latency: 955.532µs message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:29:55Z" - latency: 922.681µs message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:28:55Z" - latency: 935.885µs message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:27:55Z" - latency: 1.555018ms message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:26:55Z" - latency: 1.268974ms message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:25:55Z" - latency: 1.317298ms message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:24:55Z" - latency: 1.024131ms message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:23:55Z" - latency: 1.311801ms message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:22:55Z" - latency: 1.376789ms message: 'network-check-target-ip-10-0-139-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:21:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T14:55:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-11-to-network-check-target-ip-10-0-139-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-11.ec2.internal uid: 233708e8-2eb0-46d8-8227-e19c93b3813d resourceVersion: "51344" uid: b245a124-99e4-4a02-b884-f2bef67fc0dc spec: sourcePod: network-check-source-dbd9cf844-zs7fx targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T15:02:55Z" message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.741094ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:30:55Z" - latency: 2.457471ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:29:55Z" - latency: 2.259674ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:28:55Z" - latency: 2.61971ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:27:55Z" - latency: 2.258017ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:26:55Z" - latency: 2.527696ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:25:55Z" - latency: 2.601329ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:24:55Z" - latency: 2.548724ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:23:55Z" - latency: 2.611219ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:22:55Z" - latency: 2.26014ms message: 'network-check-target-ip-10-0-139-244: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:21:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T14:55:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-11-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-11.ec2.internal uid: 233708e8-2eb0-46d8-8227-e19c93b3813d resourceVersion: "45771" uid: bd389878-c91c-4308-89e7-e51736c38b47 spec: sourcePod: network-check-source-dbd9cf844-zs7fx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T15:01:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 856.138µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:25:55Z" - latency: 1.714028ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:25:55Z" - latency: 840.245µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:24:55Z" - latency: 1.643352ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:24:55Z" - latency: 914.605µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:23:55Z" - latency: 1.750843ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:23:55Z" - latency: 837.322µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:22:55Z" - latency: 2.012917ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:22:55Z" - latency: 899.615µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T15:21:55Z" - latency: 1.937841ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T15:21:55Z" kind: List metadata: resourceVersion: ""