apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T17:09:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-220-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-220.ec2.internal uid: 306fe638-1ee0-4013-947c-00344f9e91e6 resourceVersion: "60368" uid: 38f29150-fbc1-4f87-bb65-a2ecdf67e172 spec: sourcePod: network-check-source-869dcfcdcd-hq4vq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-13T17:16:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.177109ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:51:19Z" - latency: 1.171073ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:50:19Z" - latency: 1.375774ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:49:19Z" - latency: 826.626µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:48:19Z" - latency: 1.349059ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:47:19Z" - latency: 924.438µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:46:19Z" - latency: 1.175127ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:45:19Z" - latency: 966.15µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:44:19Z" - latency: 856.568µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:43:19Z" - latency: 1.407203ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:42:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T17:09:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-220-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-220.ec2.internal uid: 306fe638-1ee0-4013-947c-00344f9e91e6 resourceVersion: "60370" uid: a7aa301d-1ae6-43d3-9267-236a753ce9a6 spec: sourcePod: network-check-source-869dcfcdcd-hq4vq targetEndpoint: a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T17:15:19Z" message: 'load-balancer-api-external: tcp connection to a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.837275ms message: 'load-balancer-api-external: tcp connection to a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:51:19Z" - latency: 9.034648ms message: 'load-balancer-api-external: resolved host name a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T17:51:19Z" - latency: 4.019697ms message: 'load-balancer-api-external: tcp connection to a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:50:19Z" - latency: 7.773806ms message: 'load-balancer-api-external: resolved host name a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T17:50:19Z" - latency: 3.6034ms message: 'load-balancer-api-external: tcp connection to a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:49:19Z" - latency: 6.410008ms message: 'load-balancer-api-external: resolved host name a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T17:49:19Z" - latency: 4.562576ms message: 'load-balancer-api-external: tcp connection to a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:48:19Z" - latency: 8.760671ms message: 'load-balancer-api-external: resolved host name a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T17:48:19Z" - latency: 4.008467ms message: 'load-balancer-api-external: tcp connection to a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:47:19Z" - latency: 7.64575ms message: 'load-balancer-api-external: resolved host name a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T17:47:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T17:09:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-220-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-220.ec2.internal uid: 306fe638-1ee0-4013-947c-00344f9e91e6 resourceVersion: "60369" uid: b20866a0-d2ca-457c-bac5-0a0ae5c766f7 spec: sourcePod: network-check-source-869dcfcdcd-hq4vq targetEndpoint: a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T17:15:19Z" message: 'load-balancer-api-internal: tcp connection to a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.87162ms message: 'load-balancer-api-internal: tcp connection to a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:51:19Z" - latency: 8.921336ms message: 'load-balancer-api-internal: resolved host name a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T17:51:19Z" - latency: 4.002407ms message: 'load-balancer-api-internal: tcp connection to a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:50:19Z" - latency: 7.722703ms message: 'load-balancer-api-internal: resolved host name a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T17:50:19Z" - latency: 3.538162ms message: 'load-balancer-api-internal: tcp connection to a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:49:19Z" - latency: 6.449123ms message: 'load-balancer-api-internal: resolved host name a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T17:49:19Z" - latency: 4.56476ms message: 'load-balancer-api-internal: tcp connection to a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:48:19Z" - latency: 8.8152ms message: 'load-balancer-api-internal: resolved host name a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T17:48:19Z" - latency: 4.111181ms message: 'load-balancer-api-internal: tcp connection to a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:47:19Z" - latency: 7.670353ms message: 'load-balancer-api-internal: resolved host name a9e4cd443864d4fc99701cba3a43690f-6cadb7ec848174a6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T17:47:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T17:09:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-220-to-network-check-target-ip-10-0-136-220 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-220.ec2.internal uid: 306fe638-1ee0-4013-947c-00344f9e91e6 resourceVersion: "60364" uid: c1f59814-65cf-45ab-8167-974a8b4bd495 spec: sourcePod: network-check-source-869dcfcdcd-hq4vq targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-13T17:16:19Z" message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.096842ms message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:51:19Z" - latency: 1.212863ms message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:50:19Z" - latency: 1.646652ms message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:49:19Z" - latency: 886.108µs message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:48:19Z" - latency: 1.329713ms message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:47:19Z" - latency: 975.894µs message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:46:19Z" - latency: 926.422µs message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:45:19Z" - latency: 1.153875ms message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:44:19Z" - latency: 881.608µs message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:43:19Z" - latency: 810.137µs message: 'network-check-target-ip-10-0-136-220: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:42:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T17:09:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-220-to-network-check-target-ip-10-0-137-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-220.ec2.internal uid: 306fe638-1ee0-4013-947c-00344f9e91e6 resourceVersion: "60365" uid: dbbe9584-a973-439c-a21d-784dc068b489 spec: sourcePod: network-check-source-869dcfcdcd-hq4vq targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T17:16:19Z" message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.655795ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:51:19Z" - latency: 2.249084ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:50:19Z" - latency: 2.384192ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:49:19Z" - latency: 2.004997ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:48:19Z" - latency: 2.64869ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:47:19Z" - latency: 2.641039ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:46:19Z" - latency: 2.903483ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:45:19Z" - latency: 2.361361ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:44:19Z" - latency: 2.168751ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:43:19Z" - latency: 1.896516ms message: 'network-check-target-ip-10-0-137-245: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:42:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T17:09:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-220-to-network-check-target-ip-10-0-138-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-220.ec2.internal uid: 306fe638-1ee0-4013-947c-00344f9e91e6 resourceVersion: "60366" uid: 7abd82be-d909-4335-9a52-c7a707b74224 spec: sourcePod: network-check-source-869dcfcdcd-hq4vq targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-13T17:16:19Z" message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.414257ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:51:19Z" - latency: 2.317724ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:50:19Z" - latency: 2.301786ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:49:19Z" - latency: 2.355917ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:48:19Z" - latency: 2.384768ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:47:19Z" - latency: 2.073416ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:46:19Z" - latency: 2.403423ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:45:19Z" - latency: 2.3606ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:44:19Z" - latency: 2.34248ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:43:19Z" - latency: 2.140264ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:42:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T17:09:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-220-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-220.ec2.internal uid: 306fe638-1ee0-4013-947c-00344f9e91e6 resourceVersion: "60367" uid: 296e8d75-767e-4b08-a7dc-77b7307560f6 spec: sourcePod: network-check-source-869dcfcdcd-hq4vq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-13T17:15:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 908.622µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:51:19Z" - latency: 2.090487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T17:51:19Z" - latency: 1.011686ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:50:19Z" - latency: 1.931745ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T17:50:19Z" - latency: 968.942µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:49:19Z" - latency: 1.94446ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T17:49:19Z" - latency: 862.06µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:48:19Z" - latency: 1.802734ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T17:48:19Z" - latency: 817.739µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T17:47:19Z" - latency: 2.605929ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T17:47:19Z" kind: List metadata: resourceVersion: ""