apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:47:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-159-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-159.ec2.internal uid: 6bb23917-5017-49a5-820b-312ff650e05f resourceVersion: "20331" uid: 2c389a2c-08f6-45de-b0f4-7de6b38e9f7c spec: sourcePod: network-check-source-dbd9cf844-vgd49 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T15:54:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.143067ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:08:21Z" - latency: 905.584µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:07:21Z" - latency: 806.023µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:06:21Z" - latency: 863.606µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:05:21Z" - latency: 1.040954ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:04:21Z" - latency: 774.33µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:03:21Z" - latency: 1.101974ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:02:21Z" - latency: 1.297597ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:01:21Z" - latency: 1.175923ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:00:21Z" - latency: 1.101958ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:59:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:47:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-159-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-159.ec2.internal uid: 6bb23917-5017-49a5-820b-312ff650e05f resourceVersion: "21928" uid: 1dcf197c-86eb-4fbe-adee-0e08c6f38bbd spec: sourcePod: network-check-source-dbd9cf844-vgd49 targetEndpoint: aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T15:53:21Z" message: 'load-balancer-api-external: tcp connection to aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.559042ms message: 'load-balancer-api-external: tcp connection to aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:11:21Z" - latency: 6.864519ms message: 'load-balancer-api-external: resolved host name aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T16:11:21Z" - latency: 6.202294ms message: 'load-balancer-api-external: tcp connection to aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:10:21Z" - latency: 8.252779ms message: 'load-balancer-api-external: resolved host name aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T16:10:21Z" - latency: 4.200457ms message: 'load-balancer-api-external: tcp connection to aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:09:21Z" - latency: 8.180793ms message: 'load-balancer-api-external: resolved host name aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T16:09:21Z" - latency: 4.918579ms message: 'load-balancer-api-external: tcp connection to aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:08:21Z" - latency: 8.621246ms message: 'load-balancer-api-external: resolved host name aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T16:08:21Z" - latency: 4.89068ms message: 'load-balancer-api-external: tcp connection to aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:07:21Z" - latency: 7.666862ms message: 'load-balancer-api-external: resolved host name aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T16:07:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:47:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-159-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-159.ec2.internal uid: 6bb23917-5017-49a5-820b-312ff650e05f resourceVersion: "21927" uid: 9af8ee11-7425-454b-86ba-1af4ee80d3f6 spec: sourcePod: network-check-source-dbd9cf844-vgd49 targetEndpoint: aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T15:53:21Z" message: 'load-balancer-api-internal: tcp connection to aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.574057ms message: 'load-balancer-api-internal: tcp connection to aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:11:21Z" - latency: 6.731897ms message: 'load-balancer-api-internal: resolved host name aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T16:11:21Z" - latency: 6.274846ms message: 'load-balancer-api-internal: tcp connection to aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:10:21Z" - latency: 8.196385ms message: 'load-balancer-api-internal: resolved host name aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T16:10:21Z" - latency: 9.680632ms message: 'load-balancer-api-internal: tcp connection to aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:09:21Z" - latency: 8.124393ms message: 'load-balancer-api-internal: resolved host name aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T16:09:21Z" - latency: 4.956547ms message: 'load-balancer-api-internal: tcp connection to aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:08:21Z" - latency: 8.543612ms message: 'load-balancer-api-internal: resolved host name aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T16:08:21Z" - latency: 4.884003ms message: 'load-balancer-api-internal: tcp connection to aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:07:21Z" - latency: 7.783841ms message: 'load-balancer-api-internal: resolved host name aab6f481dbb224d81af7cbcdb5457c4f-2848cfc039f3fc58.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T16:07:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:47:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-159-to-network-check-target-ip-10-0-128-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-159.ec2.internal uid: 6bb23917-5017-49a5-820b-312ff650e05f resourceVersion: "20330" uid: ed80cc61-e7b0-461e-84a9-bd08086e88cc spec: sourcePod: network-check-source-dbd9cf844-vgd49 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T15:54:21Z" message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.209245ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:08:21Z" - latency: 2.070431ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:07:21Z" - latency: 2.432149ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:06:21Z" - latency: 2.444641ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:05:21Z" - latency: 2.269841ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:04:21Z" - latency: 2.086335ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:03:21Z" - latency: 2.327625ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:02:21Z" - latency: 2.292986ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:01:21Z" - latency: 2.323394ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:00:21Z" - latency: 2.465144ms message: 'network-check-target-ip-10-0-128-73: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:59:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:47:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-159-to-network-check-target-ip-10-0-129-94 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-159.ec2.internal uid: 6bb23917-5017-49a5-820b-312ff650e05f resourceVersion: "20329" uid: dcc9099c-421a-4d20-b71c-daa4c12822b4 spec: sourcePod: network-check-source-dbd9cf844-vgd49 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T15:54:21Z" message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.720339ms message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:08:21Z" - latency: 2.120301ms message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:07:21Z" - latency: 1.744716ms message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:06:21Z" - latency: 1.85122ms message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:05:21Z" - latency: 1.899668ms message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:04:21Z" - latency: 1.900611ms message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:03:21Z" - latency: 1.803026ms message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:02:21Z" - latency: 1.836192ms message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:01:21Z" - latency: 2.095189ms message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:00:21Z" - latency: 1.768547ms message: 'network-check-target-ip-10-0-129-94: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:59:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:47:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-159-to-network-check-target-ip-10-0-136-159 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-159.ec2.internal uid: 6bb23917-5017-49a5-820b-312ff650e05f resourceVersion: "20328" uid: c44d5750-6298-49d4-92a0-7dbf4d53af19 spec: sourcePod: network-check-source-dbd9cf844-vgd49 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T15:54:21Z" message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 816.528µs message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:08:21Z" - latency: 978.972µs message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:07:21Z" - latency: 1.053992ms message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:06:21Z" - latency: 869.542µs message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:05:21Z" - latency: 1.387707ms message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:04:21Z" - latency: 1.614325ms message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:03:21Z" - latency: 933.196µs message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:02:21Z" - latency: 1.556483ms message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:01:21Z" - latency: 954.087µs message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:00:21Z" - latency: 799.692µs message: 'network-check-target-ip-10-0-136-159: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T15:59:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T15:47:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-159-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-159.ec2.internal uid: 6bb23917-5017-49a5-820b-312ff650e05f resourceVersion: "21926" uid: 4287ec15-3056-4ea8-bb0f-56eff88cab42 spec: sourcePod: network-check-source-dbd9cf844-vgd49 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T15:53:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 925.994µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:11:21Z" - latency: 1.691916ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T16:11:21Z" - latency: 667.935µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:10:21Z" - latency: 1.556649ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T16:10:21Z" - latency: 849.103µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:09:21Z" - latency: 1.631249ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T16:09:21Z" - latency: 806.365µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:08:21Z" - latency: 2.225646ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T16:08:21Z" - latency: 752.739µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T16:07:21Z" - latency: 1.87474ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T16:07:21Z" kind: List metadata: resourceVersion: ""