apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T16:44:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-37-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-37.ec2.internal uid: 3df0202e-f431-4078-a441-7af645ac738d resourceVersion: "39925" uid: c8b3b838-969c-4714-a0d1-d3d657cce7bb spec: sourcePod: network-check-source-8894fc9bd-4d6qk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T16:51:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 894.93µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:40:42Z" - latency: 1.073095ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:39:42Z" - latency: 943.34µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:38:42Z" - latency: 974.96µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:37:42Z" - latency: 1.106364ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:36:42Z" - latency: 985.843µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:35:42Z" - latency: 1.08085ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:34:42Z" - latency: 912.971µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:33:42Z" - latency: 1.042ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:32:42Z" - latency: 1.052462ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:31:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T16:44:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-37-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-37.ec2.internal uid: 3df0202e-f431-4078-a441-7af645ac738d resourceVersion: "42094" uid: 87f3a6b7-6276-4e55-b517-a8cf7d8a8dc5 spec: sourcePod: network-check-source-8894fc9bd-4d6qk targetEndpoint: a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T16:50:42Z" message: 'load-balancer-api-external: tcp connection to a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.622076ms message: 'load-balancer-api-external: tcp connection to a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:44:42Z" - latency: 8.117986ms message: 'load-balancer-api-external: resolved host name a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:44:42Z" - latency: 4.117778ms message: 'load-balancer-api-external: tcp connection to a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:43:42Z" - latency: 8.217021ms message: 'load-balancer-api-external: resolved host name a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:43:42Z" - latency: 5.171831ms message: 'load-balancer-api-external: tcp connection to a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:42:42Z" - latency: 7.945839ms message: 'load-balancer-api-external: resolved host name a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:42:42Z" - latency: 3.767158ms message: 'load-balancer-api-external: tcp connection to a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:41:42Z" - latency: 8.163278ms message: 'load-balancer-api-external: resolved host name a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:41:42Z" - latency: 4.397333ms message: 'load-balancer-api-external: tcp connection to a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:40:42Z" - latency: 8.944042ms message: 'load-balancer-api-external: resolved host name a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:40:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T16:44:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-37-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-37.ec2.internal uid: 3df0202e-f431-4078-a441-7af645ac738d resourceVersion: "42095" uid: 98e3992f-ecb1-4fa0-bd14-737919e27a20 spec: sourcePod: network-check-source-8894fc9bd-4d6qk targetEndpoint: a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T16:50:42Z" message: 'load-balancer-api-internal: tcp connection to a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.594696ms message: 'load-balancer-api-internal: tcp connection to a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:44:42Z" - latency: 8.062692ms message: 'load-balancer-api-internal: resolved host name a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:44:42Z" - latency: 4.128967ms message: 'load-balancer-api-internal: tcp connection to a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:43:42Z" - latency: 8.187168ms message: 'load-balancer-api-internal: resolved host name a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:43:42Z" - latency: 5.26083ms message: 'load-balancer-api-internal: tcp connection to a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:42:42Z" - latency: 7.813362ms message: 'load-balancer-api-internal: resolved host name a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:42:42Z" - latency: 3.79493ms message: 'load-balancer-api-internal: tcp connection to a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:41:42Z" - latency: 8.101589ms message: 'load-balancer-api-internal: resolved host name a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:41:42Z" - latency: 4.443065ms message: 'load-balancer-api-internal: tcp connection to a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:40:42Z" - latency: 8.893883ms message: 'load-balancer-api-internal: resolved host name a23dd618bf5b1432e9199545b124a6ec-11c246fa6d4fe17e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T17:40:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T16:44:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-37-to-network-check-target-ip-10-0-131-37 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-37.ec2.internal uid: 3df0202e-f431-4078-a441-7af645ac738d resourceVersion: "39922" uid: bacfff45-fc5a-4094-8de0-2da125a51757 spec: sourcePod: network-check-source-8894fc9bd-4d6qk targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-24T16:51:42Z" message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 842.619µs message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:40:42Z" - latency: 778.277µs message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:39:42Z" - latency: 1.479098ms message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:38:42Z" - latency: 844.047µs message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:37:42Z" - latency: 963.101µs message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:36:42Z" - latency: 931.849µs message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:35:42Z" - latency: 858.375µs message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:34:42Z" - latency: 959.232µs message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:33:42Z" - latency: 1.516959ms message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:32:42Z" - latency: 909.349µs message: 'network-check-target-ip-10-0-131-37: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:31:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T16:44:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-37-to-network-check-target-ip-10-0-137-179 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-37.ec2.internal uid: 3df0202e-f431-4078-a441-7af645ac738d resourceVersion: "39924" uid: 10101d9b-ca5b-4566-9877-5de58f2b923d spec: sourcePod: network-check-source-8894fc9bd-4d6qk targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T16:51:42Z" message: 'network-check-target-ip-10-0-137-179: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.27933ms message: 'network-check-target-ip-10-0-137-179: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:40:42Z" - latency: 2.772218ms message: 'network-check-target-ip-10-0-137-179: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:39:42Z" - latency: 2.417671ms message: 'network-check-target-ip-10-0-137-179: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:38:42Z" - latency: 2.426015ms message: 'network-check-target-ip-10-0-137-179: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:37:42Z" - latency: 2.39282ms message: 'network-check-target-ip-10-0-137-179: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:36:42Z" - latency: 2.306906ms message: 'network-check-target-ip-10-0-137-179: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:35:42Z" - latency: 2.203456ms message: 'network-check-target-ip-10-0-137-179: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:34:42Z" - latency: 2.264689ms message: 'network-check-target-ip-10-0-137-179: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:33:42Z" - latency: 2.212209ms message: 'network-check-target-ip-10-0-137-179: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:32:42Z" - latency: 2.074084ms message: 'network-check-target-ip-10-0-137-179: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:31:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T16:44:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-37-to-network-check-target-ip-10-0-142-182 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-37.ec2.internal uid: 3df0202e-f431-4078-a441-7af645ac738d resourceVersion: "39923" uid: cc71071f-700c-490c-9eca-ec66b3bdedeb spec: sourcePod: network-check-source-8894fc9bd-4d6qk targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T16:51:42Z" message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.1817ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:40:42Z" - latency: 2.817504ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:39:42Z" - latency: 2.453887ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:38:42Z" - latency: 2.275038ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:37:42Z" - latency: 2.263502ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:36:42Z" - latency: 2.357168ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:35:42Z" - latency: 2.375664ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:34:42Z" - latency: 1.904564ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:33:42Z" - latency: 2.470018ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:32:42Z" - latency: 2.407855ms message: 'network-check-target-ip-10-0-142-182: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:31:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T16:44:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-37-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-37.ec2.internal uid: 3df0202e-f431-4078-a441-7af645ac738d resourceVersion: "42093" uid: 8318cd3d-5ce9-4044-a68c-e9e1e3656544 spec: sourcePod: network-check-source-8894fc9bd-4d6qk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T16:50:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 864.519µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:44:42Z" - latency: 1.757596ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T17:44:42Z" - latency: 882.961µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:43:42Z" - latency: 1.625382ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T17:43:42Z" - latency: 1.045314ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:42:42Z" - latency: 1.689814ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T17:42:42Z" - latency: 1.050452ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:41:42Z" - latency: 1.923385ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T17:41:42Z" - latency: 1.155897ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T17:40:42Z" - latency: 1.729717ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T17:40:42Z" kind: List metadata: resourceVersion: ""