apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T14:55:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-241-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-241.ec2.internal uid: e4cf59ca-60e8-4401-98b4-4f90e2127e13 resourceVersion: "60146" uid: eab4d250-3fb9-4632-9f09-a9e3dc3a0be7 spec: sourcePod: network-check-source-869dcfcdcd-r5rgg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-13T15:02:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.14543ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:37:37Z" - latency: 1.004376ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:36:37Z" - latency: 1.16699ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:35:37Z" - latency: 810.805µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:34:37Z" - latency: 1.113311ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:33:37Z" - latency: 1.095144ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:32:37Z" - latency: 1.063413ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:31:37Z" - latency: 1.358908ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:30:37Z" - latency: 1.270604ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:29:37Z" - latency: 1.176907ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:28:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T14:55:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-241-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-241.ec2.internal uid: e4cf59ca-60e8-4401-98b4-4f90e2127e13 resourceVersion: "60148" uid: a4c09b5f-a9c9-4aad-88e2-224b48fb0c9e spec: sourcePod: network-check-source-869dcfcdcd-r5rgg targetEndpoint: a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T15:01:37Z" message: 'load-balancer-api-external: tcp connection to a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.207996ms message: 'load-balancer-api-external: tcp connection to a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:37:37Z" - latency: 10.452498ms message: 'load-balancer-api-external: resolved host name a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T15:37:37Z" - latency: 3.826417ms message: 'load-balancer-api-external: tcp connection to a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:36:37Z" - latency: 6.437087ms message: 'load-balancer-api-external: resolved host name a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T15:36:37Z" - latency: 4.0869ms message: 'load-balancer-api-external: tcp connection to a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:35:37Z" - latency: 7.462468ms message: 'load-balancer-api-external: resolved host name a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T15:35:37Z" - latency: 3.883234ms message: 'load-balancer-api-external: tcp connection to a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:34:37Z" - latency: 7.103564ms message: 'load-balancer-api-external: resolved host name a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T15:34:37Z" - latency: 4.414772ms message: 'load-balancer-api-external: tcp connection to a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:33:37Z" - latency: 8.34197ms message: 'load-balancer-api-external: resolved host name a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T15:33:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T14:55:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-241-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-241.ec2.internal uid: e4cf59ca-60e8-4401-98b4-4f90e2127e13 resourceVersion: "60149" uid: c81e7e17-2b7a-4234-890e-b4a07ab792c8 spec: sourcePod: network-check-source-869dcfcdcd-r5rgg targetEndpoint: a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T15:01:37Z" message: 'load-balancer-api-internal: tcp connection to a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.740492ms message: 'load-balancer-api-internal: tcp connection to a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:37:37Z" - latency: 10.549171ms message: 'load-balancer-api-internal: resolved host name a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T15:37:37Z" - latency: 3.816675ms message: 'load-balancer-api-internal: tcp connection to a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:36:37Z" - latency: 6.530289ms message: 'load-balancer-api-internal: resolved host name a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T15:36:37Z" - latency: 4.549583ms message: 'load-balancer-api-internal: tcp connection to a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:35:37Z" - latency: 7.381537ms message: 'load-balancer-api-internal: resolved host name a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T15:35:37Z" - latency: 5.309491ms message: 'load-balancer-api-internal: tcp connection to a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:34:37Z" - latency: 7.021129ms message: 'load-balancer-api-internal: resolved host name a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T15:34:37Z" - latency: 4.869459ms message: 'load-balancer-api-internal: tcp connection to a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:33:37Z" - latency: 8.239483ms message: 'load-balancer-api-internal: resolved host name a8b89f2e55f5148eb997d5e29f0c87b5-e0dbb730badcc5f4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T15:33:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T14:55:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-241-to-network-check-target-ip-10-0-128-29 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-241.ec2.internal uid: e4cf59ca-60e8-4401-98b4-4f90e2127e13 resourceVersion: "60144" uid: 6ea4890e-2ed2-4f13-8143-63b016cd51c3 spec: sourcePod: network-check-source-869dcfcdcd-r5rgg targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T15:02:37Z" message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.041734ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:37:37Z" - latency: 1.842269ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:36:37Z" - latency: 2.032136ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:35:37Z" - latency: 1.599384ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:34:37Z" - latency: 2.077513ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:33:37Z" - latency: 1.810772ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:32:37Z" - latency: 1.945581ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:31:37Z" - latency: 2.104009ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:30:37Z" - latency: 1.893615ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:29:37Z" - latency: 1.832745ms message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:28:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T14:55:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-241-to-network-check-target-ip-10-0-134-237 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-241.ec2.internal uid: e4cf59ca-60e8-4401-98b4-4f90e2127e13 resourceVersion: "60143" uid: 0963a2e7-b40c-4ebd-9c86-36cd1be5d7f1 spec: sourcePod: network-check-source-869dcfcdcd-r5rgg targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T15:02:37Z" message: 'network-check-target-ip-10-0-134-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.219154ms message: 'network-check-target-ip-10-0-134-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:37:37Z" - latency: 1.975163ms message: 'network-check-target-ip-10-0-134-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:36:37Z" - latency: 2.171466ms message: 'network-check-target-ip-10-0-134-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:35:37Z" - latency: 1.848436ms message: 'network-check-target-ip-10-0-134-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:34:37Z" - latency: 2.210348ms message: 'network-check-target-ip-10-0-134-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:33:37Z" - latency: 2.28176ms message: 'network-check-target-ip-10-0-134-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:32:37Z" - latency: 2.31443ms message: 'network-check-target-ip-10-0-134-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:31:37Z" - latency: 2.391981ms message: 'network-check-target-ip-10-0-134-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:30:37Z" - latency: 2.17612ms message: 'network-check-target-ip-10-0-134-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:29:37Z" - latency: 2.20984ms message: 'network-check-target-ip-10-0-134-237: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:28:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T14:55:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-241-to-network-check-target-ip-10-0-134-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-241.ec2.internal uid: e4cf59ca-60e8-4401-98b4-4f90e2127e13 resourceVersion: "60142" uid: f77136f3-ac3c-4c65-885c-b81088fb1814 spec: sourcePod: network-check-source-869dcfcdcd-r5rgg targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-13T15:02:37Z" message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.248217ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:37:37Z" - latency: 1.197489ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:36:37Z" - latency: 939.71µs message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:35:37Z" - latency: 1.23817ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:34:37Z" - latency: 1.051813ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:33:37Z" - latency: 1.047889ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:32:37Z" - latency: 1.370252ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:31:37Z" - latency: 1.104407ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:30:37Z" - latency: 898.829µs message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:29:37Z" - latency: 918.042µs message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:28:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T14:55:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-241-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-241.ec2.internal uid: e4cf59ca-60e8-4401-98b4-4f90e2127e13 resourceVersion: "60145" uid: 4590ba04-62d0-4ea5-9a10-61202e2bcb16 spec: sourcePod: network-check-source-869dcfcdcd-r5rgg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-13T15:01:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 701.96µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:37:37Z" - latency: 2.083043ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T15:37:37Z" - latency: 898.01µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:36:37Z" - latency: 1.808409ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T15:36:37Z" - latency: 868.932µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:35:37Z" - latency: 1.847922ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T15:35:37Z" - latency: 820.101µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:34:37Z" - latency: 2.174816ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T15:34:37Z" - latency: 792.227µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T15:33:37Z" - latency: 2.266538ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T15:33:37Z" kind: List metadata: resourceVersion: ""