apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:19:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-131-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-131.ec2.internal uid: ac9d9e07-fe5f-4706-baf9-c5a821095bea resourceVersion: "53619" uid: fa803e2c-d651-4a6a-8aee-462909813eee spec: sourcePod: network-check-source-7d88cb55d8-6dvs6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T21:26:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 791.446µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:43:36Z" - latency: 732.422µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:42:36Z" - latency: 781.212µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:41:36Z" - latency: 1.221332ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:40:36Z" - latency: 809.164µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:39:36Z" - latency: 1.38971ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:38:36Z" - latency: 867.11µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:37:36Z" - latency: 1.099953ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:36:36Z" - latency: 824.647µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:35:36Z" - latency: 1.306837ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:34:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:19:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-131-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-131.ec2.internal uid: ac9d9e07-fe5f-4706-baf9-c5a821095bea resourceVersion: "53621" uid: 283c7daf-4c8e-4c78-957e-a4b62cfb65e5 spec: sourcePod: network-check-source-7d88cb55d8-6dvs6 targetEndpoint: aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T21:25:36Z" message: 'load-balancer-api-external: tcp connection to aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.161539ms message: 'load-balancer-api-external: tcp connection to aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:43:36Z" - latency: 7.98834ms message: 'load-balancer-api-external: resolved host name aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T22:43:36Z" - latency: 4.775324ms message: 'load-balancer-api-external: tcp connection to aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:42:36Z" - latency: 8.657917ms message: 'load-balancer-api-external: resolved host name aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T22:42:36Z" - latency: 5.69816ms message: 'load-balancer-api-external: tcp connection to aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:41:36Z" - latency: 7.93004ms message: 'load-balancer-api-external: resolved host name aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T22:41:36Z" - latency: 5.287301ms message: 'load-balancer-api-external: tcp connection to aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:40:36Z" - latency: 7.746509ms message: 'load-balancer-api-external: resolved host name aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T22:40:36Z" - latency: 5.22974ms message: 'load-balancer-api-external: tcp connection to aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:39:36Z" - latency: 8.046433ms message: 'load-balancer-api-external: resolved host name aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T22:39:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:19:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-131-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-131.ec2.internal uid: ac9d9e07-fe5f-4706-baf9-c5a821095bea resourceVersion: "53620" uid: 6641823f-e12b-470a-95d0-826bdd46cf18 spec: sourcePod: network-check-source-7d88cb55d8-6dvs6 targetEndpoint: aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T21:25:36Z" message: 'load-balancer-api-internal: tcp connection to aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.148742ms message: 'load-balancer-api-internal: tcp connection to aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:43:36Z" - latency: 8.056785ms message: 'load-balancer-api-internal: resolved host name aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T22:43:36Z" - latency: 4.812704ms message: 'load-balancer-api-internal: tcp connection to aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:42:36Z" - latency: 8.563356ms message: 'load-balancer-api-internal: resolved host name aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T22:42:36Z" - latency: 5.717514ms message: 'load-balancer-api-internal: tcp connection to aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:41:36Z" - latency: 8.027261ms message: 'load-balancer-api-internal: resolved host name aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T22:41:36Z" - latency: 5.317767ms message: 'load-balancer-api-internal: tcp connection to aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:40:36Z" - latency: 7.716909ms message: 'load-balancer-api-internal: resolved host name aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T22:40:36Z" - latency: 5.195077ms message: 'load-balancer-api-internal: tcp connection to aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:39:36Z" - latency: 8.088323ms message: 'load-balancer-api-internal: resolved host name aa43fa264bbdd4554abcfcd60162c2cd-92df92f9035edb6a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T22:39:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:19:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-131-to-network-check-target-ip-10-0-129-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-131.ec2.internal uid: ac9d9e07-fe5f-4706-baf9-c5a821095bea resourceVersion: "53617" uid: de7227a0-c372-49a0-8c7f-f87bb1345872 spec: sourcePod: network-check-source-7d88cb55d8-6dvs6 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-24T21:26:36Z" message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.857486ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:43:36Z" - latency: 1.574182ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:42:36Z" - latency: 2.094938ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:41:36Z" - latency: 1.817095ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:40:36Z" - latency: 1.916102ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:39:36Z" - latency: 1.975535ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:38:36Z" - latency: 1.75759ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:37:36Z" - latency: 2.248829ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:36:36Z" - latency: 2.024096ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:35:36Z" - latency: 1.797342ms message: 'network-check-target-ip-10-0-129-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:34:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:19:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-131-to-network-check-target-ip-10-0-138-131 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-131.ec2.internal uid: ac9d9e07-fe5f-4706-baf9-c5a821095bea resourceVersion: "53615" uid: cb6d6034-c887-4fa8-846d-55edf3ac0f13 spec: sourcePod: network-check-source-7d88cb55d8-6dvs6 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T21:26:36Z" message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 711.262µs message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:43:36Z" - latency: 753.074µs message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:42:36Z" - latency: 668.576µs message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:41:36Z" - latency: 658.206µs message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:40:36Z" - latency: 705.541µs message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:39:36Z" - latency: 757.261µs message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:38:36Z" - latency: 638.404µs message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:37:36Z" - latency: 924.042µs message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:36:36Z" - latency: 901.761µs message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:35:36Z" - latency: 755.863µs message: 'network-check-target-ip-10-0-138-131: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:34:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:19:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-131-to-network-check-target-ip-10-0-143-243 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-131.ec2.internal uid: ac9d9e07-fe5f-4706-baf9-c5a821095bea resourceVersion: "53616" uid: c0ea880a-d71e-48d6-8f8c-67f7d1a487e6 spec: sourcePod: network-check-source-7d88cb55d8-6dvs6 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T21:26:36Z" message: 'network-check-target-ip-10-0-143-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.848388ms message: 'network-check-target-ip-10-0-143-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:43:36Z" - latency: 1.865328ms message: 'network-check-target-ip-10-0-143-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:42:36Z" - latency: 2.100113ms message: 'network-check-target-ip-10-0-143-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:41:36Z" - latency: 2.026026ms message: 'network-check-target-ip-10-0-143-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:40:36Z" - latency: 2.090502ms message: 'network-check-target-ip-10-0-143-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:39:36Z" - latency: 2.123908ms message: 'network-check-target-ip-10-0-143-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:38:36Z" - latency: 2.358256ms message: 'network-check-target-ip-10-0-143-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:37:36Z" - latency: 2.166537ms message: 'network-check-target-ip-10-0-143-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:36:36Z" - latency: 1.982212ms message: 'network-check-target-ip-10-0-143-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:35:36Z" - latency: 2.01034ms message: 'network-check-target-ip-10-0-143-243: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:34:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T21:19:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-131-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-131.ec2.internal uid: ac9d9e07-fe5f-4706-baf9-c5a821095bea resourceVersion: "53618" uid: 7521b8f3-3044-4082-8a72-7125232d47e9 spec: sourcePod: network-check-source-7d88cb55d8-6dvs6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T21:25:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 870.133µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:43:36Z" - latency: 1.69844ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T22:43:36Z" - latency: 873.73µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:42:36Z" - latency: 1.692967ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T22:42:36Z" - latency: 1.053865ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:41:36Z" - latency: 1.674561ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T22:41:36Z" - latency: 827.232µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:40:36Z" - latency: 1.375596ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T22:40:36Z" - latency: 774.641µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T22:39:36Z" - latency: 1.857367ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T22:39:36Z" kind: List metadata: resourceVersion: ""