apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:23:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-179-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-179.ec2.internal uid: fb15098d-2c14-4341-8226-cf1e258dfa1d resourceVersion: "36552" uid: 11132d24-e89c-4fe2-8090-f266be9ee977 spec: sourcePod: network-check-source-8894fc9bd-6dmj7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T16:30:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.091922ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:44:51Z" - latency: 1.050578ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:43:51Z" - latency: 1.05076ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:42:51Z" - latency: 1.071059ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:41:51Z" - latency: 1.023105ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:40:51Z" - latency: 1.214026ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:39:51Z" - latency: 1.01932ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:38:51Z" - latency: 1.070149ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:37:51Z" - latency: 796.113µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:36:51Z" - latency: 1.026077ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:35:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:23:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-179-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-179.ec2.internal uid: fb15098d-2c14-4341-8226-cf1e258dfa1d resourceVersion: "39794" uid: 219c04a8-9902-43a4-96f6-ac5a6ea58f6f spec: sourcePod: network-check-source-8894fc9bd-6dmj7 targetEndpoint: a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T16:29:51Z" message: 'load-balancer-api-external: tcp connection to a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.963421ms message: 'load-balancer-api-external: tcp connection to a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:47:51Z" - latency: 6.59885ms message: 'load-balancer-api-external: resolved host name a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:47:51Z" - latency: 4.701028ms message: 'load-balancer-api-external: tcp connection to a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:46:51Z" - latency: 9.542294ms message: 'load-balancer-api-external: resolved host name a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:46:51Z" - latency: 3.453577ms message: 'load-balancer-api-external: tcp connection to a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:45:51Z" - latency: 7.638677ms message: 'load-balancer-api-external: resolved host name a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:45:51Z" - latency: 4.217556ms message: 'load-balancer-api-external: tcp connection to a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:44:51Z" - latency: 15.338312ms message: 'load-balancer-api-external: resolved host name a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:44:51Z" - latency: 4.679388ms message: 'load-balancer-api-external: tcp connection to a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:43:51Z" - latency: 9.70385ms message: 'load-balancer-api-external: resolved host name a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:43:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:23:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-179-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-179.ec2.internal uid: fb15098d-2c14-4341-8226-cf1e258dfa1d resourceVersion: "39795" uid: bda71bad-4211-4440-a79a-994ef8f790fa spec: sourcePod: network-check-source-8894fc9bd-6dmj7 targetEndpoint: a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T16:29:51Z" message: 'load-balancer-api-internal: tcp connection to a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.97926ms message: 'load-balancer-api-internal: tcp connection to a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:47:51Z" - latency: 6.557567ms message: 'load-balancer-api-internal: resolved host name a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:47:51Z" - latency: 4.801146ms message: 'load-balancer-api-internal: tcp connection to a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:46:51Z" - latency: 9.502947ms message: 'load-balancer-api-internal: resolved host name a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:46:51Z" - latency: 3.449151ms message: 'load-balancer-api-internal: tcp connection to a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:45:51Z" - latency: 7.556867ms message: 'load-balancer-api-internal: resolved host name a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:45:51Z" - latency: 4.182888ms message: 'load-balancer-api-internal: tcp connection to a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:44:51Z" - latency: 15.408648ms message: 'load-balancer-api-internal: resolved host name a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:44:51Z" - latency: 4.720587ms message: 'load-balancer-api-internal: tcp connection to a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:43:51Z" - latency: 9.649896ms message: 'load-balancer-api-internal: resolved host name a193e3cc5d13f423981993119da8d00b-a9a85d8ed83075d5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T16:43:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:23:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-179-to-network-check-target-ip-10-0-132-179 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-179.ec2.internal uid: fb15098d-2c14-4341-8226-cf1e258dfa1d resourceVersion: "36549" uid: 32e17355-1782-4071-821d-2abfaab8d1f6 spec: sourcePod: network-check-source-8894fc9bd-6dmj7 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T16:30:51Z" message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 779.75µs message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:44:51Z" - latency: 862.644µs message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:43:51Z" - latency: 926.451µs message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:42:51Z" - latency: 1.012364ms message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:41:51Z" - latency: 880.568µs message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:40:51Z" - latency: 951.981µs message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:39:51Z" - latency: 899.427µs message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:38:51Z" - latency: 828.378µs message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:37:51Z" - latency: 948.538µs message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:36:51Z" - latency: 918.518µs message: 'network-check-target-ip-10-0-132-179: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:35:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:23:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-179-to-network-check-target-ip-10-0-134-77 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-179.ec2.internal uid: fb15098d-2c14-4341-8226-cf1e258dfa1d resourceVersion: "36550" uid: 447b55e9-3de8-40ec-89bb-ef168f04be98 spec: sourcePod: network-check-source-8894fc9bd-6dmj7 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-17T16:30:51Z" message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.124949ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:44:51Z" - latency: 2.348045ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:43:51Z" - latency: 2.272709ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:42:51Z" - latency: 2.285245ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:41:51Z" - latency: 2.124279ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:40:51Z" - latency: 2.183933ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:39:51Z" - latency: 2.216959ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:38:51Z" - latency: 2.246609ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:37:51Z" - latency: 2.199832ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:36:51Z" - latency: 2.321858ms message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:35:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:23:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-179-to-network-check-target-ip-10-0-136-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-179.ec2.internal uid: fb15098d-2c14-4341-8226-cf1e258dfa1d resourceVersion: "36551" uid: 9a5dda29-0aa6-410e-a6a4-012b66023791 spec: sourcePod: network-check-source-8894fc9bd-6dmj7 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T16:30:51Z" message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.258934ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:44:51Z" - latency: 2.371971ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:43:51Z" - latency: 2.411614ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:42:51Z" - latency: 2.30621ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:41:51Z" - latency: 2.301051ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:40:51Z" - latency: 2.64683ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:39:51Z" - latency: 2.074717ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:38:51Z" - latency: 2.255266ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:37:51Z" - latency: 2.380082ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:36:51Z" - latency: 2.379085ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:35:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-17T16:23:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-179-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-179.ec2.internal uid: fb15098d-2c14-4341-8226-cf1e258dfa1d resourceVersion: "39792" uid: 4937b378-2b86-405c-ad64-0764df3d20e8 spec: sourcePod: network-check-source-8894fc9bd-6dmj7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T16:29:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 946.949µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:47:51Z" - latency: 2.016242ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T16:47:51Z" - latency: 862.065µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:46:51Z" - latency: 2.163039ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T16:46:51Z" - latency: 1.137553ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:45:51Z" - latency: 1.778424ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T16:45:51Z" - latency: 1.021704ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:44:51Z" - latency: 2.090673ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T16:44:51Z" - latency: 903.031µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T16:43:51Z" - latency: 1.67201ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T16:43:51Z" kind: List metadata: resourceVersion: ""